Finance | Project Operations, Human Resources, ...

Cannot edit a record in LastValue (SysLastValue) - Error in multi threaded batch job

(0) Share

Report

Posted on by PK_Dax365

Hi All,

I am getting below error during batch job execution,

Cannot edit a record in LastValue (SysLastValue).An update conflict occurred due to another user process deleting the record or changing one or more fields in the record.

I tried with table.reread() before updating the record but it is not helping.

Note : We have a mitithreaded process when create/update is happening in UserInfo, SysUserInfo, SecurityUserRole tables.

Any help would be highly appreciated.

Thank you!

Categories:

Dynamics 365 Finance

Microsoft Dynamics AX

I have the same question (0)

All responses (2)

Answers (0)

Jonas "Jones" Melgaard 4,980 Most Valuable Professional on at

Like (0)

Report

Hi @PK_Dax365,

What exactly are you doing, what are you rereading?
For me it sounds like you are updating the same record in all of your batch threads, then I'd say it's expected that it complains about update conflicts.

Was this reply helpful? Yes No
Suggested answer

Saif Ali Sabri 2,351 Super User 2025 Season 2 on at

Like (0)

Report
This error occurs due to concurrency conflicts when multiple threads try to update the SysLastValue table simultaneously. Since SysLastValue is used to store the last used values for different processes, concurrent updates can lead to conflicts.
Solution:

Use RecordSelectLock for exclusive access
Before updating SysLastValue, lock the record to prevent conflicts:

x++

ttsBegin;
SysLastValue lastValue;
select forUpdate lastValue
where lastValue.ElementName == 'YourElementName';

if (lastValue)
{
lastValue.Value = 'YourUpdatedValue';
lastValue.update();
}
ttsCommit;

2. Retry logic in case of conflicts
Implement a retry mechanism using retry keyword to handle intermittent failures:
x++

int retryCount = 3;
while (retryCount > 0)
{
try
{
ttsBegin;
select forUpdate lastValue
where lastValue.ElementName == 'YourElementName';
if (lastValue)
{
lastValue.Value = 'YourUpdatedValue';
lastValue.update();
}
ttsCommit;
break;
}
catch (Exception::UpdateConflict)
{
retryCount--;
if (retryCount == 0)
{
throw error("Update conflict on SysLastValue. Please try again.");
}
}
}

Ensure transactions are correctly scoped

Avoid holding locks for long durations.

Only update SysLastValue when necessary.

Run batch jobs with a single thread if SysLastValue updates are critical.

By implementing these solutions, you should reduce update conflicts and ensure smooth batch processing.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Cannot edit a record in LastValue (SysLastValue) - Error in multi threaded batch job

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

Cannot edit a record in LastValue (SysLastValue) - Error in multi threaded batch job

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates