nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Allow ArcGIS Pro to sort Coded-Value Domains with special characters

GregWolowich1

I have a coded-value domain with single quotes (') used within the domain value. When editing in ArcPro I was unable to sort the field using that domain. I would like to see coded-value domains permit sorting on fields using domains with special characters such as single quotes.

Thanks,

Greg

Find more posts tagged with

Editing

Closed

Status: Closed

Comments

KoryKramer

Thanks for submitting this idea @GregWolowich1

When you say "When editing in ArcPro I was unable to sort the field using that domain," can you clarify if you mean you're trying to sort the field:

Or are you looking for the domain picklist to be sorted differently?

If the latter, you could sort the domain and save the sorted order:

But from your description it sounds like you're not seeing the sorting order you expect when sorting the field itself. Can you provide screenshots and some examples of the domain values containing single quotes?

Thank you.

GregWolowich1

Hi Kory,

The domain picklist is in the correct order. It is the values in the table that will not sort property. If I uncheck "show domain and subtype descriptions" the values sort properly.

But when it is checked I cannot sort the values in the field, as you can see in the screen shot below. I was told by the support technician this is by design and not a bug.

Thank you!

Greg

KoryKramer

Thanks for that detail @GregWolowich1 . I'm not convinced that this isn't a bug and am checking on our side here. Will follow up when I have more info.

Thank you

KoryKramer

This has been logged as [BUG-000144153: Hosted feature layer fields with apostrophe characters (') in domain codes and descriptions sort incorrectly in ArcGIS Pro 2.8.2]

If you are experiencing this issue, the bug should be available on support.esri.com shortly - use the Subscribe button to be set up for notifications and increment the count of affected customers.

Thank you!