The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.
When I try and add a Dataverse table from my default environment I get the following error
Expression.Error: The field 'new_itemclassname' already exists in the record.
Details:
Name=new_itemclassname
Value=
This happens on loading any table in the default environment whether they are built in or custom. Power BI Desktop does not allow the table to load. This happens on a brand new blank report.
The problem does not exist if I load dataverse tables from other environments
Has anyone see this and have suggestions on how to troubleshoot?
Solved! Go to Solution.
The error means there's a duplicate column name (new_itemclassname) in the Dataverse table schema—likely caused by hidden metadata or relationships in the Default Environment. Power BI can't load it because each field must be unique. Try using a custom view, switching to OData, or loading from a different environment to bypass the issue
The error means there's a duplicate column name (new_itemclassname) in the Dataverse table schema—likely caused by hidden metadata or relationships in the Default Environment. Power BI can't load it because each field must be unique. Try using a custom view, switching to OData, or loading from a different environment to bypass the issue
Thanks so much Shahid12523. I will probably go down the route of creating a new environment but just wondered what you meant by try using a custom view? Thanks
@PaulineSP Is the only step the Source/Navigation steps? If not, try removing steps until the error goes away and then investigate that step or post what it is doing here.
It literally appears on the initial load when selecting the table - before any steps can be added
User | Count |
---|---|
65 | |
61 | |
60 | |
53 | |
30 |
User | Count |
---|---|
180 | |
88 | |
72 | |
48 | |
46 |