topic Re: New AGS Mapservice Layers Not Showing in AGOL WebMap in ArcGIS Enterprise Questions

New AGS Mapservice Layers Not Showing in AGOL WebMap

MichaelVolz — Fri, 01 Jun 2018 19:13:20 GMT

I have an AGOL webmap that originates from an ArcGIS Server (AGS) mapservice which has been in operation for several months. Last month many new layers were added to the mxd for the mapservice and these layers appeared in the webmap after the mapservice was republished. More changes were made this week and after republishing the changes were seen in the mapservice's REST endpoint, but are not seen in the webmap.

Has anyone ever encountered this scenario and would know how to fix the problem?

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

JonathanQuinn — Mon, 04 Jun 2018 21:41:02 GMT

Are you adding the whole map service to the webmap? Do you have any definition queries or filters? Looking at the parameters of the exportMap operation should tell you why certain layers don't come through.

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

MichaelVolz — Mon, 04 Jun 2018 22:52:55 GMT

Jonathan:

The new layers are available at rest endpt, just not in the webmap.

How exactly do I use the exportMap operation to tell why certain layers don't come through?

So I went into the mxd that is the datasource for the mapservice that is being passed thru AGOL and I retrieved the bounding box for an area where a feature from the new layers should appear, which it does with the exportMap operation. As such why would these new layers show up in the rest endpt and in the exportMap, but not in the AGOL webmap?

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

MichaelVolz — Tue, 05 Jun 2018 16:30:14 GMT

I have some more information in regards to the new layers in the mapservice that might be the issue which I had not picked up on until now. There are 4 fields in each new layer with Text data types and Length of 2147483598. Would a field length such as this cause issues with the layers appearing in an AGOL webmap as I can see the layer with the ArcGIS Javascript viewer from the REST endpt?

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

JonathanQuinn — Tue, 05 Jun 2018 22:17:17 GMT

So you've confirmed that the service works, so it appears to be a client side problem, in this case AGOL or the webmap. I would take a look at the requests from the webmap using Fiddler or the browsers dev tools and determine how the request is different. You can also just try to bring in the service in a new webmap and see if they show up, which would confirm it's a webmap problem. If they don't show up, then it could be a problem with certain field types or lengths, as you're speculating.

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

MichaelVolz — Tue, 22 Jun 2021 08:20:11 GMT

Jonathan:

Does this idea:

https://community.esri.com/ideas/13249

cover the phenomenon I am seeing as this is expected behavior which makes updating webappbuilder apps painful. You need to recreate the webmap if new layers are added in existing groups or above existing layers in the mxd (I updated the mxd a month ago with layers that are were all placed after the previous layers and the webmap saw the new layers after republishing the mapservice).

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

JonathanQuinn — Wed, 06 Jun 2018 16:55:59 GMT

If you're adding the whole map service to the webmap, then no, that doesn't cover it. All layers will be included in the map service so they're all included in exportMap requests, (unless, again, there's a layer filter in the webmap).

Hosted layers have to be added individually, so if you had a hosted service with layer1 in it and then add layer2 to the MXD and republish, layer2 won't show up in the map until you actually add it in.

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

SverkerNorlander — Thu, 07 Jun 2018 09:00:41 GMT

Hi!

We've seen this issue with a few customer (I'm swedish tech support).

The solution for us has been to use Ago Assistant to edit the json data of the web map and manually add the new layers in the json data of the web map.

The problem might have something to do with popups being enabled or not, but we haven't had the time or opportunity to do extensive testing to verify this, or why this problem occurs.

Easiest when modifying the json would be to copy any of the already existing layers in the json and paste it at the end of the array and remove as much popup info as possible (I think we made it empty) and change the id.

Esri support should be able to help, but let me know if you need some assistance.

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

Anonymous User — Sat, 11 Dec 2021 06:31:49 GMT

Echoing Sveker's point: we do this as well -- use AGOL assistant to update the web map's JSON.

We've found that this happens when custom pop-ups are being used primarily. Support is probably the best option to get this done, but if you're in a time-crunch and are comfortable with JSON, I'm including the workflow we go through to accomplish this for you (and all others who may face the challenge).

The workflow we use is as follows:

AGO Assistant Steps
1. Open your current web map that is having the issues (i.e. not reflecting the changes) and choose the option to "Save As" and name this copied web map "DevConfMap."
2. Create a new web map and add the service URL to the map and configure only the new layers the way you want (i.e. set their pop-up rules, modify symbology, labeling, name etc.). Save this map as "TempConfMap."
3. Go to ago-assistant.com , login, and choose the option to 'view an item's JSON' from the main ribbon. Then find the newly created Web Map named "TempConfMap." Click on that Web Map and two panes will appear in the right side of the screen. Scroll so you see the bottom containing the actual map configuration options. Copy all the content in that pane and paste it Notepad++.
4. In AGO Assistant, now find the Web Map we named "DevConfMap" and do the same steps as above to get the Web Map's JSON. Paste the contents into a new Notepad++ tab.

