We have a feature class that has a primary key constraint(not OBJECTID) on it's database table. This field also has an auto incrementing trigger (BEFORE INSERT)
When our users try to create/add features to this class using arcmap, since it's a non nullable number field, ArcMap adds a default value to it (0), so the second time it tries to put 0, it violates the pk constraint. Not only that but it overwrites the BEFORE INSERT trigger by putting 0 after it triggered.
I haven't been able to workaround this even with indexes.
An idea that I thought could work was making a AFTER INSERT incrementing trigger, or an ON UPDATE trigger that only works if the pk values is 0, but I'm not sure how to make none of these, or if that's even possible/necessary.