How do you identify multiple services from a single data source

[ShareUser]

With the announcement of a June 24th update that enforces a "Restriction on publishing multiple services from a single data source", I would like to know how I can identify in advance any issues in my organization's instance.  

ArcGIS Online Will Update Soon

This email is to notify you that we plan to update ArcGIS Online on June 24, 2026, from 5:00 p.m. to 12:00 a.m. (PT). ArcGIS Online updates are applied automatically with no expected downtime.

[ShareUser]

A blog post or something similar would be great. As others have already said, we're not even sure what to check because of the vagueness of a single eligible source data item.. Going just by that specific terminology it could be a lot:

https://developers.arcgis.com/rest/enterprise-administration/server/dataitem/

What are these, existing publishing restrictions? Where are these restrictions documented? And if it's a restriction, how is it being allowed if that is... ...restricted? Allowed and restricted are mutually exclusive.

creating a one-to-many relationship between source items and published services...ArcGIS Online will now enforce a one-to-one relationship between supported source data items and published services.

This could be a number of things?:

• One feature service per feature class-- --similar to a bulk publish.
• Inability to reference the same service multiple times-- --only unique end points allowed
• Source data items only hosted in ArcGIS Online as an item or any data item connected to ArcGIS Online?

I'll ask some questions that should have been asked before that email was sent:

• Is this going to break a number of things?
• How many things?
• Will affected organizations be emailed in advance that they have violated our undocumented restrictions?
• How does our user base check these things?
• Have we provided a workflow or tools for our user base to check?
• If this is going to break a number of things, why is the timeline to prepare and remedy deficient items so short?
• Have we provided a technical article or blog post to be released alongside this announcement?

Hoping for the best.

[ShareUser]

I've been mulling this over this weekend, and the more I think about it, there just can't be any way that single eligible source data item could possibly mean an enterprise database feature class. The extent to which that would affect organizations is absolutely out of proportion with the amount of time given before this change that it would be absolutely negligent to have waited until this close to make the announcement. Obviously it still sounds like a big change and @GIS_Spellblade is absolutely correct that the ambiguity of the communication is really difficult to parse.

[ShareUser]

From an ESRI rep recently, emphasis mine:

To clarify, this change does not impact workflows that involve registering or using ArcGIS Server services (including those referencing registered data sources). Those services will continue to function as expected.

The restriction applies specifically to content uploaded into ArcGIS Online (such as file geodatabases, shapefiles, CSVs, or rasters) that are used as source data items for publishing. Moving forward, only one primary service can be published from each uploaded source item.

Existing services created prior to the update will continue to work without interruption. However, if additional services are needed from the same data, users will need to create a copy of the source data item before publishing.

Hosted Feature Services are not impacted, and their ability to create related child items such as tile layers, OGC services, and views remains unchanged.

"Source data items” in this context refers specifically to data uploaded into ArcGIS Online (such as file geodatabases, shapefiles, CSVs, or raster files) that are used as inputs for publishing hosted services. This does not apply to services that reference registered data sources, such as ArcGIS Server services or federated services using enterprise geodatabases. Those workflows are unaffected by this change.

[ShareUser]

See, why couldn't that have been in the original communication? 

[ShareUser]

Having copies of sources all over your AGOL page seems very inefficient. What is the point for this change? Is it so that we have to buy more storage? 

WL

[ShareUser]

To clarify, this change does not impact workflows that involve registering or using ArcGIS Server services (including those referencing registered data sources). Those services will continue to function as expected.

The restriction applies specifically to content uploaded into ArcGIS Online (such as file geodatabases, shapefiles, CSVs, or rasters) that are used as source data items for publishing. Moving forward, only one primary service can be published from each uploaded source item.

Existing services created prior to the update will continue to work without interruption. However, if additional services are needed from the same data, users will need to create a copy of the source data item before publishing.

Hosted Feature Services are not impacted, and their ability to create related child items such as tile layers, OGC services, and views remains unchanged.

"Source data items” in this context refers specifically to data uploaded into ArcGIS Online (such as file geodatabases, shapefiles, CSVs, or raster files) that are used as inputs for publishing hosted services. This does not apply to services that reference registered data sources, such as ArcGIS Server services or federated services using enterprise geodatabases. Those workflows are unaffected by this change.

Hope this helps clarify.

[ShareUser]

Thank you for jumping in, as the terminology was not clear in the initial announcement.

Is there an official statement to this effect somewhere in the Esri Website?

Is there a more-exhaustive list of affected "source data items?"
Is the "Tiled imagery layer (hosted)" on that list?

[ShareUser]

You’re right; the wording is confusing.

1. Is there an official Esri statement confirming this behavior?
At this time, Esri has published the restriction language in the ArcGIS Online update notice and community channels, but there is not yet a single official article that fully clarifies how this applies across all workflows (particularly the distinction between uploaded data and referenced/registered data). Esri is aware of the confusion and is working to improve the wording.

2. What are “source data items”? Is there a full list?
“Source data items” refers to data that is uploaded into ArcGIS Online and used as input for publishing hosted services. Based on current documentation, this includes file geodatabases, shapefiles, CSVs, Excel files, GeoJSON, raster files, and similar uploaded content.
There is not currently a formal, exhaustive list tied specifically to this restriction, but it aligns with the existing publishing inputs documented for hosted feature layers.

3. Does this include hosted tiles or imagery layers?
No. Hosted Feature Services and their related derivative items including tile layers, OGC layers, and similar outputs are explicitly not impacted. These are considered child items generated from a hosted service, not separate services published directly from a source data item.

Esri understands that there are some questions surrounding this topic. We are working on an official statement coming shortly. Stay tuned and sorry for the confusion. 

[ShareUser]

@Roshan_MarkSingh_Matharu   My apologies if this is unwarranted, but did you utilize an AI LLM to create that response?  If so, may I ask which one?

I am trying to learn how to identify such products, and some of the syntax made me curious.

If I am way out of line, I very much apologize.