Notepad++ Steps

Inspect the TempConfMap json in Notepad++ and identify the layers you configured that are currently not showing up in the DevConfMap within the JSON's "layers." It'll likely look something like this:

                    "id": 0,
                    "layerDefinition": {
                        "source": {
                            "type": "mapLayer",
                            "mapLayerId": 0
                        },
                        "drawingInfo": {
                            "renderer": {
                                "type": "uniqueValue",
                                "field1": "ParkingStatus",
                                "defaultSymbol": null,
                                "uniqueValueInfos": [
                                    {
                                        "value": "1OpenLow",
                                        "label": "Open - Spaces Available",
                                        "symbol": {
                                            "color": [
                                                56,
                                                168,
                                                0,
                                                142
                                            ],
                                            "outline": {
                                                "color": [
                                                    153,
                                                    153,
                                                    153,
                                                    255
                                                ],
                                                "width": 0.75,
                                                "type": "esriSLS",
                                                "style": "esriSLSSolid"
                                            },
                                            "type": "esriSFS",
                                            "style": "esriSFSSolid"
                                        }
                                    },
                                    {
                                        "value": "2OpenHi",
                                        "label": "Open - Near Capacity",
                                        "symbol": {
                                            "color": [
                                                255,
                                                222,
                                                62,
                                                180
                                            ],
                                            "outline": {
                                                "color": [
                                                    153,
                                                    153,
                                                    153,
                                                    255
                                                ],
                                                "width": 0.75,
                                                "type": "esriSLS",
                                                "style": "esriSLSSolid"
                                            },
                                            "type": "esriSFS",
                                            "style": "esriSFSSolid"
                                        }
                                    },
                                    {
                                        "value": "4Full",
                                        "label": "Full",
                                        "symbol": {
                                            "color": [
                                                230,
                                                0,
                                                0,
                                                162
                                            ],
                                            "outline": {
                                                "color": [
                                                    153,
                                                    153,
                                                    153,
                                                    255
                                                ],
                                                "width": 0.75,
                                                "type": "esriSLS",
                                                "style": "esriSLSSolid"
                                            },
                                            "type": "esriSFS",
                                            "style": "esriSFSSolid"
                                        }
                                    },
                                    {
                                        "value": "3Closed",
                                        "label": "Closed for Construction",
                                        "symbol": {
                                            "color": [
                                                252,
                                                146,
                                                31,
                                                165
                                            ],
                                            "outline": {
                                                "color": [
                                                    153,
                                                    153,
                                                    153,
                                                    255
                                                ],
                                                "width": 0.75,
                                                "type": "esriSLS",
                                                "style": "esriSLSSolid"
                                            },
                                            "type": "esriSFS",
                                            "style": "esriSFSSolid"
                                        }
                                    }
                                ]
                            },
                            "labelingInfo": [
                                {
                                    "labelExpression": "[Name]",
                                    "useCodedValues": true,
                                    "maxScale": 0,
                                    "minScale": 0,
                                    "where": null,
                                    "labelPlacement": "esriServerPolygonPlacementAlwaysHorizontal",
                                    "symbol": {
                                        "color": [
                                            47,
                                            79,
                                            79,
                                            255
                                        ],
                                        "type": "esriTS",
                                        "backgroundColor": null,
                                        "borderLineColor": null,
                                        "haloSize": 0,
                                        "haloColor": null,
                                        "horizontalAlignment": "center",
                                        "rightToLeft": false,
                                        "angle": 0,
                                        "xoffset": 0,
                                        "yoffset": 0,
                                        "text": "",
                                        "rotated": false,
                                        "kerning": true,
                                        "font": {
                                            "size": 7.5,
                                            "style": "italic",
                                            "decoration": "none",
                                            "weight": "bold",
                                            "family": "Arial Unicode MS"
                                        }
                                    }
                                }
                            ],
                            "showLabels": true
                        }
                    }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

The index and mapLayerIndex correspond with the service's index (i.e. .../MapServer/0, .../MapServer/1, etc.). This is a good way to confirm you're looking at the right layer.
Once you've identified what JSON section needs to be added (each layer has it's own section separated by commas and contained with { } brackets, copy that JSON.

Inspect the DevConfMap JSON and identify the layer that is missing all of the layers. You're going to paste the copied snippet into the appropriate location (be sure to make sure the JSON is valid after you inject this JSON).
1. Note that sometimes the formatting is not exactly the same between the source and destination web maps. If this is the case (i.e. one has mapLayerID and the other does not), the injected JSON should conform to the destination JSON.
Once the JSON is confirmed as valid, return to AGO Assistant.

AGO Assistant Part 2
1. Find the "DevConfMap" in your content and choose the option to 'view an item's JSON.'
2. Scroll to the bottom panel on the right side of the screen and choose the option to 'edit this items JSON.'
  1. It will then turn a different color.
