Latest Contributions by AdrienLepoutre

The functionality to collaborate and synchronize content from registered enterprise geodatabases as copies (via distributed collaboration) to other Portals or AGOL is currently possible. We would like to see this functionality be enabled for data published as non-hosted feature layers collaborated from registered file geodatabases. This would enable more flexibility in leveraging the capabilities of Portal and AGOL within a same data branch. ... View more

The functionality to collaborate and synchronize content from registered enterprise geodatabases as copies (via distributed collaboration) to other Portals or AGOL is currently possible. We would like to see this functionality be enabled for data published as non-hosted feature layers collaborated from registered file geodatabases. This would enable more flexibility in leveraging the capabilities of Portal and AGOL within a same data branch. ... View more

We would like to be able to change the REST name of web services in Portal and AGOL. There is documentation indicating this could be possible but after testing it with ESRI analyst, renaming the REST name, at first glance, does not seem possible. The analyst is currently seeking additional resource to look into this issue andto be sure that renaming service is not supported. The documentation is: Rename Service with ArcGIS REST API (doesn't work) How To: Change the name of a feature service  (changes only feature layer) Update Definition (Feature Service)—ArcGIS REST API: Services Directory | ArcGIS for Developers (payload doesn't stick) This idea change is related to the following post: Updating Title of Hosted Feature Layer getting Updated via Script  ... View more

We would like to be able to change the REST name of web services in Portal and AGOL. There is documentation indicating this could be possible but after testing it with ESRI analyst, renaming the REST name, at first glance, does not seem possible. The analyst is currently seeking additional resource to look into this issue andto be sure that renaming service is not supported. The documentation is: Rename Service with ArcGIS REST API (doesn't work) How To: Change the name of a feature service  (changes only feature layer) Update Definition (Feature Service)—ArcGIS REST API: Services Directory | ArcGIS for Developers (payload doesn't stick) This idea change is related to the following post: Updating Title of Hosted Feature Layer getting Updated via Script  ... View more

Hello everyone, I have been trying, unsuccessfully to change the title of a previously published hosted feature layer in AGOL getting updated by the following method Updating your hosted feature services with ArcGIS Pro and the ArcGIS API for Python  Setup: I have an .aprx that gets used to update open data content, collaborated via AGOL. This .aprx contains feature layers which get used to create and stage service definition files which will then update the .sd files associated with the hosted feature layers. Once a sd file is updated, it gets published to push the changes to the hosted feature layer. Goal: I would like to be able to change the tile of the hosted feature layer and upstream feature layer in the .aprx to update the name of this item. I would like for this update to happen without the item ID of the downstream item in AGOL changing and without having to store a lookup table for the old-new name in my Python script (i.e. I want the change to happen permanently inside the process). What I've tried (unsucessfully):    1) Updating the feature layer name in TOC, associated .sd and hosted feature layer names in AGOL. This led to the    following error in Python during the sdItem.publish(overwrite = True) command:     "RuntimeError: User cant overwrite this service, using this data, as this data is already referring to another    service."    I interpret this as the TOC name creates a service draft that wants to publish a new item using the previous .sd but    since a pre-existing item is already getting updated by this .sd. The solution would be to delete the pre-existing         service  hosted feature layer....but that would not allow us to keep its ID.    2) Using the overwrite web layer geoprocessing tool directly on the hosted feature layer with the updated feature layer    name. This simply failed with the message: "Failed.View log" (and a link to the log without much information) I would like to know if there is a way to permanently change the title of a hosted feature layer in the scripting update pipeline describe in the arcgis blog (link above) while keeping the hosted feature layer item ID? Any help would be great! Thank you, Adrien ... View more

Our goal: publish our data by reference from a registered file geodatabase in Portal. When this data needs to be external, we would like to collaborate with (via distributed collaboration) as a copy (to become a hosted feature layer) to AGOL. This synced copy would then leverage the cloud capabilities for public facing request levels. However when going through the process of setting up the collaboration and reading the online documentation, it was not clear that this set-up was possible. For example: when setting up the collaboration workspace, we have the choice between (screenshot ) sending "Feature layers [...] in my portal [...] as References or as Copies (If possible). When selecting "Copies (if possible)", a message appears mentioning only "hosted feature layers" for which you need to "checked 'Enable Sync'". The conditionality ("if possible") combined by the fact that feature layers by reference (hanging off a map image layer) do not have the "Enable sync" option available, it seems to me that it means that to have a synchronized copy in AGOL collaborated via Portal, it needs to have been published as a hosted feature layer during the initial publishing to Portal (?) If so, that would mean that by reference feature layers in Portal could only be collaborated to AGOL as references, hence the "If possible" (inferring that it is not possible for layers initially by reference) ? Testing it out with layers by reference, the URLs were always pointing to the original Map image layer (by reference) on the Portal REST. Only when published as hosted initially (and synced) did the URL change to a cloud-like URL. However an ESRI staff explained that this setup was possible yesterday. I wanted to find confirmation that this was either not possible or indeed possible in a way we hadn't figured out yet. Thank you, Adrien ... View more