Unanswered

Converted to Production and URL Change: No longer able to access CDS data

(0) Share

Report

Posted on by User3324234_BRD

Pretty new to power apps and Dataverse, but just switched over our environment from trial to production and renaming our environment url, and now unable to export table data (Connection validation failed. Connection '7c71bd42-35db-4525-9cc1-4dc806337fe0-default.cds.DM' does not exists.) and when trying to reference CDS data in flows (Could not retrieve values. Request to XRM API failed with error: 'Message:
Code: InnerError: '.).

Nearly positive its something to do with the tables referencing the old environment url, but unsure where to look to adjust the dataverse url ref.

Thanks!

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (7)

Answers (0)

ChrisPiasecki 6,422 Most Valuable Professional on at

Like (0)

Report

Hi @User3324234_BRD ,

How long after converting the environment did you run into this error? Wondering if it was still performing some actions in the background when you tried to do this? Have you tried clearing your browser cache and trying again?

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No
User3324234_BRD 10 on at

Like (0)

Report

Hi Chris,
Did not see any errors when converting the url and in converting to production, all went smoothly. I should also note these issues to not arise when utilizing CDS data in an app.

Was this reply helpful? Yes No
User3324234_BRD 10 on at

Like (0)

Report

[Redacted]

Was this reply helpful? Yes No
ChrisPiasecki 6,422 Most Valuable Professional on at

Like (0)

Report

Hi @User3324234_BRD ,

If you navigate to Data > Connections, does the status of the Common Data Service connectors say Connected? If not, you can try updating the connection to see if that helps.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No
User3324234_BRD 10 on at

Like (0)

Report

To no avail still, removed the connections, re-added, no luck. Also today, the Table and choices headers do not display at all anymore

Was this reply helpful? Yes No
ChrisPiasecki 6,422 Most Valuable Professional on at

Like (0)

Report

Hi @User3324234_BRD,

That is very strange. I'd suggest opening a support ticket with Microsoft.

Was this reply helpful? Yes No
Hamish Sheild 3,005 Most Valuable Professional on at

Like (0)

Report

Hi @User3324234_BRD , did you have any luck in resolving this? I am having a very similar issue after converting Prod to Sandbox and also changing the URL. It worked fine yesterday immediately after the change but today I am getting the same errors in Power Automate. I am also not able to add a Dataverse action to Power Automate.

I have raised a ticket with Microsoft also. Will report back if I get an answer

Was this reply helpful? Yes No