I have my own gp service that gets a point as parameter.
After I published it I can run it from Pro, I can add it and run t from a WebMap and I can build a Web AppBuilder (old) that running it with no problem.
When I try to build experience builder and run it (Enterprise 11.5) I get the error you can see in the attachment.
Tring to run it with EB developer works fine!!
Is it a bug??
Hi @Ke_Xu
It is very simple.
Create a Python script that get one parameter
The script should not do anything else, the problem is before the script is running.
You can open a cursor on the FeatureSet and print the coordinates (just for check).
In a atbx I created a new script tool, the first parameter is a feature set that get point only (filter in the parameter screen) and pointing to my script.
Run and publish.
Try to use in experience builder
As I said it works in REST, Pro, WebMap, old WAB and EB developer
I’ve hit similar snags using featureSet in custom scripts—it usually comes down to how the input is being passed. One trick that helped me was explicitly converting the input to a FeatureSet using FeatureSet(Text(myFeature)) before calling the tool. Sometimes it’s just about making sure the object type matches exactly what the tool expects, even if the structure looks right.
Hi
I am not sure I understand. Is this in the EB setting?
There is nothing wrong with the gp service, it works from all the other applications.