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
Allow 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 ...PeterDaniels53 minutes agoAdvocate IIINew176Views0likes2CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen1 hour agoAdvocate INew292Views47likes2CommentsSupport Encrypted Sensitivity-Labeled Excel Files in Power Query
Description Currently, Power Query Online and Power Query in Excel are unable to access encrypted Excel files. Excel files with sensitivity types other than Public or Non-Business can be encrypted a...ewarstdhyjugkhi2 hours agoMicrosoft EmployeeNew16Views6likes0Comments