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

How do you identify multiple services from a single data source

JeffSilberberg

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.

タグ付けされた投稿をもっと見る

Accepted answers

CalvinHarmin

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.

All comments

jordan.carmona@piercecountywa.gov_piercecowa

If anyone was wondering how to check for offending items, this is a script that I put together.

from arcgis.gis import GIS
gis = GIS("home")
search_results = gis.content.search(query="", max_items=-1)
# a dictionary containing the item object as key, and list of related services if that list is larger than 1
results = {
    item: v
    for item in search_results
    if (v := item.related_items(rel_type="Service2Data", direction="reverse")) and len(v) > 1
}
# you can check the unique source types
represented_types = {k.type for k, v in results.items()}
print(represented_types)
# since the Esri response was non-exhaustive, the better methodology would be to exclude items we know would not be on an exhaustive list
remove_features = {k: v for k, v in results.items() if k.type not in ["Compact Tile Package", "Feature Collection", "Feature Service", "Vector Tile Package"]}
# these would be all of the items that you'd want to check
print(remove_features)
# and rinse, lather, repeat for item types that don't count

EDIT: I made the below check before screening out items that had only one related item. So that question probably doesn't make sense. We only had feature services that had more than one related item.

we were left with these types, does a service definition count as a source data item?

{'CSV',
 'File Geodatabase',
 'GeoJson',
 'Microsoft Excel',
 'Service Definition',
 'Shapefile'}

NLI_Wendy

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?

ODWC_GIS

@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.

Roshan_MarkSingh_Matharu

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.

ODWC_GIS

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?

Roshan_MarkSingh_Matharu

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.

ZachBodenner

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

CalvinHarmin

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.

ZachBodenner

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.

GIS_Spellblade

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

We also got this email today. And I am totally confused. We have a lot of services that use the same feature classes and hence data sources. Our parcel feature class is used at least in 6 various services. These services are being used in various applications and integrations with Lucity and Accela. How will it affect us?

ODWC_GIS

I know we should not reference politics in the forums, for the sake of professionalism and basic dignity, but I suddenly had a flashback to then-PM Teressa May's "explanations."

Public: "What does Brexit mean for us?"
Teressa May: "Brexit means Brexit!"
Public: "Oh, okay... But what should we expect?"
Teressa May: "Don't worry! It won't be as bad as Mad Max!"

ZachBodenner

Agreed, and the other thing that's interesting is that this is an AGOL change, not an Enterprise one. So it's not like you could publish a referenced enterprise geodatabase dataset to AGOL anyway (at least not without your own server as an in-between). So I also don't really know what this is referring to. Now, Enterprise of course receives all the code changes to AGOL eventually, so I think this does really need to be clarified.

MProctorBrown

Would be really nice to get some clarity of what is affected, rather than the only example being what's not affected.

ODWC_GIS

Here's a copy of the full email, for those of you who did not receive one:Early Morning Email of May 22, 2026, from ESRI.

I'm in the same boat as OP, regarding what that first paragraph really means...

Restriction on publishing multiple services from a single data source
Prior to this update, organizations could publish multiple supported services from a single eligible source data item, creating a one-to-many relationship between source items and published services. To align with existing publishing restrictions, ArcGIS Online will now enforce a one-to-one relationship between supported source data items and published services. With this change, only one service can be published from each eligible source data item type. Hosted Feature Services are not impacted by this change and will continue to support the creation of multiple child items, such as Tile Layers and OGC layers. Organizations that currently publish multiple services from the same source item will need to create copies of the source data item to continue creating additional services.

What exactly is this "single eligible source data item" to which ESRI is referring?

All they explain is that it isn't "Hosted Feature Services."

ZachBodenner

I'm glad I'm not the only one confused about this. If it means you can't publish multiple services from one Enterprise Geodatabase feature class, wouldn't that like, completely defeat the purpose of that entire products?

JonM32

@JeffSilberberg

Weird. That would likely break a lot of services out there if that happens. I haven't seen any emails from Esri regarding it but I'm not a part of the early adopters/beta tester thing for ArcGIS Online.

Thanks for the heads up though! I'll be curious what happens from this.

JeffSilberberg

@JonM32

I am not really sure what I am referring to.

I received the Email notice on the update, and the fact that the "feature" was not going to be supported as of the update. But I honestly an not sure how to identify if any of the many "authors" have used this and what the impact would be on the organization.

"Restriction on publishing multiple services from a single data source

Prior to this update, organizations could publish multiple supported services from a single eligible source data item, creating a one-to-many relationship between source items and published services. To align with existing publishing restrictions, ArcGIS Online will now enforce a one-to-one relationship between supported source data items and published services. With this change, only one service can be published from each eligible source data item type. Hosted Feature Services are not impacted by this change and will continue to support the creation of multiple child items, such as Tile Layers and OGC layers. Organizations that currently publish multiple services from the same source item will need to create copies of the source data item to continue creating additional services."

JonM32

@JeffSilberberg

If you're referring to services that are not hosted feature layers, but services you published from a enterprise portal or non-federated server, you can go to the server manager and look at the services in detail there. There's an option listed right next to the service name, it looks like a small database icon. Click that, it'll list the details of where the service is coming from.

Hope this helps!

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

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