Latest Contributions by AmyRoust

The catch to this is that I have group layers in maps where the sublayers are all turned on, but the group itself is turned off. As an example, I do this with our historic registry properties, which are split into local, state, and national registries. Typically, users don't want to see them on the map, but if they activate the group, I want all of the layers to display. I like this suggestion, though. I wonder if there is a way to enable the action if the sub layer is turned off by default but not auto turn on the group if the sublayers are visible? ... View more

Thanks, Ken! Worked perfectly. ... View more

@AndrewTurner - Yes! https://geoportal-lawrenceks.hub.arcgis.com/   ... View more

@DiveshGoyal - thank you for investigating and finding a fix! This will be a big help to us. ... View more

I just remembered another oddity of sharing as copies. You cannot have two or more layers in your service that reference the same feature layer. As an example, I had two layers in my map that referenced the same bike network line feature class. The first one had a definition query to only show existing routes, and the second one had a definition query to only show planned routes. You can publish a service like this, but you cannot share it via the collaboration. ... View more

@SSWoodward I decided to go with your sample code since I'm already working with arcpy in a file on my server. I successfully created the new version: server = f"https://xyz/FeatureServer" version_name = 'python' arcpy.management.CreateVersion(server, 'sde.DEFAULT', version_name) new_lyr = arcpy.management.MakeTableView(f'{server}/15', 'default_lyr') full_version_name = [v.name for v in arcpy.da.ListVersions(server) if version_name in v.name][0] meter = arcpy.management.ChangeVersion(new_lyr, 'BRANCH', full_version_name)  But I cannot get it to switch back to DEFAULT before posting and reconciling. arcpy.management.ChangeVersion(new_lyr, 'BRANCH', 'sde.DEFAULT') arcpy.management.ReconcileVersions(server, "ALL_VERSIONS", "sde.DEFAULT", full_version_name, "LOCK_ACQUIRED", "NO_ABORT", "BY_OBJECT", "FAVOR_TARGET_VERSION", "POST", "DELETE_VERSION", r"C:\Log.txt", "PROCEED", "RECONCILE")   When line 2 runs, it says "Warning: Error deleting version xyz.python. The version is currently in use. [xyz.python] Not running inside a server process.   I could change the reconcile to keep the version, but I'd prefer to delete it. ... View more

OK, that first part is wild. I agree that it should be impossible for your items to be shared as a reference! I also agree that turning off editing should not be your deal breaker. We don't share any editable services from Portal to AGO. I hate to say it, but with the information you have at this point, I think it's time to endure a tech support call. There might be something more specific in their troubleshooting documentation related to that specific error. If I think of anything else, I'll definitely let you know! ... View more

I'm sure you know this, Mike, but the log-in prompt shows up when an item is shared as a reference instead of a copy. Just adding that note for others who might not have gotten that far yet. I dug into my old notes from troubleshooting to see if there was anything else useful. One note I forgot about, which is pretty specific: if you're publishing the service in Portal as a registered service (it connects to the SDE database when published), make sure you are using an account that has more than viewer-level permissions. A viewer account does not have sufficient privileges in SQL Server to allow the collaboration to work. The account I use has read-write permission, but the service that I share via collaboration has editing turned off. The only other thing I saw was a note on checking the Distributed Collaboration logs in Portal Directory (https://yourservername/portal/sharing/rest). After you log in: - Click your username in the breadcrumbs at the top (Community > Users > username) - Click the Org ID hyperlink in the blue box - Scroll to the bottom and click Collaborations (buried in Child Resources) - Click on the Collaboration ID - Click on Collaboration Workspaces - Click on the Collaboration Workspace ID - Click Sync Status (at the bottom under Supported Operations) That will give you a slightly more detailed log than what you see in Portal. Third option is to go to portaladmin, set your log level to debug, run the collaboration attempt again, and then check that log file. I recall that there were some additional clues in there that helped me narrow down my issue. So ... no real "a-ha" suggestions here, but I thought I'd share just in case. ... View more