Why is ArcGIS Pro Query Definition converting strings with commas?

MJChurchill

Hi all,

I have a field containing values that are comma separated lists [e.g. '1, 2, 3', '6', '2, 5, 9']. Note that this is three strings marked by single quotes.

I try to use values from this field in a definition query like so:

But, as soon as I close the dialog, the values get converted to a list of the individual values as strings - instead of three values, there are now 7 values ['1', '2', '3', etc.]:

Only the value without a comma, '6',  is now correct.

I realize I can work around this by adding a field and converting the commas to some other character but I feel like this should not be necessary. Why is ArcGIS Pro altering the strings?

[I am using ArcGIS Pro 2.4.0 on a Windows 10 machine]

Regards,

MJ

MarisaClaggett

Hi MJ,

This appears to be related to the following logged defect.

BUG-000111347 : Layer definition query with “Add Clause” and “Include(s) the value(s)” on a text field with comma separated single values, is interpreted incorrectly and separates one value in the data into two separate values.

It is currently in the product plan to be fixed, unfortunately, I am unsure of the timeline.  If you create a case with Esri Technical Support, we can attach this bug to your account and you follow it's progress in My Esri.  

Have a great weekend!

- Marisa