Microsoft Dynamics AX (Archived)

An example where OCC is turned off ?

(0) Share

Report

Posted on by San Artham

3,175

Hi All, i am curious to know what might be the business scenario where OCC could be turned off ?

Thanks,

San

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (1)

Bilal Issa 4,370 on at

Like (0)

Report

Hi ,

when OCC is off the record is locked when it is fetched from the database, so it was used in Dynamics Ax 3.0 , we could use in a scenario where users are not allowed to see a record if another user is viewing the record.

Regards,

Bilal

Was this reply helpful? Yes No
San Artham 3,175 on at

Like (0)

Report

Thanks for the response Bilal. could you think of a real time Business scenario for this ?

Thanks,

San

Was this reply helpful? Yes No
Verified answer

Ivan (Vanya) Kashperuk on at

Like (2)

Report

There are a bunch of tables in standard application that are not OccEnabled.

A good example is InventSum/InventSumDelta, where a failure to update the record is very expensive to attempt again, and potentially the data could already be different. So we ensure it happens strictly one by one.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Enforce optimistic concurrency in situations where the optimistic model would improve concurrency and throughput when compared with the pessimistic model. For example, where more records are locked than are actually updated. Use OCC if a table is never updated or deleted from code but updated only by a client through a form.

Use pessimistic concurrency under the following conditions:

• Serialization logic exists that requires an update lock on a record in the database. The serializing select statement should include the pessimisticLock keyword. The logic fails if the OccEnabled property is changed on the table.

• Update conflicts are likely (otherwise, extra time is used on retries).

If only a few business scenarios require a different concurrency model rather than the one already set on the table, handle the scenarios individually by applying a line of statement-level concurrency code.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Please refer following link for more details

msdn.microsoft.com/.../bb190073.aspx

Please verify and update us if this helps you.

Was this reply helpful? Yes No
Rob Klaproth 1,730 on at

Like (0)

Report

Well, several years later, this issue still occurs, although for me this is the FIRST time I've ever had this issue in all of the 100+ GP upgrades I've done. Upgrading from 2015R2 to 2018R2.

Just inserted the -1 into all of the company ID's that were missing it (in this case 18, 11, and 20):

insert into dynamics.dbo.sy20020 values ('-1', '18', '0')
insert into dynamics.dbo.sy20020 values ('-1', '11', '0')
insert into dynamics.dbo.sy20020 values ('-1', '20', '0')

No more error. Why does this happen?

Was this reply helpful? Yes No
Martin Dráb 237,976 Most Valuable Professional on at

Like (0)

Report

Rob, it looks like you're in a completely wrong thread - different topic, different product (Dynamics AX, not Dynamics GP).

Was this reply helpful? Yes No
Rob Klaproth 1,730 on at

Like (0)

Report

Martin you're right. For some reason there is a problem with the community.dynamics.com - could you escalate to Microsoft to see what's going on? This is the second time its happened where I'm viewing a GP thread, and I reply, but it posts it in another forum. Last time I replied and it posted it in CRM. I've never even been in the AX or the CRM forums, so I'm not sure why it's posting my GP replies to a different place.

Rob

Was this reply helpful? Yes No