SAC - Data locks on this model prevented the changes from publishing (data action script, one user)

[Guillaume_P]

Hello experts.

I'm facing a very frustrating issue with a data action script transferring records from a model to another.

Only one user has the error message below : 

The results of the data action "abcde" could not be published on version "2025_B1". You can still try to do a partial publish manually. Data locks on this model prevented the changes from publishing.

While for several other users the script runs fine.

(of course parameters are the same in each run)

Data locks are obviously managed the correct way (if not the case all runs would fail except for the admin user).

My user (with the planning professional licence) has of course no issue.

What could be different for user XXXX ? What would explain this difference of results ?

(I am considering opening a support ticket).

Any relevant investigation tricks would be welcome.

Thanks in advance & Regards.

G.

[William_Yu1 · Accepted solution]

One possibility, user xxxx has unique data it's private/public edit which resulted in a slightly different target data region. Just a guess though...

[Guillaume_P · Accepted solution]

Hello William, and thank you for the feedback.

I'm not sure to understand what you mean : 

at least the number of posted records is the same between a failed and a successful run

Are you talking about records that may already be present in the destination model, and not yet published ?

(and the data action script run would also publish those problematic records ?)

Regards.

G.

[William_Yu1 · Accepted solution]

Ok, from the records count it seems the same between users. But still there are chance that they are on different data points( considering there are overlaps between different steps: pulished records smaller than total recors combined from 4 steps). And you are right, existing records in public edit in target version of user xxxx might be another potential reason, publish is always for the whole version but not for the data region populated by current data action execution.

[Guillaume_P · Accepted solution]

"And you are right, existing records in public edit in target version of user xxxx might be another potential reason, publish is always for the whole version but not for the data region populated by current data action execution."

-> it was the issue ... an existing private version in the destination model was preventing the publishing process to succeed. Good to know even if it is not the default behaviour I would have expected.

Thanks again for helping and have a nice day.