Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I am trying to connect to custom entities in Common Data Service to build reports for a Model-driven app.
It appears that if your entity name is the same as a field name (for example entity called new_department and you change the primary field from "name" to "department", so there ends up being a new_department field) then Power BI can't find the field.
From what I've researched, the api, when faced with this issue, applies a 1 to the field name under the covers. So ostensibly, the name of your field and entity are both new_department, but according to the api the field is named new_department1.
Somehow, Power BI is unable to recognize this, and subsequently the troublesome field just won't show up.
Anyone else ever encounter this? Any ideas on how to fix it or work around it? Rebuilding the entities is not an option. Anyone from Microsoft know if this is a known issue?
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
8 | |
7 | |
3 | |
2 | |
2 |
User | Count |
---|---|
6 | |
5 | |
4 | |
4 | |
3 |