Latest Contributions by AnthonyJonesRSK

Hi @ZhifangWang, Thanks for the quick response on this, that's perfect and works brilliantly. Thanks again to you and the team for all your efforts. Anthony ... View more

Hi @IsmaelChivite,  Is the captcha functionality available in Connect? Thanks Anthony ... View more

Hi Ana, Obviously James is the expert on this but I don't think it's possible to populate questions in repeats using urls. It certainly says that here and see below. One way around it though is to build a separate form on top of your repeat. This was you could populate questions for existing repeats or generate a url to create new features in the repeat. This may not work in your situation but is a workaround I use in order to populate repeats whilst keeping the data all under one parent layer, which helps with report generation. Cheers Anthony  ... View more

Sure. My url is generated in Arcade, see below. You can ignore most of it but I spent a long time trying to get the callback variables to work. Basically I found that if I included my callback variables in a parameters dictionary as I've done for the survey123 parameters and then used the UrlEncode function, Field Maps didn't appear to like that and kept telling me that I needed to supply the featureID parameter despite it being there in the url. I ended up realising that Field Maps doesn't like any ampersands after the callback which is why I've had to encode these manually rather than using the UrlEncode function on the parameters dictionary, which kept adding the ampersands back in.  The callback part of my script could probably be written a bit more elegantly as I'm still fairly new to Arcade but this worked so I didn't want to mess with it too much! Like you say it would be great to pull data back from S123 in the callback but I was at least glad to be able to get it to update the layer in Field Maps once the form had been completed. The only thing I don't like is that when it goes back to Field Maps the updateFeature element reopens the form and it'd be great if it just wrote "Yes" to the field without the form being opened again, to avoid the surveyor changing anything else by accident.  Don't know if that's of any of use but just wanted to acknowledge your post as it was the first thing I'd seen that suggested additional callback parameters may be possible. Cheers //Convert coordinates to wgs84 for use in survey123 function WebMercatorToWGS84 (x, y) {     var lon = (x / 20037508.34) * 180;     var lat = (y / 20037508.34) * 180;     lat = 180/PI * (2 * Atan(Exp(lat * PI / 180)) - PI / 2);     return {         y: lat,         x: lon     } } //Launch survey123 var urlsource ="arcgis-survey123://?itemid=XXXXXXX&"; //Get centroid of feature var geom = Centroid($feature) //Generate coordinates from centroid var coords =  WebMercatorToWGS84(geom.x, geom.y) //Format coordinates so they work with survey123 geopoint var splitcoords = coords.y + "," + coords.x //Get polygon area to pass to survey123 var featurearea = Round(AreaGeodetic($feature, 'square-meters'), 2) //Format globalid var fglobalid = Mid($feature.globalid, 1,36) //Generate other url parameters to pass to survey123 var params = {   center: splitcoords,   "field:FeatureProjectCode": $feature.PolygonProjectCode,   "field:FeatureSiteID": $feature.PolygonSiteID,   "field:IDCount": $feature.PolygonCount,   "field:CommonName": $feature.PolygonCommonName,   "field:parentglobalid": $feature.parentglobalid,   "field:GeometryGUID": $feature.globalid,   "field:FeatureType": "Polygon",     "field:FeatureSize": featurearea }; var callback = {   callback: "https://fieldmaps.arcgis.app/?referenceContext=updateFeature&itemID=XXXXXXX&featureSourceURL=XXXXXXXX", } var callbackid = "featureID=" + fglobalid var callbackattributes = 'featureAttributes={"PolygonDataEntered":"Yes"}' return urlsource + UrlEncode(params) + "&" + UrlEncode(callback) + "%26" + UrlEncode(callbackid) + "%26" + UrlEncode(callbackattributes) ... View more

