When using Buffer, a popup will not display a value in a Web AppBuilder App. However, it is shown in an AGOL map. Centroid(), which was released with Arcade 1.3, works properly.

Versions:

WAB Developer Edition 2.6 (JSAPI 3.22)

Arcade: 1.3 (JSAPI ??)

Arcade 1.3 is only integrated in JS API version 3.23. So if WAB Dev edition 2.6 uses JS API 3.22, there will be no official support for the functions new in Arcade 1.3. To clarify, this doesn't mean that all new functions released in 1.3 weren't present in the Arcade codebase in prior versions. Some were, but weren't documented or officially "released". For example, Centroid was likely included in the Arcade codebase prior to Arcade 1.3, but we hadn't documented it because it wasn't thoroughly tested. Other reasons may include wanting to release all geometry functions in the same release. In fact, there are some other geometry functions technically present in version 1.3 that we didn't "release" or document because we don't have valid use cases for them yet. They will likely come later as we expand Arcade's ability to access other features within the context of a single feature.

When using Buffer, a popup will not display a value in a Web AppBuilder App. However, it is shown in an AGOL map. Centroid(), which was released with Arcade 1.3, works properly.

Versions:

WAB Developer Edition 2.6 (JSAPI 3.22)

Arcade: 1.3 (JSAPI ??)

Arcade 1.3 is only integrated in JS API version 3.23. So if WAB Dev edition 2.6 uses JS API 3.22, there will be no official support for the functions new in Arcade 1.3. To clarify, this doesn't mean that all new functions released in 1.3 weren't present in the Arcade codebase in prior versions. Some were, but weren't documented or officially "released". For example, Centroid was likely included in the Arcade codebase prior to Arcade 1.3, but we hadn't documented it because it wasn't thoroughly tested. Other reasons may include wanting to release all geometry functions in the same release. In fact, there are some other geometry functions technically present in version 1.3 that we didn't "release" or document because we don't have valid use cases for them yet. They will likely come later as we expand Arcade's ability to access other features within the context of a single feature.