I know how to recognize an Indexed Field Name by the the asterisk (*). And, I know how to add an Index to a field and remove it.
But, how do Indexed Field Names originate? In other words, how do they become indexed in the first place?
I ask because, I can have a Field that is indexed, but when I share that layer with someone else, it may not be indexed when they open it.
Thanks
You can create them or some other actions can create them e.g. search settings or filters.
I don't believe the fields are indexed by users. It may be because they are not the owner they don't see the * or something.
...Hmmm, I may be misunderstanding your response. Fields CAN absolutely be Indexed by a User using the "Add Attribute Index" tool. Users can also remove it using a tool.
My question, however, is about Fields that become Indexed WITHOUT User involvement -- and, I'm referring to fields other than the 'ObjectID" field.
It appears that some tools will automatically do this to certain fields as seen by the Output layer or table. ...That's what I don't quite understand. ...Does anybody know more bout this?
Oh OK, thanks for the clarification.
Yeah, nothing I'm referring to is hosted online.
I am taking a Standalone CSV Text file and Exporting it into a Geodatabase where it becomes a File Geodatabase Table ...During that process, one of the Fields became automatically Indexed. For some reason it indexes the 'Name' field which stores values for State names.
And, because of that, it will not Join correctly with the associated State spatial layer. ONLY the last record (Wyoming) joins; al other values are <Null>.
If I remove the Index it will work. But, I'm at a total loss as to the real "cause" and what is really going on here?
...I've solved the problem, I'm just trying to figure out the exact "cause".
But, I wouldn't think a field named 'Name' would cause problems -- that field name is used everywhere in GIS without problems.
I've also experienced this problem with a field named, 'GEOID".