Finance | Project Operations, Human Resources, ...

Error when posting the journal integration

(7) Share

Report

Posted on by SA-03040615-0

Hi,

I am facing an issue while posting the Project Operations Integration Journal in Dynamics 365 Finance & Operations with Dual-write enabled.

When I try to post the journal, the posting fails with the following error:

Unable to write data to entity msdyn_actuals. Writes to ProjActualsImportEntity failed with error message Request failed with status code BadRequest and CDS error code: 0x80040265 response message: Actuals cannot be updated. Please use the "Correct Entries" functionality to perform any corrections through a correction journal.

We are using Project Operations integrated with Finance & Operations through Dual-write. The error occurs during journal posting in F&O. The dual-write map is set the version 1.0.20 as per ms docs.

Please suggest a fix for this problem.

Thank You.

Categories:

Dynamics 365 Finance

Dynamics 365 Human Resources

Dynamics 365 Project Operations

I have the same question (0)

All responses (10)

Answers (0)

Sort by

Suggested answer

Alireza Eshaghzadeh 15,220 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Hi @SA-03040615-0,
This error is coming from the Dataverse Actuals table (`msdyn_actuals`). In Project Operations, actuals should not be updated directly after they are created. If an actual needs to be corrected, it must be done through the supported “Correct entries” functionality / correction journal.
So I would first check whether the integration journal line is trying to update an actual that already exists in Dataverse, instead of creating/synchronizing a valid new actual. This can happen if the same transaction was already processed, partially synced, or if the dual-write payload is treated as an update.

Was this reply helpful? Yes No
SA-03040615-0 16 on at

Like (2)

Report
Copy link

Link copied!

I've checked the payload by pausing the Actual Dual-Write entity. When posting on F&O it's sending the response to CRM. The record is queued. So, I need to set the mapping direction for Dataverse to F&O, Am I right?

Was this reply helpful? Yes No
André Arnaud de Cal... 305,815 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Yes, the actuals should only be sent to F&O, not vice versa. You can read more in the documentation: Project estimates and actuals integration | Microsoft Learn

Was this reply helpful? Yes No
Assisted by AI

SA-03040615-0 16 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Thank you for your response.

We are currently facing another issue. After resuming the entity from a paused state, the Actuals are not syncing. I have tried stopping and restarting the process, and even reset the link, but the Actuals are still not syncing in Finance & Operations.

I checked the Out of Sync Actuals page and corrected the errors listed there. However, the job is still not syncing any data to Finance & Operations. Other data, such as Project Invoice Proposals, are syncing but with zero amounts.

At this point, I am unable to identify the root cause of the problem.

Could you please suggest a solution for this issue?

For reference, I am working in a Tier-1 environment.

Was this reply helpful? Yes No
Puneet Darji 170 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Same issue being faced by me in tier 1 env.

@André Arnaud de Calavon - The article you mention, in the same article its mentioned that once you post the integration journal it will update back the dataverse, in this case when its trying to update we are presented with the error as mentioned by OP.

Was this reply helpful? Yes No
André Arnaud de Cal... 305,815 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

When looking at the screenshot again, some journals are posted and some not. What is the difference here? Are there some corrections done before posting the journal?

Was this reply helpful? Yes No
Darji Puneet 4 on at

Like (1)

Report
Copy link

Link copied!

Hi,

No changes are being made to the journal, they are getting posted as is.

Was this reply helpful? Yes No
André Arnaud de Cal... 305,815 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

In case some journals are posted and some not, there should be a difference between them. Are you able to find some correlation? If not, you can create a ticket for Microsoft Support.

Was this reply helpful? Yes No
Darji Puneet 4 on at

Like (0)

Report
Copy link

Link copied!

Hi,

What we have observed is that, hour lines are getting posted fine, its only expense line which is having the issue. In other environment which we have no such issue. I believe something is missed cannot pinpoint. Will raise the ticket.

Thanks!.

Was this reply helpful? Yes No
Assisted by AI

Saif Ali Sabri 2,701 Moderator on at

Like (0)

Report
Copy link

Link copied!
The error “Actuals cannot be updated. Please use the ‘Correct Entries’ functionality…” is raised because Project Operations actuals in Dataverse (msdyn_actuals) are immutable once created. Dual-write integration journals in Finance & Operations must always create new actuals, not attempt to update existing ones.
From your description, the following deeper analysis applies:
🔍 Root Cause Analysis

Direction mismatch in dual-write mapping: The ProjActualsImportEntity should flow Dataverse → F&O, not the other way around. If the mapping is bi-directional or incorrectly set, F&O posting may attempt to update Dataverse actuals, which is unsupported.

Expense line behavior: You observed that hour lines post successfully, but expense lines fail. This indicates that expense actuals are being treated as updates to existing Dataverse records rather than new inserts. In another environment where mappings are correct, this issue does not occur.

Paused/resumed entity state: When the entity was paused and resumed, queued records may have lost synchronization context. This can cause “out of sync” errors even after corrections are applied.

Tier‑1 environment limitations: In Tier‑1 (sandbox) environments, dual-write jobs sometimes fail silently or skip records due to throttling or incomplete configuration. This explains why invoice proposals sync with zero amounts.

🧩 Recommended Solutions

Verify mapping direction: Ensure that the Actuals dual-write map is set to Dataverse → F&O only. Disable updates from F&O to Dataverse for msdyn_actuals.

Check expense line mapping: Compare the expense line mapping with the working environment. Look for differences in field direction (insert vs update) or missing transformations.

Clear and resync out-of-sync records: Use the Out of Sync Actuals page to fully clear failed records, then re-run synchronization. Partial corrections may leave stale references.

Validate correction journal usage: If corrections were attempted in Dataverse, ensure they were done via Correct Entries. Any manual edits to actuals will block synchronization.

Test in higher-tier environment: Since Tier‑1 can mask integration issues, replicate the scenario in Tier‑2 or UAT to confirm whether the problem is environmental or configuration-based.

💡 Additional Tip
For expense lines specifically, export the dual-write payload (JSON) during posting and compare it against a successful environment. If the payload contains an update operation instead of create, the mapping direction is incorrect. Adjusting the dual-write map to enforce create-only behavior for expense actuals should resolve the issue.

Was this reply helpful? Yes No