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

[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

[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]

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.