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; } } }

Selection "Set as Analysis input" ignoring attributes and only bringing geometry to input of custom web tool

tssaus

EB Developer Edition v 1.16

I have a custom geoprocessing service (Python Toolbox) published to ArcGIS Enterprise, and it is being used in the Analysis widget within my Experience Builder.

When I make a selection on a layer with the Select widget, and use "Set as Analysis input" to my custom tool (the input parameter type is GPFeatureRecordSetLayer), it seems to only send the OBJECTID, Shape_Length, and Shape_Area attributes & its geometry. It ignores all other attributes. Since my tool depends on other attributes, it of course fails.

The layers I am using are feature services referenced to an SDE.

I know this isn't a problem with my code, because when I use the entire layer as the input, the attributes go to the tool as expected.

This seems like a bug? Is there a workaround for this, either within my script or in EB?

@Wei_Ying (I saw you are involved with this specific data action on other posts)

Find more posts tagged with

ArcGIS Enterprise

Accepted answers

All comments

Wei_Ying

Hi @tssaus thanks for your feedback! Looks like a bug.

Would you be able to share with me the tool?
And meanwhile, can you try loading your data in Table widget, and then select some records from table, to "Set as Analysis input " to the tool. See if the data attributes are passed correctly?

tssaus

Hey! The attributes do pass correctly when sending from the Table widget off of a selection, and the tool functions as normal. It seems there is a bug with the select widget.

Wei_Ying

Thanks for confirmation. We will investigate the select widget issue.

Vara_PrasadM_S

Hi @Wei_Ying,

We are also facing same issue. When we use 'Set as Analysis input' option from Select widget, the geo processing tool we configured in Analysis widget is not receiving data for all attributes from selected layer and subtypes and domains are also not available from the layer.

However, if we do same 'Set as Analysis input" from Table widget, everything is going fine.

Could you please let me know if its a bug, if there is any work around to continue to use Select widget as our users want to do selection from Select widget and use this 'Set as Analysis input' from Select widget only.

Thanks in advance!

Wei_Ying

@Vara_PrasadM_S wrote:
Hi @Wei_Ying,
We are also facing same issue. When we use 'Set as Analysis input' option from Select widget, the geo processing tool we configured in Analysis widget is not receiving data for all attributes from selected layer and subtypes and domains are also not available from the layer.
However, if we do same 'Set as Analysis input" from Table widget, everything is going fine.
Could you please let me know if its a bug, if there is any work around to continue to use Select widget as our users want to do selection from Select widget and use this 'Set as Analysis input' from Select widget only.
Thanks in advance!

Yes it is a known limitation that from Select widget the selected feature cannot pass all attributes. As the Select widget does not load all attributes for performance concern. And Table loads all attributes if you view it so the selection can be passed correctly. We will try to solve the limitation in future.

Vara_PrasadM_S

Hi @Wei_Ying,

Thank you for the information. Is there any way we can track the bug.

We have done a work around to fix this in our custom GP Tool and come out of this issue. However, we are facing another issue from Select Widget > Set as Analysis input.

1. Select features from "Select" widget => Use "Set as Analysis input" from Select widget, all working fine(with our work around in our custom GP tool)

2. Select features from "Table" widget => use "Set as Analysis input" from Table widget, all working fine

3. Select features from "Table" widget => use "Set as Analysis input" from "Select" widget, all working fine

4. Select features from "Select" widget => use "Set as Analysis input" from "Table" widget. This flow is *not* working. Our tool has only one input parameter which is of Data Type - "Feature Layer". It is giving below error. I have add message statement as first line in our custom GP tool, that log itself is not visible. So, I feel before tool execution start itself, its failing.

Error: Invalid value for parameter PlanCutoverLayer - Details : Invalid JSON for GPFeatureRecordSetLayer or GPRecordSet datatype
Error: Failed.

Could you please let me know if its also a limitation from Select Widget.

Thanks in advance.

Vara_PrasadM_S

Hi @Wei_Ying ,

Could you please help me in this regards.

With Regards.

MichaelFallon

This post was super helpful. Was running into a similar issue with a custom GeoProcessing service that had a GPFeatureRecordSetLayer as an input. I had enabled the option to Allow browsing for layers option, expecting that to allow users to browse to a layer that had a selection, but there appears to be an issue that limits which layers are displayed (the tool help to require these layers to be public doesn't seem accurate).

Adding a select widget and using the Select widget use "Set as Analysis input" option is a decent workaround.

Wei_Ying

Yes as I said it is a known limitation that from Select widget the selected feature cannot pass all attributes. As the Select widget does not load all attributes for performance concern. Table loads all attributes if you view and select features from there, so the selection can be passed correctly. We will try to solve the limitation of select widget in future.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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