Azure / logicapps

Azure Logic Apps labs, samples, and tools
MIT License
368 stars 302 forks source link

Dataverse Not Getting Correct Properties for Columns that Have Duplicate Display Names #1208

Open BACBcnorris opened 1 month ago

BACBcnorris commented 1 month ago

Describe the Bug

When using any Dataverse Action, if I select a table that has a duplicate name the properties that are displayed are that of the first table only.

It does not matter which table I select from the drop down, it will only show me the incorrect properties.

Plan Type

Consumption

Steps to Reproduce the Bug or Issue

  1. In Dataverse create a table that has a duplicate name, for example "Applications" or "Audits", these tables will be prefixed with your organization name.
  2. In Azure Logic Apps, create an action to Modify a dataverse entity.
  3. Select the new Duplicate table name from the drop down.
  4. The properties that are displayed are not correct.

When reviewing the code view, the path is not updated to reflect the correct entity name when the table is changed to either of the tables with the same name.

The only work around I have found is to update the path with the correct entity name which is organization_{table_name}

Workflow JSON

{ "type": "ApiConnection", "inputs": { "host": { "connection": { "referenceName": "commondataservice" } }, "method": "patch", "headers": { "prefer": "return=representation,odata.include-annotations=*", "accept": "application/json;odata.metadata=full", "organization": "@{encodeURIComponent(encodeURIComponent('{removed}.dynamics.com'))}" }, "path": "/api/data/v9.1/@{encodeURIComponent(encodeURIComponent('audits'))}(@{encodeURIComponent(encodeURIComponent(triggerBody()?['{removed}_auditid']))})" }, "runAfter": {} }

Screenshots or Videos

No response

Additional context

No response

BACBcnorris commented 1 month ago

There has been no action on this, so I am commenting on this to prevent premature closure.