We are using file geodatabases along with Micorsoft teams one drive. The beauty of this is that users all have the need files on their C drives and it is super fast. When a user edits a file it automatically gets updated on everyone elses PC. When we try going off the network it is painfully slow. So hence why we are not using Enterprise GDB along with the additional cost.
Where I am running into an issue is that if two users are trying to create points at the sametime in a feature class with the file geodatabase and then save the point it saves on their version on the C drive. However, because they both are using the same object ID which everyone makes it to the server gets posted. So if both users create a point because objectID goes in incremental order it would be objectID #7 for example. Hence the overwriting.
As I understand it you cannot have two users writing to the same feature class at the same time even if they both were using the same geodatabase.
So my question: Is it possible to change the objectID from being incremental to something else like maybe a globalID or allow us to programmatically assign the ObjectID. Can I make it so the ObjectID is not the unique identifier but something else would be. How can I work around this issue?