3. Select All and delete -- then insert the entire JSON snippet from the DevConfMap sheet in Notepad++ (i.e. the JSON after the injection).
4. Save
5. Go to AGOL and open DevConfMap to see if it looks right -- if so, you can make a deployment plan to update the production Web Map.
  1. If not, review the JSON and see what's going on

If you run into snags, feel free to ping me

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

MichaelVolz — Thu, 07 Jun 2018 18:19:02 GMT

Sverker:

Do you see this as expected behavior for the webmap not to recognize new layers if the popups have been customized in the webmap?

Seems like a bug to me as it creates a much more complex workflow to update webmaps for webappbuilder apps.

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

Anonymous User — Tue, 12 Jun 2018 11:00:45 GMT

Likely an enhancement request at a minimum, but I remember talking to one of my buddies at Esri about the JSON build for a Web Map and there were some limitations associated with 'refreshing' the JSON automatically when certain customization had been made... but don't rightly recall...

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

JonathanQuinn — Tue, 22 Jun 2021 08:20:14 GMT

Webmaps are static items, meaning it's just a text representation of the item. This isn't updated if a service is updated, as there's a push/pull mechanism to update any dependencies at this time. You'll need to use AGO Assistant. There is an idea about this already:

https://community.esri.com/ideas/13249

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

MichaelVolz — Mon, 18 Jun 2018 19:27:19 GMT

I have done some additional testing on this issue myself and having an ESRI support analyst try to replicate the issue, but this replication has so far been unsuccessful so I am not sure what the mechanism is that causes the webmap not to update when an underlying mapservice has been updated and then republished.

I added layers several times to the mxd after configuring pop-ups in the webmap and the new layers were visible after republishing. I also added layers above existing layers and within existing group layers but the new layers have been available to the webmap after 4 iterations of changes.

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

Anonymous User — Wed, 10 Apr 2019 16:52:21 GMT

I usually see this happen as well. Not a feature, a design bug. AGOL Assistant is labelled as unsupported. If I add a layer to a service, I'd expect the webmap to update its JSON itself. Not a tall order. Also I use a simple click(); function to expand certain sublayers in my layer lists in WAB (because that is not yet implemented as a property of a sublayer object, that would be nice) so their legends are visible and already expanded, and since I target the DOM node ID, it changes once I re-add my service, which means I also have to update all those. Having the webmap keep its JSON in sync with a service will hopefully be supported in the coming milestone AGOL update.

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

SSMIC3038 — Fri, 13 Mar 2020 18:35:00 GMT

Thank you for taking the time to write this up and share - I will be using it extensively!!!

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

ZorbaConlen1 — Sat, 04 Jul 2020 19:57:45 GMT

Agreed this seems like a bug. I ran into the problem just now. It's inconsistent. The webmap in question has several services. I have added and removed layers in all of them, and in most cases, the webmap reflects the change automatically, but for one service it does not.

Nice to have the agol assistant work-around as documented above, but that's a lot of hassle and its easy to make a small error when editing json files directly.

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

ahargreaves_FW — Tue, 09 Aug 2022 20:13:14 GMT

Ditto...I either need to recreate an entire webmap, including popups, scale ranges and visibilities or hack away at the JSON via an unsupported tool. If when successfully updating the JSON (I've gotten pretty good at it now!) this can bust WAB widgets such as the Attribute table.

I've cross posted and tagged @KellyGerrow , AGOL product owner, here and here.

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

Kara_Lara — Fri, 07 Apr 2023 23:40:28 GMT

Thank you! This worked for me!

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

Kara_Lara — Mon, 26 Feb 2024 20:00:41 GMT

We're still having this issue in ArcMap 10.8, publishing to stand-alone AGS, using AGOL to view & develop web map. Now almost every time we overwrite the map image layer for a specific map service, publishing is successful, can see new, changed, or moved layers at REST endpoint (seen in AGOL Item Details) but not in AGOL Map Viewer or Map Viewer Classic (Contents panel nor in the map), & also not seen in the deployed web app. But it's not consistent. Sometimes overwrites work fine, sometimes they don't.

Images attached, layer of interest is "83 Industrial". An interesting thing I noticed is found when you compare the "AGOL_OpenInArcGISDesktop.png" & "AGOL_OpenInArcGISPro.png" images, you'll see that downloading FROM AGOL, the Desktop lyr file is correct, whereas the Pro pitemx isn't.

Re: New AGS Mapservice Layers Not Showing in AGOL WebMap

Kara_Lara — Mon, 26 Feb 2024 20:38:49 GMT

@JonathanQuinn - Bringing the same service into a new web map in AGOL does not solve it. Fields in my layer are few & simple. It appears that the AGOL JSON calling the layers & popups is not getting "refreshed" when the map image layer is being "overwritten" by publishing. This keeps happening to us & we keep having to publish it as a new map image layer, losing all popups. This is time consuming & costly for our client. If interested, please see my additional post from today in this topic.