Unanswered

"An attribute with the specified name already exists for entity" but it doesnt exists

(0) Share

Report

Posted on by felypeterra

I get this error "An attribute with the specified name (column name) already exists for entity (table name)" when trying to create a column, but the name isnt being used in any other column from any table.

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (0)

felypeterra 2 on at

Like (0)

Report

Its a dataverse table

Was this reply helpful? Yes No
bankmeneertje on at

Like (0)

Report

Did you find any fix? I am getting the same problem.
I tried to create te column before with no succes, might it be like a shadow exist?

Was this reply helpful? Yes No
gary_nightingal 2 on at

Like (0)

Report

my issue deals with entities relationships.
I have a property-lease relationship and was told to create a property-service relationship, but I keep getting this result: "An attribute with the specified name mti_PropertyGN already exists for entity mti_ServiceGN.", which is not the case.

Was this reply helpful? Yes No
olira 2 on at

Like (0)

Report
I ran into the same error message but likely a different scenario.

While the issues described above may differ, what I have learned may help further debugging.

The error occurred when I tried to create a calculated column cust_AccountName, which should show some data about an entity linked by the lookup-type column cust_Account.

I couldn't find anything wrong by looking at the UI or querying the table through WebAPI.
At this point, I decided to fetch the Attributes directly off the EntityDefinitions WebAPI:

https://<dynamicshost>/api/data/v9.2/EntityDefinitions(LogicalName='<logicaltablename>')/Attributes

Using the EntityDefinitions endpoint, I got a complete list of any internal and external attributes and their metadata. Indeed, a logical attribute with this name indeed existed and was an attribute of the lookup column I created.

[ ..., { "@odata.type": "#Microsoft.Dynamics.CRM.StringAttributeMetadata", "Format": "Text", "AttributeOf": "cust_account", "AttributeType": "String", "EntityLogicalName": "cust_detail", "IsCustomAttribute": true, "LogicalName": "cust_accountname", "SchemaName": "cust_AccountName", "ExternalName": null, "IsLogical": true, ... }, ... }

So, for my issue, when one creates a lookup-type column, there is an internal Logical column <lookupcolumnname>name, which is automatically created.

More details about the EntityDefinitions Endpoint can be found on Microsoft Learn.

Was this reply helpful? Yes No
bankmeneertje on at

Like (0)

Report

Very interesting, that explains the problem! Thanks for sharing.

Was this reply helpful? Yes No