Hi Luigi,
I checked the batch job that had the UniqueID check. It is not checking for the ObjectID. I'm going to submit a request to update the message to remove ObjectID.
So you have some features with duplicate GFIDs. You may want to check if they are duplicate features within the same feature class. If so, you can delete one feature. If not, then you would have to udpdate one of the feature's GFID. Does Defense Mapping or Production Mapping have a tool to do that?
Regards,
michellej.
Hello Luigi,
Out of curiousity, what version of Defense Mapping are you working with. Earlier you stated that you are on ArcMap 10.1, but have you installed any service packs or updates? I was looking at the batch job that you are discussing here and noticed that the check changed at 10.1 Service Pack 1 QFE 1. The check that is causing the issue is the MGCP_TRD3_Duplication_Checks.rbj.
That rbj is no longer checking the OID field of the feature classes rather it is making sure that the GFID field is unique for each feature. There should be two ways for you to test this; the first would be to edit the check so that it looks like the following image.
[ATTACH=CONFIG]31087[/ATTACH]
The second option would be to update your software to the latest version and test to see if this resolves the issue that you are seeing.
If you would like more direct contact please feel free to email me at jmoore@esri.com, I am part of the Defense Mapping team and would be able to provide support with this issue.
Thank you,
Jeremiah Moore