Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / OccEnable property cha...
Finance | Project Operations, Human Resources, ...
Suggested answer

OccEnable property changed to "NO" on table any impact on data - AX 2012

(0) ShareShare
ReportReport
Posted on by Akbarpasha

Hi All,

Is there any impact on data if we change the table property "OccEnabled" to "No" as by default it is "Yes".

I have gone through the docs about this property, but wanted to know is there any impact on the data.

We are getting the below error while data is updating from CRM to AX, when we changed the "PurchLine" table property "OccEnabled" to "No", the issue is resolved.

"Cannot edit a record in Purchase order lines (PurchLine).

An update conflict occurred due to another user process deleting the record or changing one or more fields in the record."

Please advice us.

Regards,

Akbar 

  • jannawangD365 Profile Picture
    jannawangD365 on at
    RE: OccEnable property changed to "NO" on table any impact on data - AX 2012

    Hi Akbarpasha.

    disable OCCEnable might impact the performance and I would suggest make the change as a one-time thing.

  • Suggested answer
    Sergei Minozhenko Profile Picture
    Sergei Minozhenko 23,089 on at
    RE: OccEnable property changed to "NO" on table any impact on data - AX 2012

    Hi Akbarpasha,

    Not sure what you mean by the impact on data, but OCCEnabled is more about when to lock records for changes. If you change the property to No, you will have more locking issues and delays in processing because of this.

    I recommend to keep settings as by default (Yes) and review the integration process, why it works with the same records at the same time.

  • Akbarpasha Profile Picture
    Akbarpasha on at
    RE: OccEnable property changed to "NO" on table any impact on data - AX 2012

    Hi Ludwig,

    In Purchase order lines , the line status is "Open order" this line came from CRM, we are not creating any Purchase order in AX, Orders are coming from CRM, when first time order flown from CRM to AX , purchase line status is "Open order", when next time CRM perform some action the order line status is getting "Received" , this time only that error is coming, so changed the table property "OccEnabled" to "YES" and the issue is resolved.

  • Ludwig Reinhard Profile Picture
    Ludwig Reinhard Microsoft Employee on at
    RE: OccEnable property changed to "NO" on table any impact on data - AX 2012

    Hello Akbar,

    Can you possibly provide us some additional information?

    What process/tables and systems are you operating with and what is the underlying business requirement.

    You directly jumped into very much details, which makes us difficult to understand the overall issue.

    Many thanks and best regards,

    Ludwig

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans