Is OCC and PCC still worked in D365FO

(1) Share

Report

Posted on by CU10121822-0

1,056

Hi team,
Is still OCC &PCC worked in D365FO. Is there any specific setup required to use them. I have do research but not yet found appropriate answer.

Please advise, thanks

Categories:

Dynamics 365 Finance

All responses (3)

Answers (0)

Sort by

Suggested answer

Martin Dráb 240,744 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

For reference, the question is about optimistic and pessimistic concurrency control.

The answer is yes, both options are available in F&O. PCC is AX from the very beginning and OCC was introduced in Dynamics AX 4.0.

You can control the type of concurrency control on the table level (OccEnable property) or for individual queries (pessimisticLock keyword, concurrencyModel() method etc.).
CU10121822-0 1,056 on at

Like (0)

Report
Copy link

Link copied!

Hi , what I understood…
OCC-
select forUpdate salesTable
where salesTable.SalesId == 'SO-1001';
salesTable.CustGroup = 'RETAIL';
salesTable.update();
If both user trying to update at same time. It can detect the concurrency conflict.

PCC-
ttsBegin;
select pessimisticLock forUpdate inventSum
where inventSum.ItemId == 'ITEM-A';
if (inventSum.AvailPhysical >= 7)
{
inventSum.AvailPhysical -= 7;
inventSum.update();
}
ttsCommit;
Here The first transaction obtains a lock on the record.
The second transaction has to wait until the first transaction completes.

concurrencyModel()- It returns the table's configured concurrency model.

Am I correct?

Pls advise, thanks
Suggested answer

Martin Dráb 240,744 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Your understanding is only partially correct.

In your example with InventSum, you forgot to take OccEnabled property into account. It's No in this case, therefore queries to InventSum are pessimistically-locked by default and using pessimisticLock in a query has no effect. It would make sense for a table with OccEnabled=Yes.

You're also wrong about concurrencyModel() method. If you look at the method signature or its documentation, you'll find that it accepts a parameter, therefore you can use it to change the concurrency model at runtime. You can use Find references on ConcurrencyModel EDT to find examples in the application. One of them is in AccountingDistribution::find():

public static AccountingDistribution find(
AccountingDistributionRecId _recId,
boolean _forupdate = false,
ConcurrencyModel _concurrencyModel = ConcurrencyModel::Auto)
{
AccountingDistribution accountingDistribution;
;
accountingDistribution.selectForUpdate(_forupdate);
if (_forupdate && _concurrencyModel != ConcurrencyModel::Auto)
{
accountingDistribution.concurrencyModel(_concurrencyModel);
}
...