johnsaxton
Microsoft Employee
4 years agoStatus:
New
Do not force or assume transformations when Power Query gets data.
I have used Power Query as part of Power BI and Dynamics 365 Customer Insights. In both cases when Power Query is used to connect to data in Dynamics 365 (Dataverse) Power Query converts all GUIDS to uppercase.
Dynamics 365 stores GUIDS in lowercase. When Power Query forces this transformation, it breaks the relationship between the system of record (Dynamics 365) and the Power BI report or the Customer Insights environment. In order to restore the relationship the user has to manually add a lowercase transformation.
This seems like a bug in Power Query. If this is an intended feature, we should at the very least, be able to turn it on or off.
1 Comment
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Power BI - incorrect handling of empty string parameter in DAX query in paginated report
Blank string parameters in paginated reports are treated as empty strings in Power BI Report Builder but as null values in the Power BI Service, resulting in incorrect report output. -> Create a pag...roshinikumarkar2 hours agoMicrosoft EmployeeNew21Views5likes0CommentsAllow NotebookUtils getSecret() to authenticate with Workspace Identity
Current behavior In Microsoft Fabric, notebookutils.credentials.getSecret() authenticates against Azure Key Vault using the identity of the user who executes the notebook. This behavior appli...tmihara4 hours agoNew MemberNew18Views1like1CommentAllow us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels11 hours agoAdvocate IIINew188Views0likes2Comments