Latest Contributions by DavinShokes1

There is files window in the Notebook screen. How do I reference files in it?  I have a json object I would like to save to the files area and reference later. How do I save files in the AGOL notebook? I'm having trouble finding documentation.   Thanks! ... View more

When fields are hidden due to conditional visibility, the values are deleted. This is critical data that just doesn't apply to the current form entry. Here is an easy example. Say you are visiting a jobsite 2 times and recording the date separately for each visit. You want to hide the previous visit field; not delete it. Fields: NumberofAttempts - Domain= 1st Attempt, 2nd Attempt FirstAttemptDate SecondAttemptDate   On the first visit, the user sets NumberofAttempts="1st Attempt". The FirstAttemptDate should be visible and required. The SecondAttemptDate should be hidden. On the second visit the user sets NumberofAttempts="2nd Attempt". The FirstAttemptDate should be hidden. The SecondAttemptDate should be visible and required.  Currently, when the user sets NumberofAttempts="2nd Attempt", the FirstAttemptDate clears its value when hidden and the data is lost forever.  This is a simple example but there are many other use cases for maintaining hidden field values. However, I could also see use cases for deleting the values. They just don't apply to any of our company's needs. I would propose this be a checkbox on the form configuration page under conditional visibility so that existing workflows aren't impacted. ... View more

There is a need for a container widget to create and store selections of features that can be accessed later as the input for widgets. Feature selection can be similar to what is possible within the Batch Attribute Editor. The primary difference is that selections can be used as inputs for widgets. Here are a few possibilities if current widgets were able to take in a global feature selection: Attribute Table: edit the attributes of individual features in a filtered table Chart: display statistical summary of the selection Related Table Chart: view only features/records related to the selection Summary: same benefits as the Chart widget Analysis: easily provide the intended features to any of the aggregation tools. Buffer selection, extract, etc. Situation Awareness: numerical summary of selection, obtain info of proximity to incident for each feature Geoprocessing: run the geoprocess on the selection Info Summary: view the feature type count for selection Directions: Optimized route for selection Batch Attribute Editor: this widget benefits from using a global selection. The intended features can be verified by leveraging other widgets before the bulk update occurs. Print: output uses padded extent of the selected features and highlights or filters them Search: batch geocode selection to get a list of addresses Edit: update geometry for entire selection Custom Reporting Widgets This is just the tip of the iceberg. Imagine how much more powerful apps and widgets would be with feature selections! Promote this idea​ ... View more

     There is a need for a container widget to create and store selections of features that can be accessed later as the input for widgets. Feature selection can be similar to what is possible within the Batch Attribute Editor. The primary difference is that selections can be used as inputs for widgets.   Here are a few possibilities if current widgets were able to take in a global feature selection:   Attribute Table: edit the attributes of individual features in a filtered table Chart: display statistical summary of the selection Related Table Chart: view only features/records related to the selection Summary: same benefits as the Chart widget Analysis: easily provide the intended features to any of the aggregation tools. Buffer selection, extract, etc. Situation Awareness: numerical summary of selection, obtain info of proximity to incident for each feature Geoprocessing: run the geoprocess on the selection Info Summary: view the feature type count for selection Directions: Optimized route for selection Batch Attribute Editor: this widget benefits from using a global selection. The intended features can be verified by leveraging other widgets before the bulk update occurs. Print: output uses padded extent of the selected features and highlights or filters them Search: batch geocode selection to get a list of addresses Edit: update geometry for entire selection Custom Reporting Widgets   This is just the tip of the iceberg. Imagine how much more powerful apps and widgets would be with feature selections! ... View more

I want to do a rest query that matches: SELECT        CustomerID, COUNT(CustomerID) AS IDCounts FROM            Property GROUP BY CustomerID HAVING        (COUNT(CustomerID) > 1) I don't see where do put having parameters in the REST interface. Any ideas? Thanks. ... View more