Currently, the only way add a new layer or table to an existing service is to use the REST/Python API or go through the lengthy process of exporting a service as an FGDB, downloading it, bringing it into Pro, making your updates, then overwriting the existing service to varying results.
Using the REST Endpoint's addToDefinition brings its own challenges and encounters problems such as these: https://support.esri.com/fr-fr/bug/new-layers-added-to-a-service-via-the-rest-endpoint-do-bug-000145... which then forced me to find this thread (https://community.esri.com/t5/arcgis-online-questions/feature-layer-added-to-feature-service-does-no...) to figure out a fix for the missing tables in the Overview page.
I would suggest that overall with Field Maps Designer that a lot of design elements for existing services are starting to appear, and perhaps developers can leverage these changes in tools that assist with the design of new layers and tables.
Thank you.
@AlfredBaldenweck - Thank you for the reply. I went and Kudos'd those posts, as well. I was surprised I couldn't find an exact idea on this anywhere when I searched for it. Hope these can get some traction.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.