Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
I am working on a SQL server where the primary/foreign keys majority in the Uniqueidentifier data type. Power BI recognize this as a text field (though, MS Access will recognize as an integer/GUID field)...not sure if that is important to note or not, but it is interesting that Power BI doesn't recognize the data type as SQL Server and Access recognize it.
So, when using these keys in relationships where all tables are in DirectQuery or all in Import mode, Power BI recognizes the relationships and matches the keys correctly as values aggregate up as expected. BUT when I start adding in Dual mode with a mixture of DirectQuery/Import mode tables to utilize the Aggregate feature, the keys are no longer recognized and when using the visuals, it assumes there are no matches and aggregate everything up to a blank value.
I think this is due to how Power BI recognizes Uniqueidentifiers as mentioned above. There's other issues related to the Aggregate feature that I noticed someone else made a post to (i.e. Power BI ignore Aggregate tables even though the measure's filters within the Calculate function still fall in line with for hitting the Aggregate table).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.