I have a JOB queue running in Background which fetches data from Dynamics 365 CRM on job table but I dont know sometime when I am working on puchase order table it is giving errror that "we cannot save your data due to a

(1) Share

Report

Posted on by Pragya752

210

JOB queue running in Background which fetches data from Dynamics 365 CRM on job table but I dont know sometime when I am working on puchase order table it is giving errror that "we cannot save your data due to a record is modified in another table by another transaction"

Error: We can't save your changes right now, because a record in table 'Job' is being updated in a transaction done by another session. You'll have to wait until the other transaction has completed, which may take a while. Please try again later.Business central

All responses (3)

Answers (1)

Pragya752 210 on at

Like (0)

Report

RE: I have a JOB queue running in Background which fetches data from Dynamics 365 CRM on job table but I dont know sometime when I am working on puchase order table it is giving errror that "we cannot save your data due to a

Its not happening everytime.It gives error sometimes and sometimes not.
Verified answer

YUN ZHU 75,848 Super User 2024 Season 2 on at

Like (0)

Report

RE: I have a JOB queue running in Background which fetches data from Dynamics 365 CRM on job table but I dont know sometime when I am working on puchase order table it is giving errror that "we cannot save your data due to a

Hi, as far as I know, there is no job table in the standard connector with CRM. Is this a custom one? If yes, please check your code, you can try to debug to see where this problem occurs.

Hope this can give you some hints.

Thanks.

ZHU
Suggested answer

Tech-Lucky 815 on at

Like (0)

Report

RE: I have a JOB queue running in Background which fetches data from Dynamics 365 CRM on job table but I dont know sometime when I am working on puchase order table it is giving errror that "we cannot save your data due to a

may be because Purchase is connected with the Job Table in certain cases so there might be Job table modifying in backend and that is why this lock table occurs when both the processes modify the job table at the same time.