Latest Contributions by ScottMcGee4

Here's the situation: 1) I have an ArcPro project that I use to update several hosted feature layers. 2) When I want to update a hosted feature layer, in the ArcPro project, I click Share > Share As > Web Layer > Overwrite Web Layer. 3) I am then presented with a dialog box that shows my folders within Portal > My Content. 4) I can then click on my folder named "Master Data Layers" to see the hosted feature layers within that folder. I then select a hosted feature layer and update it. The above works just fine, no problem, as long as I'm the one who performs the update. The issue I have is that I need figure out how a coworker can also use the same ArcPro project to update the hosted feature layers. In my office, there are two of us that do GIS work, and I am typically the one who updates the layers. However, if I'm out of the office and can't do the update, the other person will need to update the layers. The problem is that I can't figure out how to make the hosted feature layers that are located within my folder "Master Data Layers" visible to the other person. When they open the ArcPro project and do Step 2 (above), they see their own folders within their Portal > My Content, and they don't see my "Master Data Layers" folder. They therefore can't select the hosted feature layer that needs to be updated. Here's what I've done to try to fix this: 1) I created a group named "Updaters". 2) I added my coworker to the "Updaters" group and assigned them the "Group manager" role. 3) In the ArcPro project, in the "Overwrite Web Layer" pane, in the "Share With" section, I made sure that the "Updaters" group was checked on, and published the layer. 4) In AGOL, under "Groups", I viewed the "Updaters" group and the hosted feature layer that I just published was in fact listed in the "Content" tab. So my question is, how do I set things up so that my coworker can also use the ArcPro project to update hosted feature layers? Thanks, Scott ... View more

I recently had to delete a hosted feature service and recreate it. This feature service has 8 layers, and each layer uses the query widget to define multiple search/filter criteria. After recreating the feature service, I had to go back into the query widget and laboriously rebuild all of the search/filter criteria for each of the 8 layers in the feature service. It would be great if the query widget offered a way to export a layer's search/filter criteria to an XML file, and then also be able to import the XML back into the query widget. This would provide a quick and easy way of backing up and restoring your search/filter criteria when you need to recreate a feature service, rather than having to re-do everything manually. This idea is not limited to just the query widget. It could also be applied to any other AGOL widget, such as the attribute table, where you set configuration options. Having the ability to export all of your widget configuration settings to XML, and then import the settings back into the widgets, would be a great way to document your project, safeguard your settings, and easily and quickly restore them if something bad happens, without having to laboriously recreate everything manually. ... View more

I recently had to delete a hosted feature service and recreate it. This feature service has 8 layers, and each layer uses the query widget to define multiple search/filter criteria. After recreating the feature service, I had to go back into the query widget and laboriously rebuild all of the search/filter criteria for each of the 8 layers in the feature service. It would be great if the query widget offered a way to export a layer's search/filter criteria to an XML file, and then also be able to import the XML back into the query widget. This would provide a quick and easy way of backing up and restoring your search/filter criteria when you need to recreate a feature service, rather than having to re-do everything manually. This idea is not limited to just the query widget. It could also be applied to any other AGOL widget, such as the attribute table, where you set configuration options. Having the ability to export all of your widget configuration settings to XML, and then import the settings back into the widgets, would be a great way to document your project, safeguard your settings, and easily and quickly restore them if something bad happens, without having to laboriously recreate everything manually. ... View more

I have a dashboard that uses several serial charts. Each chart shows several categories, and each category displays an acreage associated with it. I want to display the sum total of all categories in a chart directly in the chart, and I don't see a way of doing that in the Operations Dashboard. Here's a visual that illustrates what I'm trying to achieve: Above, you can see that there are 16 categories with an associated acreage. It's good to see how much acreage each category has, but if you want to see what the grand total acreage is, you have to pull out a calculator. Pretty tedious and error-prone. Below is a mock-up of what I'd like to see: See the total acreage listed? That's what I'd like to achieve in all of my Operations Dashboard serial charts. This seems like an obvious thing to have, but I don't see any way of doing this. Any ideas? ... View more