Latest Contributions by SFM_TravisBott

The issue: a secured layer will not display when viewed through an embedded application on my Hub site. I have an application whose map contains a secure layer. For that secure layer the URL for the application, as well as that of the map that underpins it, are stored as the viable URLs (background on the process can be found here).  As configured this application can be embedded in a website and the data will be displayed properly (because it's being viewed through the appropriate embedded URL). This works fine on our organization's website. This does not work, however, on a Hub site. Is there a a workaround to make this viable? The layer does not display in either the embedded application nor when place as an iFrame.  ... View more

Hoping the community here can lend a hand.  The goal: create a calculation attribute rule for a polygon feature class that extracts a value from the feature with which it has the largest overlap in another dataset. If a user creates a polygon I want the value of an underlying polygon to be used for an attribute in the edited datasets. However I want to have error controls in case the user creates a polygon that overlaps two of the underlying polygons. I want to extract the attribute from the polygon with which it has the largest overlap.  Current code:   var fsJurisdiction = FeatureSetByName($datastore, "jurisdictions", ["Jurisdiction"]) var fsJurisdictionIntersect = Intersects(fsJurisdiction, $feature) var jurisdiction = First(fsJurisdictionIntersect) if (jurisdiction == null) return {"errorMessage": "Not in a jurisdiction"} return jurisdiction.Jurisdiction   ... View more

I have a layer in a map that I am serving in Experience Builder to solicit edits. I updated the domain values that were the templates for editing and they're not being honored when viewed through the new map viewer/Experience Builder.  I changed one of the Zone Type domain values from "Non-Wildland" to "Non-Wildland Buffer" (not just label, but the coded value as well. I updated existing entries that were 'Non-Wildland' to the correct 'Non-Wildland Buffer). This reflects fine in symbology.... ....As well as editing in Map Viewer Classic....   However, the new Map Viewer refuses to honor the change when attempting to edit, and it's not presenting the template appropriately in Map Viewer or Experience Builder.  I have gone through and explored the JSONs for the layer and the map and updated every instance of Zone Type being 'Non-Wildland' to make sure it reflects 'Non-Wildland Buffer.' The JSON reflects the editing template as specifying 'Non-Wildland Buffer.' Why is this honored in Map Viewer Classic and not the new Map Viewer? What gives? And is there a trick to get it to reflect appropriately in the new Map Viewer and EB? Thanks!   ... View more