topic Re: Can't create field indexes on feature layer with related table in ArcGIS Online Questions

Can't create field indexes on feature layer with related table

MattCashen — Wed, 04 Feb 2026 16:11:29 GMT

I have a feature layer in AGO that is published every day with a related table. I have a script set up that creates new field indexes on the feature layer after it is republished. I noticed today that the field indexes weren't being created. When I run the script, I get the error "Exception: Unable to add feature service layer definition. A full-text index cannot be created on the table or indexed view because duplicate column 'FIELDNAME' is specified" I assumed this was a problem with the script, but when I go into AGO and try and manually create the field index it tells me that an index can't be created. I'm guessing this may have been happening since the last AGO update and I only just noticed. I'm fairly certain it is being caused by the related table as I don't have this issue with other layers that don't have related tables. Is this a bug within AGO or is this just a limitation I'm going to have to deal with going forward?

Re: Can't create field indexes on feature layer with related table

RPGIS — Wed, 04 Feb 2026 17:20:17 GMT

One thing you can try as a simple test is to create a very small copy of the datasets/tables and run the script on that small sample to see if it is the script trying to match a field that might be duplicating. If it doesn't then it might be a potential issue with the layer possibly.

Another option is to overwrite the layer and see if that republished dataset/tables fixes the indexing issues.

Re: Can't create field indexes on feature layer with related table

MattCashen — Wed, 04 Feb 2026 18:32:17 GMT

@RPGIS

Thanks for the suggestion to overwrite the layer. The layer gets overwritten every day via a script and after reading your comment I noticed that it took over twice as long to run this morning than usual. So I went ahead and ran the script again. The indexes are now working. There must've just been an issue when the script originally ran this morning.