Finance | Project Operations, Human Resources, ...

occenabled property in table in D365FO

(0) Share

Report

Posted on by CU10121822-0

388

Hi Team,

My question is in D365FO , PCC will work in D365FO?

Pls let me know how the OCCEnabled will work in D365FO in real scenario.

I mean If i set to Table property - OCCEnabled set to Yes, or No.

Pls explain. thanks1

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Subra 1,467 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @CU10121822-0

The below link has details information about the OCC and usage as well.

https://d365ffo.com/2021/04/19/d365ffo-ax-optimistic-concurrency-control/

Thanks,
Subra

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
CU10121822-0 388 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Subra, I have already go through this. Not understood. Thats is the reason i posted here.

Pls let me know your thoughts. If you know ...

thanks!

Was this reply helpful? Yes No
Suggested answer

Subra 1,467 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi

Please find the below scenarios and let me know if you need any clarification on this.

PCC will work in D365 but we have to implement that and by default all the table will enabled as OCC.

With OCC enabled, D365FO checks whether a record has been modified by another user between the time it was read and the time it is updated. This is done using the system-managed RecVersion field. If the record has changed, D365FO throws an update conflict instead of overwriting the other user's changes.

Thanks,
Subra

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
Suggested answer

Subra 1,467 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi

Additionally, please find the real time example as well.

We have the below recod in the table Employee

Employee Salary RecVersion

EMP001 50,000 100

ScenarioUser A

Opens the record.

Salary = 50,000.

User B

Opens the same record.

Salary = 50,000.

User B updates the salary to 55,000 and saves.The record becomes:

Employee Salary RecVersion

EMP001 55,000 101

Now User A tries to save a salary of 52,000.Because the RecVersion has changed (100 → 101), D365FO detects that another user has modified the record and throws an update conflict instead of overwriting User B's changes.ScenarioUser A

Opens the record.

Salary = 50,000.

User B

Opens the same record.

Salary = 50,000.

User B updates the salary to 55,000 and saves.The record becomes:

Employee Salary RecVersion

EMP001 55,000 101

Now User A tries to save a salary of 52,000.Because the RecVersion has changed (100 → 101), D365FO detects that another user has modified the record and throws an update conflict instead of overwriting User B's changes.

Thanks,
Subra

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No