Attribute Expressions in Map Viewer are incredibly powerful and extremely useful. Unfortunately, bringing those wonderfully calculated and formatted attribute expressions into widgets in Experience Builder currently doesn't seem possible.
Your only options for "Connecting to data" are the raw attributes from layers in your web map. The only place within Experience Builder that your attribute expressions appear is in the map pop-up and Feature Info widget.
Map Viewer Attribute Expressions should appear in the "connect to data" list for ALL EXB widgets.
EXAMPLE:
I created an attribute expression called "Mill Calculation" in my web map in Map Viewer and want to connect the text widget in EXB to it.
^ "Mill Calculation" Attribute Expression in Map Viewer ^
Unfortunately, in the "connect to data" list for the text widget, none of my glorious Attribute Expressions are available.
For what it's worth, I was unable to use attribute expressions in the following EXB widgets:
A possible work-around for this is to re-create the attribute expression in the Dynamic Content, Expression tab. I tried this and unfortunately, Arcade expressions are not supported here, but I guess that's a whole different idea...
I personally need expressions to be available in the Table widget, but I agree all ExB widgets should be able to see the attribute expressions created in the web map
This is a nearly critical change to facilitate the transition from WAB to EB and ESRI has been talking about making the change for almost 5 years. Is this functionality on the road map for EB?
Yes!!!! This drives me crazy every time ... currently struggling with null values in my source data (because of a hosted join layer with statistics) and presenting them nicely in an experience builder, but I can't seem to fix it with an 'expression' in dynamic content and the attribute expressions built in the web map aren't available to use when configuring the Text widget.
here's an example -- we need to present the number of available volunteer slots (calculated through a hosted layer join) -- if there are no volunteers, then the summary statistic is null -- which means there's lots of slots available, but the calculation doesn't work because of the null...
attribute expression works great! but not available in the app...
Would love to see this implemented! Configure once ... use everywhere!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.