Hi Doug, I stumbled across your post after looking into the use of url callbacks. I agree the ability to send data back from Survey123 would be great. After reading your post and a lot of tinkering with the encoding I at least managed to set up a system where once the survey has been completed the callback goes back to the polygon layer and updates a status field to indicate that the associated survey has been completed for that particular polygon. My hope is that this will help our surveyors keep track of which features they've fully completed. Plus with the new filter options in Field Maps it means they can filter to show those they've missed. So I'm not really offering anything new to the conversation but just wanted to say thanks as your post convinced me that more complex call backs are possible! Cheers   ... View more

Thanks Barbara, much appreciated. ... View more

Hi @BarbaraWebster1 , Thanks for the quick response on this. I did think after I'd posted this that the Save As option probably covers us on the old My Surveys option but would it be possible to reinstate the My Organization option as that was always quite handy to be able to see all other surveys across our organisation and duplicate them if needed? This was often used to help troubleshoot if someone was having issues but now they'd need to be shared to the templates group or the files shared separately. Thanks Anthony   ... View more

Hi Barbara, Thanks for the update, there are some really useful features here. The auto updating of domains and aliases in particular are great updates as this was always a bit of a pain particularly if the domain needed to be updated across multiple related layers! One thing we've noticed though is that the ability to create a new survey from an existing survey you own or from the organisation appears to have disappeared. The "My Surveys" and "My Organization" options (see below) are not available in the latest update. We only have the ability to use an existing file or feature service but of course using the feature service doesn't include the form settings. Are we missing something here? Thanks Anthony  @IsmaelChivite @BarbaraWebster1 @Anonymous User    ... View more

Hi Aaron, Just wanted to say a big thank you for this suggestion as it has helped me immensely. Last week I was pulling my hair out as I've been trying to pass globalids to the parentglobalid field in another feature using the intersection function so I could create relationships between the two features if they intersect (save the user having to add related records manually). I kept finding that the globalid would calculate sporadically and couldn't work out what the issue was. In my case I found that using the Lower() function on my globalid has solved it so again big thanks for this, it's been a life saver! Thanks Anthony ... View more

This is great news and will prove very useful. Thanks Phil and to the wider Survey123 for all your efforts, it's much appreciated. ... View more

Sorry, ignore my last comment. I've just looked at your web map example and can see in there how you've enclosed the field parameter and field name in inverted commas e.g. "field:asset_id": $feature["asset_id"], which seems to do the trick. Thanks! ... View more

Hi @JamesTedrick, Thanks for this really useful article. I'm having an issue passing field parameters as you have in your example. Where you have field:asset_id: $feature["asset_id"] I keep getting the error Unexpected token :. It doesn't like the second colon so I was wondering how it's possible to define field parameters in a dictionary in this way? Thanks Anthony ... View more

Hi @SandraLuken1, than you for the prompt response. The problem with the current situation is if you have two points that sit on top of one another then it zooms in far too close so you end up with a blurred base map. Could it be enhanced by changing the  point zoom scale to a minimum possible zoom rather than a definitive? This would mean that if you are zooming to an aggregated extent it would zoom to the best scale for those features but not beyond the minimum. Thanks  ... View more

I did consider using an expression but I'm not sure it will work in my instance. To provide further context I'm basically trying to map my companies offices (around 300 records) and each has a related layer for business units within that office and within each business unit is a related layer for the staff within that unit. So in my case a business unit may be represented in multiple offices. I basically need an app where a user can go in, see all the office locations and which business units and staff are in each. But I also want them to be able to filter the offices by business unit so they can see where all our ecology staff are for example.  The problem I'm having is that the parent layer for the offices doesn't contain any info on the business units so I can't filter it by business unit. So I tried just using the business unit layer to show the office locations as each business unit has geometry matching the office layer and also the name of the office. This is where I've run into the zoom issue as this layer needs the grouping to hide the duplicates but needs to maintain the data for each record.  Ideally I just need more operators for filters such as "contains". These are available in Experience Builder but ExB is limited in its ability to filter across layers by common fields. I feel like I'll just need a workaround for now until Group Filter becomes available in ExB. Thanks Anthony ... View more