Latest Contributions by PeterKnoop

If you can, I would recommend updating the image URLs using the StoryMap module in the ArcGIS API for Python. It is a more robust approach, and runs less of a risk of leaving a StoryMap in an unexpected, broken state. That said, if need to make the changes via Assistant, what version of the StoryMap JSON did you edit? An individual StoryMap can exist in up to two different states, draft (or unpublished changes) and published, depending on what you've been doing with your StoryMap. The draft and published versions are stored as separate resources, so in Assistant after you open your StoryMap item, go to the Resources tab. You'll find the draft version in a file named "draft_<timestamp>.json", and the published version in a file named "published_data.json". Those two files are separate from the JSON under the Data tab for your StoryMap, which is the "current" JSON that gets used. When you edit a story, publish a story, discard changes, etc. the correct version is copied from draft or published to current. (Or something like that; what goes on behind the scenes is not publicly documented.) I would recommend making sure the StoryMap you want to edit is published, so that both a draft and published version exist. I would also make a copy of the draft version's JSON elsewhere, so that you can paste it back in, should something go wrong with your edits. Next, I would make your changes to the draft JSON version. (Don't have the StoryMap open for editing in another tab, or you run the risk of overwriting your changes!) After completing your edits, then open your StoryMap in Edit view, and verify the changes you've made are correct. If everything looks good, then publish the StoryMap. If something goes wrong, and you're not sure how to fix it, then you can use "Discard unpublished changes" to revert to your previously published version of the StoryMap. (And, if you cannot reach the discard functionality because the story is too broken, then go back to the Assistant and paste back in the original draft JSON content.) ... View more

@Mario, if you are comfortable authoring in Survey123 Connect and using pulldata() with custom JavaScript functions, then here is a potluck survey example that might be a helpful model on which you can build. When a user is filling out the survey to indicate what type of dish they are bringing to the potluck, it displays a table of the dish types and counts that have already been submitted:   Note that Survey123 custom JavaScript functions impose some key constraints on the approach outlined here: the survey cannot be shared publicly, and only members of the survey's owner's organization can submit responses (see Known limitations.) To create your survey in Survey123 Connect, you can put the following in the XLS form's survey tab: The calculation for others_dishes uses pulldata with the custom JavaScript function others_dishes (see below). The function returns a HTML-formatted table with the dish type counts, which is displayed to the user via the dishes note type question. Pair the above with something like the following set of dish type options on the choices tab: And, in the Scripts section of Survey123 Connect, provide the following custom JavaScript function: /* * JavaScript functions for Survey123 */ function others_dishes(token) { let counts = {}; let result = ""; // Set up query parameters. let f = "f=json"; let where = "where=1=1"; // retrieve all records let outFields = "outFields=your_dish"; let returnGeometry = "returnGeometry=false"; let query_parameters = [f,where,outFields,returnGeometry].join("&"); if( token ) { query_parameters = query_parameters + `&token=${token}`; } // Query URL for the ArcGIS REST API // (Obtain the appropriate URL from your feature layer's Item details page.) // For ArcGIS Online, the URL will be of the form: // https://<server>/<org_id>/arcgis/services/<service_name>FeatureServer/<layer_id> let layer_url = "your_feature_layer_url" let url = `${layer_url}/query?${query_parameters}`; // Make request to the ArcGIS REST API let xhr = new XMLHttpRequest(); xhr.open("GET",url,false); xhr.send(); // Process request result, if status code is 200 or OK. if( xhr.status === 200) { // Convert reponse text to a JSON object let response = JSON.parse(xhr.responseText); // If response is not an error, proceed. if( !response.error ) { if( response ) { // If successful, response is a Feature Set. // Retrieve array of dishes (features). let other_dishes = []; response.features.forEach(function(feature) { other_dishes.push(feature.attributes.your_dish); }); // Calculate count for each type of dish as dictionary. for( const dish of other_dishes ) { if( counts[dish] ) { counts[dish]++; } else { counts[dish] = 1; } } } } } // Convert dish count dictionary into an HTML table for display in a note. if( Object.keys(counts).length === 0 ) { result = "No other dishes yet..."; } else { result = '<table>'; result = result + '<tr>'; result = result + '<th style="text-align:left;">Dish</th>'; result = result + '<th style="text-align:right;">Count</th>'; result = result + '</tr>'; Object.entries(counts).forEach(function([key,value]) { result = result + '<tr>'; result = result + `<td style="text-align:left;">${key}</td>`; result = result + `<td style="text-align:right;">${value}</td>`; result = result + '</tr>'; }); result = result + '</table>'; } return result; }   ... View more

@MichaelVolz see the Filter options along the left-hand side of Content. Under Item type filters you can select "Apps", and underneath it, "StoryMaps". If you are logged in as an administrator, and have selected the My organization view for Content, then you should see a list of all of the ArcGIS StoryMaps in your organization. ... View more