Can branch versioned tables effectively support multi-user editing scenarios?

[angiexx1]

I have a non UN table and it is branch versioned table and its attached to the attribute rule, so whenever there is a yes /no in the table the attribute rule evokes the process , now can i do this for multi user scenario? if one person has it yes and the tool works and when its done it goes back to no, so if its branch versioned table, will it support multi user, without disrupting the original flow?

[MikeMillerGIS]

If the table is branched and published in the same Feature Service as the UN, it can be in the same version as the UN features, so when they are in a UN version, the table will be in the same version, so their value is only in that version.  Sounds like it should work.

[angiexx1]

so if i develop a tool which incorporates a versioned table, will it be maintained for the particular user? Like the edits made out of that tool will be maintained within the versioned table and the versioned user right? when this used across multi user it wont be a problem

[MikeMillerGIS · Accepted solution]

Yes, but will also be posted to default.  Just need to think through how to prevent conflicts.

[angiexx1]

okay! i was wondering what could be the potential conflict that might arise