Forum Discussion
Power bi dashboard
When I make a power bi dashboard for the pre built app in my office So that App is used AD password for the UserID since when I make the relationship between the tables I used from the database to power bi, should have to get that AD password as the primary key between the tables in power query modeling since I cannot make proper relationship between tables in power bi Why is that
Hi APWS ,
You don’t need to use AD passwords as keys for relationships in Power BI, as passwords are sensitive and not meant for linking tables. Instead, please use a stable user identifier like UserID, UserPrincipalName (email), or EmployeeID that exists in both tables.
5 Replies
- burakkaragozSuper User
Hi APWS ,
Since your measure already works in a table, you’re almost there. To get it working in a pie chart, you just need to reshape the logic a bit so that the chart can group by "On Time" vs "Not On Time" status.
Here’s a clean way to do it:
1. Create a new measure that returns status per house:
HouseStatus = VAR AllPartsOnTime = CALCULATE( COUNTROWS(HouseParts), HouseParts[PlannedDate] <> HouseParts[RealDate] ) = 0 RETURN IF(AllPartsOnTime, "On Time", "Not On Time")2. Create a summary table (optional but helps):
HouseSummary = SUMMARIZE( HouseParts, HouseParts[House], "Status", [HouseStatus] )3. Use this in your pie chart:
- Legend: Status
- Values: DISTINCTCOUNT(HouseParts[House]) or just House if you're using the summary table
This will give you a pie chart showing how many houses are fully on time vs not, based on your current date filter.
Also make sure your date slicer is filtering the data correctly so the measure reflects the right time window.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
translation and formatting supported by AI - BhavinVyas3003Super User
Hi APWS ,
You don’t need to use AD passwords as keys for relationships in Power BI, as passwords are sensitive and not meant for linking tables. Instead, please use a stable user identifier like UserID, UserPrincipalName (email), or EmployeeID that exists in both tables.
- v-echaithraCommunity Support
Hi APWS ,
Thank you BhavinVyas3003 for your inputs.
We would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.Regards,
Chaithra. - v-echaithraCommunity Support
Hi APWS ,
May I ask if you have gotten this issue resolved?
If it is solved, please mark the helpful reply or share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster.
Regards,
Chaithra. - v-echaithraCommunity Support
Hi @APWS ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.Regards,
Chaithra.