Proxyaddress error when bringing in Salesforce and SQL Server data to dataflow

[dvnitsch21]

Hello, I am attempting to bring in data from a Salesforce object and a SQL Server instance to the same dataflow. I am able to bring in both individually but once I try connecting to both I get an error message on the Salesforce data connection saying "The value of the property 'proxyaddress' cannot be parsed. The error is: Invalid URI: The Authority/Host could be parsed." The first screenshot shows me able to select the merge option once I connect to both but then once I apply the merge it prompts the error message and no longer loads the Salesforce data. I am able to do this successfully in PBI desktop but have a need to bring the query into a dataflow to share with an external customer. Any help would be appreciated!

[ReportMaster]

Hi @dvnitsch21 As a workaround, maybe you can try to test your connection with a 3rd party connector, which pulls data directly from SF objects API. I've tried windsor.ai, supermetrics and funnel.io. I stayed with windsor because it is much cheaper so just to let you know other options. In case you wonder, to make the connection first search for the Salesforce connector in the data sources list:

After that, just grant access to your Salesforce account using your credentials, then on preview and destination page you will see a preview of your Salesforce fields:

There just select the fields you need. It is also compatible with custom fields and custom objects, so you'll be able to export them through windsor.  Finally, just select PBI as your data destination and finally just copy and paste the url on PBI --> Get Data --> Web --> Paste the url. 

[aj1973]

Hi @dvnitsch21 

before merging check out the Field id of both Tables if there is an issue with one or multiple cells. Looks like the Gateway could not parse and id in line 7.

[dvnitsch21]

I don't see any issues, I think the error is on line 7 and not row 7 of the tables. I still get the error if I don't do the merge and just attempt to refresh the SF data.

[aj1973]

I see,

Try to add a SQL code to the SF table to CAST the id field before calling it into the dataflow.