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

Building a dynamically FeatureSetByName query

Jake_S

Hey folks, currently trying to dynamically build a FeatureSetByName query but am getting the notorious 9999999 error in ArcGIS Pro 2.6.6 for even a simple case. Does anyone know if this is possible or if I'm going about it the wrong way?

var s ="indxltm_region_ltm5000"
var x = FeatureSetByName($datastore, s , ["OBJECTID", "PLAN_NAME"], true)if (Count(x) > 0) {    return first(x).PLAN_NAME
}

Encontre mais publicações marcadas com

Arcade

Accepted answers

HusseinNasser2

FeatureSetByName does not support dynamic class names. The name of the class has to be available during static analysis of the script so we can build out the relations in the catalog. (E.g. if you copy Class A which has an attribute rule that reads from Class B we also copy Class B too)

here is more details explaining why

Why FeatureSetByName doesn't work with variables

https://community.esri.com/t5/attribute-rules-blog/why-featuresetbyname-doesn-t-work-with-variables/ba-p/1541572

All comments

RoderickPerendy

I don't mean to be disrespectful here but could this get added as an error code? Or maybe it has? I'm running off Pro 3.1 and Enterprise 11.1 I would have been pulling my hair out trying to figure out the source of the 999999 error I got until I saw this thread. Removed my When function and made a cascaded if statement instead and it solved the FeatureSetByName issue using dynamic variable.

HusseinNasser2

here is more details explaining why

Why FeatureSetByName doesn't work with variables

https://community.esri.com/t5/attribute-rules-blog/why-featuresetbyname-doesn-t-work-with-variables/ba-p/1541572

Jake_S

Johannes, thanks for keeping a pulse on this. We still haven't found a solution either

JohannesLindner

Well... A few days later, I now need the same thing. Now I tested it in an Attribute Rule, turns out it doesn't work there.

@HusseinNasser2, any tips?

JohannesLindner

The expression seems to be OK, it worked for me in a Popup.

So either it doesn't work in an Attribute Rule (which I doubt) or it's not the expression that causes the error.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

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