Forum Discussion
Salesforce Data Flow
Hi, Anonymous
Please check the transformations you have made on the entities. For further information, you may refer to the following link.
Best Regards
Allan
If this post helps, then please consider Accepting it as the solution.
Post ProdigyHi Mozart,
This sounds like a dataflow entity issue rather than a Salesforce connection issue.
Since the entity works when you exclude date columns, I would focus on how those Salesforce date or datetime fields are being typed and transformed inside the dataflow. I would try a very small test entity first:
Opportunity Id and Name only.
Add one Salesforce date field.
Add one Salesforce datetime field.
Check whether the entity still loads and appears in Power BI Desktop.
If it breaks, convert the date or datetime field to text at the earliest possible step, or create a separate normalized date column before saving the dataflow.
If the goal is simply to bring Salesforce Opportunity data into Power BI Desktop, another route is to skip the dataflow layer and connect Power BI to a prepared Salesforce dataset directly.
Power BI Connector for Salesforce by Metrica Software can help with that: https://appexchange.salesforce.com/appxListingDetail?listingId=31526f0e-abd8-4cb5-bd1a-3bd56b5c0577
With this connector, you create a data source inside Salesforce, select the Opportunity fields you need, apply filters, preview the output, and then connect Power BI to that prepared source. SOQL mode is also available if you need more control over date fields and filtering.
This does not fix Power BI dataflow date handling itself, but it can remove the extra dataflow layer if that is where the problem occurs.
Docs: https://metricasoftware.com/docs/salesforce/
Support: https://metricasoftware.com/docs/salesforce/contact-support/
Happy to show how we would structure an Opportunity export with date and datetime fields for Power BI.
Cheers,
Metrica Team