Hi all, I’m running into an issue in my Dynamics 365 Dataverse environment after a recent update.
I am a Global Admin and Environment Maker.
I can create new flows successfully in this environment.
However, when the new flow runs and tries to access a Dataverse table (e.g. using “List rows” or “Get row by ID”), the run fails with a generic IIS error:
404 - File or directory not found. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
The connection to Dataverse appears established (no reconnect required).
The environment URL (https://.....crm4.dynamics.com/) loads fine in the browser.
Older flows that were created before the update still run without issue.
This only affects newly created flows.
My question:
Has something changed in the way new Dataverse connections/connection references are provisioned that could cause them to point to the wrong URL?
Could this be related to the environment update that introduced the AppInsights Id environment variable (though we don’t use Application Insights)?
Has anyone else seen new flows fail with 404 when calling Dataverse tables while old flows still work?
1. I would go to the table named ta_XXXX and look if there is a column called recordid that has that value
2. Please swap to the old UI, turn off the new one. Save it there, run it again, see if it works please
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Share
Report
All responses (
Answers (
49,344
