Hi Lukasz.

I haven’t tried with the offline sync. Sequence might be skewed on the offline scenario, where the actual request is happening when it’s syncing to the server. Duplicates I think will less likely to happen, as the sync is happened after the fact.

Great stuff. Do you know how this works in conjunction with offline sync. Especially in the sequence number scenario?
Does it create new numbers on sync or leaves potential duplicates.

Seed is not solution aware, you might need to readjust the seed in the next environment. Here is an excerpt from Jonas’ finding: Note that setting the seed only changes the current number value for the specified attribute. It does not imply a common start value for the attribute. Thus the seed is not solution aware to be transported between environments. To set the starting number after a solution import, the `SetAutoNumberSeedRequest` must be called in the target environment.

AFAIK, no. It applicable to all records. 3rd party solution might be able to do the conditional one.