Latest Contributions by JamieLambert

The sequence_id is already in both hosted features. I thought the Field Mapper was to copy a field from the Input and write it to the Output? Or is this how the Unique Feature Identifier setting works? You assign that value then use Field Mapper to tie the Input and Output records based on how that value is mapped? Happy to give it a crack anyway! Thanks. ... View more

Thanks @JakeSkinner. A couple of updates after a meeting with the business line yesterday - 'job_id' is now replaced by 'sequence_id' as 'job_id' is not always unique. And 'Complete' is now 'ReportSent' (Input) and 'report_sent' (Output). The overall GeoEvent (10.8.1) setup is still the same and still not writing the value to the existing output record. The Input is filtered to only records where a report has been sent (i.e. complete) and to Incremental Updates as once the report has been sent the record is no longer edited. The Output Unique Feature Identifier is 'sequence_id'. And 'sequence_id' is the TRACK_ID field for the Input Definition (I am assuming it is not required for the Output Definition as Output Unique Feature Identifier is already set). Field Mapper in the Service maps the Input 'ReportSent' field to the Output 'report_sent' field. The geometries are the same - both polygon. I'm assuming that with the 'sequence_id' as Unique Feature Identifier and TRACK_ID assigned to the Input this will match the Input and Output records, then the Field Mapper will populate the Output 'report_sent' field with the Input value 'ReportSent'. I think I have captured everything in the image below:   The 'ReportSent' value is being mapped, though it seems like the corresponding 'sequence_id' record in the Output hosted feature is not being picked up / written to. The Output feature is editable. Do I need to add a Filter or some other process? Thanks. Jamie. ... View more

Not sure if that is possible with the Flash Repeat. You may be better off looking into using Arcade for custom symbology - based on creation date or last edit date. This is on my list to look into, though I haven't had a chance as yet... ... View more

I did this also though I found I also had to rename the CSV file (and update the pulldata calculations) for it to work. Creating a new file and reusing the same filename was not enough. Jamie. ... View more

@JohnWatson_EBA @SaraPluta @IsmaelChivite  I'm seeing an issue where recent updates I have made to a CSV file are not working, though all the original records - exactly the same pulldata functions pointing to the same CSV file - work fine. So the calculations work, only recent changes (not to the headers, just body text) to the CSV aren't working. This is a CSV file in the Media folder of the Survey. No issues in Connect or Windows, but not working on iOS. This seems to be a common issue on iOS with CSV files created before a key date... I tried creating a new CSV file and reusing the same filename, though this didn't work. I tried harder and used a NEW FILENAME and updated my pulldata calculations (find/replace) accordingly and this worked. See also: pulldata-function-in-survey123-does-not-work-on-iPad?  Jamie. ... View more

Hi @BrettStokes , Just went through the workflow for the polygon example, and worked perfectly in Map Viewer Classic, though not in Map Viewer. The expression gives the same result when testing in both, though the URL does not work correctly in Map Viewer. In the pop-up, all coordinates are displayed, and only the first latitude value is passed to Survey123. Cheers, Jamie. ... View more

This one worked for me - thanks for sharing Matt! ... View more

Thanks @RussRoberts, that works for the web, though we see no data at all in field apps (Explorer, Field Maps). ... View more

Hi @LJackson29, If you manually typed the {globalid} part of your URL, try using the Fields:{} dropdown to select if from the dataset instead. I have had issues in the past when manually typing {globalid} that have been resolved this way. Hope this helps! Jamie. ... View more

This is a great idea (especially when you have a heap of records). See also: Dashboards: Filter data by user input text - add autocomplete filter for user input. And: Dashboards: Category, Number, Date Selectors as stand-alone elements - to have these filters as their own elements to be positioned anywhere - not just the Header or Side-panel. That way you could put your User Input filter with you List element where it makes the most sense! Also much better for stacked elements. Cheers, Jamie. ... View more

Any idea when BUG-000138393 will be fixed - Pop-ups do not honor the existing layer attribute filters when displaying feature information? This has been a known issue before Dashboards came out of beta - first identified in late July 2020. Its a significant issue that I would hope would take some priority. dashboards-beta-map-widget-shows-popups-for-filtered-features latest-update-to-arcgis-dashboards-lists-and-selectors-are-not-correctly-filtering-popups  arcgis-dashboards-beta-category-selector-filters date-selector-in-dashboard-is-not-filtering-correctly Thanks, Jamie. ... View more