Good morning,
When I try to run an EB application that uses a web map with a layer that is password protected, it pops up the following error message:
"Provide the Client ID for Experience Builder registered in the ArcGIS Enterprise you specify above"
How do we fix this issue?
You'll need to find the client ID of the Experience Builder app you registered in Portal/AGOL:
Then, open up the cdn folder of the downloaded application and open the numbered folder, then open config.json:
Find the empty clientID property and paste the value from the app:
and what about if you're not using the Developer edition, and its still referenced to another Portal?
You should not be seeing this warning if you are not on Developer Edition.
If you have triggered this warning in Online/Enterprise, it probably means you have manually edited the json files to transfer a project between Portals and have not scrubbed all the references to the other Portal.
I got the same error after the EB app was exported from Dev portal and imported to test portal.
The EB app in test is still pointing to the dev portal.
Should i switch to test portal in Dev before i export from Dev? How do I do that?
Thanks
Helen
Hello - We are receiving this same message. We pulled a 10.9.1 service into a web-map inside of 11.5 and saved the map. We then went into EB to point to the web-map and this is where we are seeing the message appear.
We were able to get around this by going to the content section inside of portal and adding the URL of the service from 10.9.1 as a new content item inside of portal 11.5. Now when we bring the data into EB and reference the data it loads just fine.
I have seen this every time I open a specific project since upgrading to Developer Edition 1.16 and now 1.17. Other projects do not have this issue. I opened up a support ticket about it and did not get any resolution. I have been able to hit cancel on that dialog box and continue without issue. Although using the browser's refresh button on the Build Mode page will crash the application.
I have occasionally seen this happen also.
One thing to watch out for, pay attention to the domain it says its using for the portal. I had an issue where I had some customer data I was using on a private instance, that was trying to link back to their data location because it may have been exported as Reference as I recall.
I had to change how the data was exported to be able to get past that as I recall to enable me to do the local testing I needed to accomplish.