Latest Contributions by WWalker

The documentation for IFieldChecker states that the interface checks for errors in field names.  Specifically, it renames the OID field to "ObjectID" based on 4 cases.  When creating a standalone table in a geodatabase, using the IFieldsEdit interface to create the OID field, there are no requirements on what constitutes a valid name for the OID field.  However, if the OID field is not named "ObjectID" when fed to the FieldChecker, it is changed to "ObjectID".  What constitutes a valid OID field name?  Are there any restrictions on valid OID field names in a geodatabase?  Will naming my OID field something other than "ObjectID" cause issues?  See relevant code below:     IFields fields = new FieldsClass();     IFieldsEdit fieldsEdit = (IFieldsEdit)fields;     fieldsEdit.FieldCount_2 = 10;     IField field = new Field();     IFieldEdit fieldEdit = (IFieldEdit)field;     fieldEdit.Name_2 = "MyOidFieldName";     fieldEdit.Type_2 = esriFieldType.esriFieldTypeOID;     fieldsEdit.set_Field(0, field);     // Add other fields here...     // use IFieldChecker to create validated fields collection     IFieldChecker fieldChecker = new FieldChecker();     IEnumFieldError enumFieldError = null;     IFields validatedFields = null;     fieldChecker.ValidateWorkspace = (IWorkspace)fws;  //fws = my feature workspace     fieldChecker.Validate(fields, out enumFieldError, out validatedFields);    //<--my OID field name is changed to "ObjectID" arcobjects 10.4.1‌objectid‌fieldname‌ ... View more

I've set up a PostgreSQL server to house production geodatabases, where 50+ analysts will edit data on various databases.  I've set up a 'sde' login, a 'data_owner' login, and an 'editor' group.  It is desirable to track user edits on some of our databases.  I would like to use our acitve directory credentials to allow users to login without requiring a separate login.  Unfortunately, our domain uses a format firstname.lastname for users, and this is not wrapped in double quotes when ArcMap communicates with the pg server.  So when a john.doe tries to select more than 100 features, or any other act that will need to make use of the log file tables, an error occurs.  Using our current active directory names will not work. After reading some PG documentation, I realized I might be able to map our illegal OS user names to legal PG user names.  (e.g. john.doe authenticates as john_doe).  After initial tests, I have been unable to get this to work either.  I don't know if this is due to, again, unseen communications between ArcMap and PG.  Is something like this even possible in the ESRI ecosystem, or am I just trying to fit a round peg in a square hole?  Short of creating a pg user for every os user, what, if any, options do I have for using our active directory? ... View more