nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

One or more layers not publicly accessible

dougbrowning

We have been getting this message for months. I took each layer out one by one until I had a completely empty map and I still get this message. Not sure what public has to do with anything really.

What is going on here and how can I get rid of this?

thanks

Najděte více příspěvků označených jako

Accepted answers

All comments

Wei_Ying

Hi @DougBrowning

If you login with an account that can access the hidden layers, do they load to the list?

It is not about the gp service or standard analysis tool, it just about the data itself. If the current user does not have access to certain layers, the map does not load and the layer list won't load either.
The user has to have access to the layer, so when running analysis tool, we can pass the credential to the tool server so it can access the data.

dougbrowning

@Wei_Ying We are now seeing some of our layers show up on the list so thanks for fixing that.

It is still telling me some layers are hidden with the public message but not which ones so I cannot track it down. Still not sure why this message is there since this is a internal geoprocessing service so the layers should not need to be public. It should only block non public layers for AGOL geoprocessing tools correct? That makes sense but not a instant block if its not a AGOL tool. What logic is being used to block some layers and list others?

Also it is still not respecting selections in the map on the layer as input. Is this going to be fixed? Users are confused that this is not working since it does work in Pro with the exact same geoprocessing tool. Selections into tools as always been part of Pro, ArcMap, and WAB in the past. This same tools works great with selections in WAB so its been hard to have to retrain our users after all these years. I could also see adding a action to link the map and analysis widget.

In addition when using Set as Analysis input in WAB it was smart and would only show me tools that took a polygon as input when coming from a polygon for example. ExB is listing all tools no matter what the layers types are. That would be a nice fix as we have users trying to run a polygon into a point layer tool for example. Then we get support calls. Matching WAB would be a good first step.

thanks a lot

dougbrowning

I could share the app but not the layers. But its an easy one to see and it happens in all ExB we have ever built. So nothing to do with ours specifically. It is AGOL ExB. Basically the Analysis widget is blocking ALL non public layers from being used. It does not seem to check which tool it is.

The tools are our own custom geoprocessing services running on ArcServer 11.3. They are not AGOL. So that means the layers do not need to be public for the gp tool to work. I can see why they would need to be public for AGOL geoprocessing tools. But internal there is no reason to block this list. I think this is simply a hardcoded in block where they forgot that geoprocessing services can be custom and thus the layer would not need to be public. I think its just an oversight and easy fix.

If you go through the Set as Analysis Input button off the popup these tools work just fine. So again no need to block them from the list.

But in some ways we have found all of this may not matter until honoring selections gets fixed. I detailed that here https://community.esri.com/t5/arcgis-experience-builder-questions/select-widget-cannot-connect-to-analysis-widget/m-p/1626374#M19453 But basically the Analysis widget ignores selections completely no matter how we make them. See posts for all the ways that do not work. Making a selection then having a toolbox honor that is a core Arc function that has been in every product ever so we were pretty surprised by this one. It is simply how toolboxes work.

thanks a lot and hope that all makes sense.

Wei_Ying

Hi @DougBrowning , can you share the application or more details?
What tools are you using for Analysis widget and what layer you use?
This message basically from the analysis component and we need share them a case. Thanks a lot!

dougbrowning

Bump on this at 4 months. I have had multiple Esri staff agree this is a big issue but can never get anyone on the ExB team to respond. We have sent videos but can resend.

We are stuck without being able to use our custom GP tools. Sure seems like a bug.

Can some one please take a look at this. @AlixVezina

dougbrowning

Tested that setting and not seeing any difference. Does not pick up selections still also.

The public layers message looks built in and not connected to any setting. Seems to assume its a AGOL cloud service.

JeffreyThompson2

From the What's New page on yesterday's update:

Analysis widget—For input feature parameters, by default Experience Builder sends feature layers to the geoprocessing server as service URLs. You can check the new Send Feature Collection instead of URL check box to send data directly as a feature collection from the client side. You should check this check box if the input feature layer is private and the geoprocessing server cannot access it without credentials, or if the geoprocessing tool only accepts feature collections and not service URLs.

So, maybe already fixed?

dougbrowning

I think I traced this down to it blocking ALL non public layers from being inputs. I could maybe see this for online analysis tools but we are using custom geoprocessing tools hosted on our own servers. So these should be able to use our own internal layers just fine.

If I use Set as Analysis input from the layer it is hiding on me it works just fine.

This seems like a hardcoded bug?

thanks

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.