Canvas App - Dynamics 365 FinOps - Couldn't update a record in Dynamics 365 Finance and Operations from a canvas app with the Dynamics 365 FinOps Connector

(0) Share

Report

Posted on by Power Platform Comm...

Hello PowerApps Community

I suspect an issue with the D365 F&O Connector in PowerApps and Power Automate.

I have a canvas app that retrieves various data directly from D365 F&O. Work with this data in the app (edit and update) and store it back into the D365 F&O. This has always worked well so far. But since a while I get the error.

"The specified record was not found... 404 File or directory not found. The resource you are looking for might have been removed, had its name changed or is temporarily unavailable."

I've created a small showcase to demonstrate the behaviour.

After sending it to Dynamics 365, I get the following error...

We have already tried everything in the D365 F&O. The Data Enity rebuilt, the Entity List refreshed. From the D365's point of view, everything looks good.
We also used an Azure Function to address the specific entity and writing back to D365 F&O works in that case.

But as soon as I try to do it with the PowerApps/Power Automate Connector I always get error message above.

Does anyone of you have an idea how I can solve this problem?

Thanks & Br
Jürgen

I have the same question (0)

All responses (2)

Answers (0)

Power Platform Comm... 8 on at

Like (0)

Report

Good morning!

I doubt it's an issue with the coding of the connector itself. We could use more information on the problem you're having; for example, is the connector retrieving the records ok in your app, but just not updating when you hit the "Send to Dynamics" button? That would point to a problem in your call to the write function of the connector; maybe the name of the database isn't entered/retrieved quite right, or the record ID isn't entered/referenced properly in your call. There's a lot that could cause this issue.

But off the cuff there are a couple things you can try:
1. Refresh the connection inside your PowerApp; probably the most obvious but I mention it anyway.
2. Check for "Red Flags" from the doctor inside PowerApps and follow up on the suggestions.
3. If you recently had a server update, then this problem occurred just after and the refresh above didn't work, you can try re-creating your connection inside your PowerApp. Yes this sucks and is tedious, but it has solved problems for me before that were created by updates to servers or the Power Platform programs.

Good luck!

Was this reply helpful? Yes No
André Arnaud de Cal... 301,146 Super User 2025 Season 2 on at

Like (0)

Report

Hi Jürgen,

Did you find your answer already? I just came across your question.

If not, continue reading. If the default company of the user does not match with the company used in the Power App, you might get this error.

Was this reply helpful? Yes No