Latest Contributions by Bud

@EmilyGeo I'm looking to set the global default value in the feature layer settings in the Content tab. ... View more

Related: Blog - ENHANCING THE ARCGIS PRO DEFINITION QUERY SPATIAL CLAUSE WITH ARCPY WITH A MULTI-LAYER GEOMETRY FILT... YouTube - Enhance the ArcGIS Pro Definition Query Spatial Clause with ArcPy with a Multi-layer Geometry Filter... Udemy - ArcGIS Pro Definition Query Masterclass with ArcPy and Python ... View more

Related: Blog - ENHANCING THE ARCGIS PRO DEFINITION QUERY SPATIAL CLAUSE WITH ARCPY WITH A MULTI-LAYER GEOMETRY FILT... YouTube - Enhance the ArcGIS Pro Definition Query Spatial Clause with ArcPy with a Multi-layer Geometry Filter... Udemy - ArcGIS Pro Definition Query Masterclass with ArcPy and Python ... View more

Related: Blog - ENHANCING THE ARCGIS PRO DEFINITION QUERY SPATIAL CLAUSE WITH ARCPY WITH A MULTI-LAYER GEOMETRY FILT... YouTube - Enhance the ArcGIS Pro Definition Query Spatial Clause with ArcPy with a Multi-layer Geometry Filter... Udemy - ArcGIS Pro Definition Query Masterclass with ArcPy and Python ... View more

For my notes: As a novice, it looks like the deprecated Web AppBuilder can do this using the Smart Editor widget. The Smart Editor widget stays open while the pop-up from the other layer is open. ... View more

@MikeMinami , regarding your comment. If you want to set the default value for a field, you need to do so on the feature template used to create features. Map viewer classic supported creating and editing feature templates, and now so does Map viewer. Check out this blog post for more information. The long answer is that the default value on a field (stored on the service) has somewhat limited utility because it gets overridden by a subtype default value and feature templates.  Even if we support changing the default value on the field, it doesn't propagate to feature templates. When you add a new feature and use a feature template, the feature template has its own default value. Now, you might think, updating the default value on the field it should also update the default value on the template. We don't do that because you may have explicitly set the default value on the template that's appropriate to the defined feature. Like others, I suspect it would be useful to be able to change the default value in a feature layer, for groups who don't use feature templates. And if people do use feature templates, then it's up to them to change any default values in the templates if needed; that's just part of normal business when we have user interfaces/front ends (like feature templates).   ... View more

For any AGOL novices like me: It looks like it's possible to change a default value in a Survey123 form UI, but not in the underlying hosted feature layer settings. ... View more

@EmilyGeo Thanks! ... View more

@bbollin  To clarify, there is a public webmap that you don't own but have permission to update, and a view that is shared either via a group or the org but not publicly? I created the web map and own it and can update it. But I don’t have any sharing privileges. The GIS administrator shared it with everyone. And same goes for the view, except it isn’t shared with anyone yet.   When you add  this view and save the webmap, you are getting the dialog above that you CAN update the view item (when in reality you can't). Does that sound right? I could modify the view if I wanted to, but I can’t share it since I don’t have any sharing privileges. ... View more