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; } } }

Change in service title naming limitations - rejects hyphens

DataOfficer

Following the latest ArcGIS Online update it seems that there have been changes to what is accepted as a service title. Previously service names could be edited to include a hyphen. However now, when trying to add a hyphen to a service name, it returns the error:

"The title of a service may only contain alphanumeric characters or underscores and be 90 characters or less."

Is there any reason why this is now being enforced? We already have many views with hyphens etc. in their names. Are these still valid?

Find more posts tagged with

Accepted answers

RebeccaRichman

Hi @DataOfficer !

My current understanding is that this was partial enforced prior to this (so if you published with hyphens, it would get converted to underscores), and so with this change the behavior is consistent across the board.

As to your existing views, I haven't been able to test on my end, but if you have any issues with them not working, please create a case with technical support: https://support.esri.com/en-us/contact

Thanks!

Rebecca

All comments

RebeccaRichman

Hi @DataOfficer !

As to your existing views, I haven't been able to test on my end, but if you have any issues with them not working, please create a case with technical support: https://support.esri.com/en-us/contact

Thanks!

Rebecca

MapOfTheSolutionatique

Same issue as original poster, but wanted to comment that even though existing views in my organization still work, they were definitely hyphenated in their title (not converted to undercores--at least not on the front end), and now we may have to rename more than a hundred services if we want to be consistent. It's strange the hyphens were accepted before, but are no longer accepted.

RebeccaRichman

Hi @DataOfficer and @MapOfTheSolutionatique,

FYI, the team has decided to roll this rule back for the moment to further discuss the implications.

Cheers,

Rebecca

RobCollett1

Hi Rebecca,

I can see that AGOL still displays this error message when creating a new hosted feature layer. Has this functionality been rolled back and reviewed? Thank you.

RebeccaRichman

Hi @RobCollett1,

To clarify, you could never use hyphens when creating a new hosted feature layer. The functionality in question was the ability to rename the item (but not the service) once it was created. That functionality should be available.

Cheers,

Rebecca

MapOfTheSolutionatique

Thank you for this change! We can now edit the alias/outgoing title of a feature service again. I realize that hyphens were never supported in the backend name, and spaces were/are converted to underscores, but now our users will be able to see hyphens again, as they have in the past. My organization greatly appreciates this.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.