Dashboard

Hi APWS,

Thank you  for reaching out to the Microsoft fabric community forum.

Relationships between tables should be created in the Model view after loading the data into Power BI. If you're trying to join tables inside Power Query using AD accounts, that might not give the expected results in the final model.

In some cases, the AD account may not be reliable if it's missing, duplicated, or inconsistent across systems. If your app stores a stable unique identifier, consider using that instead.

Ensure the AD account field is consistent in format. Even small differences like casing or extra spaces can break the relationship.
Ensure the AD account field is consistent in format. Even small differences like casing or extra spaces can break the relationship.

check that the data types match between the related fields in each table, as mismatched data types will block relationship creation.

If you could share more specific details about the issue you're encountering, we would be glad to help you further.

please gothrough with the below document hope it may resolve your Issue:
https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-create-and-manage-relationships

If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it

Best Regards,
Harshitha.
Community Support Team

Hi APWS 

The issue you're facing likely stems from inconsistencies or mismatches in how the Azure Active Directory (AD) account identifiers—such as user principal names (UPNs), email addresses, or object IDs—are represented across the different tables you're trying to join in Power BI's Power Query Editor. In enterprise applications, it's common to use the AD account (e.g., [email protected]) as a unique identifier, but problems arise when the format of this field varies across data sources. For instance, one table may store the full UPN, another might have only the username (user), and another may use the GUID-based object ID. If these formats don’t match exactly, Power BI cannot establish a proper relationship between the tables, leading to inaccurate results or failed joins.

 

Additionally, Power Query performs case-sensitive and whitespace-sensitive matching when creating relationships or performing merges, so even small formatting differences can break the logic. Another possible issue is missing or null AD values in some rows, which silently disrupts the relationships and results in incomplete visuals. To resolve this, you should first ensure all tables use the same, consistent AD field (e.g., UPN in lowercase, trimmed of spaces) and apply necessary transformations in Power Query to standardize them before attempting to merge or relate. You may also want to validate that all relevant users exist across both tables and that there are no duplicate or ambiguous entries. Once the identifiers are aligned, creating the relationships and generating accurate results in Power BI should work as expected.