topic Query distinct fail on 10.5 with field longer than 22 char in ArcGIS REST APIs and Services Questions

Query distinct fail on 10.5 with field longer than 22 char

FrancisGagne — Fri, 13 Oct 2017 18:22:38 GMT

I'm trying to get the domain of value for a field with 23 characters and it fails.

Here is the query I'm doing on 10.5:

queryf=json

&where=1=1

&returnGeometry=false

&spatialRel=esriSpatialRelIntersects

&outFields=UTILISATEURMODIFICATION

&returnDistinctValues=true

&orderByFields=UTILISATEURMODIFICATION

It returns

{"error":{"code":400,"message":"Failed to execute query.","details":[]}}

When I remove the returnDistinctValues, it works fine but I get every records.

I tried the same exact query on 10.3 with the same MXD and data and the returnDistinct works fine.

Here is the log from the server:

Geodatabase error: Attribute column not found [42S22:[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name 'UTILISATEURMODIFICATIO'.] .

It seems the last characters are truncated. I have the same problem with other fields:

Geodatabase error: Attribute column not found [42S22:[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name 'INDICATEURPROTECTIONGE'.]

Re: Query distinct fail on 10.5 with field longer than 22 char

VinceAngelo — Fri, 13 Oct 2017 18:44:26 GMT

If you prepend the column name with "DISTINCT ", the field contents becomes 31 characters long, which happens to be the maximum column name length. Very curious.

- V

Re: Query distinct fail on 10.5 with field longer than 22 char

FrancisGagne — Fri, 13 Oct 2017 18:54:22 GMT

Does the limit have reduced since 10.3?

Re: Query distinct fail on 10.5 with field longer than 22 char

VinceAngelo — Fri, 13 Oct 2017 18:57:55 GMT

No, the underlying ArcSDE API constant, set to 32 (but not counting the string terminator) has not changed since SDE 3.0.

Re: Query distinct fail on 10.5 with field longer than 22 char

MicahBabinski — Fri, 13 Oct 2017 19:01:51 GMT

What is the character length of your request URL? Are you using GET or POST?

Re: Query distinct fail on 10.5 with field longer than 22 char

FrancisGagne — Thu, 24 May 2018 19:04:37 GMT

Is there any update on this? I managed to get around by querying my data directly but some others might not be able to do that easily.

I just tried again on the service and I still have the same problem with long fields.

Thanks,

Re: Query distinct fail on 10.5 with field longer than 22 char

CherylHagevik — Wed, 17 Oct 2018 15:10:14 GMT

This appears to be unexpected behavior when querying with Return Distinct Values. This issue has been reported to the Product Team for further investigation as BUG-000117499 : Query fails at REST with 'Unable to perform query operation' when returning Distinct Values with outField that has name over 22 characters long. Hopefully we will see this issue addressed soon! Thanks, Cheryl

Re: Query distinct fail on 10.5 with field longer than 22 char

WillStafford — Fri, 14 Feb 2020 11:55:32 GMT

Has there been an update on this Vince. Is it repaired. It was still active in 10.6.1 . Setting up a 10.7.1 or 10.8 back end soon.

Will

Re: Query distinct fail on 10.5 with field longer than 22 char

VinceAngelo — Fri, 14 Feb 2020 16:37:57 GMT

Cheryl reported the bug number - BUG-000117499 - which does not appear to have any updates.
I don't have anything to add here. You might want to try Tech Support, adding your e-mail to the
notifications on this issue...

- V