Latest Contributions by DSIProvince_Nord

Hi there, I have done exactly this and it works well.  1- create geographic feature service (point, line or polygon) with GlobalID in an SQL server SDE database 2- create table and 1-N relationship class between FS and table (GlobalID <-> GUID) 3- ensure FS and table have Archiving enabled (or versioned) 4- Open in AGPro and publish as a Feature Service (non hosted) 5- In Survey Connect, use the URL of your FS as Submission URL and name of the table as Form_ID in the settings sheet (be careful, the submission URL should be like https://your_organization/argis/sharing/rest/content/items/*****item_id****) -- Do NOT add a geopoint question in your survey (unless you created a relationship class between two geographic layers) -- also DO NOT create the survey from your FS. Create it from scratch or it will show every field from your FS and related table. 6- ensure you have the GUID field in Survey123 filled with the GlobalID of your asset via the custom URL scheme (see how to use parameters here : https://community.esri.com/groups/survey123/blog/2016/07/30/understanding-survey123s-custom-url-scheme ) So far it works for me. ... View more

Hi, I have a similar issue, after updating ArcGIS Enterprise from 10.6.1 to 10.7.1 and thus License manager to 2019.0, I cannot connect directly ArcGIS Pro 2.4 to my portal to get a named user license.  I have the same error "A core license could not be found....." The workaround I found is to connect to my AGOL account, then once AGPro is open, to switch to my portal url. I put my named users and AGPro license on the portal by downloading the JSON file from MyEsri. I don't have GIS Professionnal user types, only Creators with AGPro additionnal licenses. Trying to rename localUser data and registry key didn't work in my case. And the issue happened also on a newly installed computer. I also tried to disable / enable my user's AGPro license through portal. Any idea ? ... View more

Hi, Yes, there is a problem with lowercase GUID : it is not recognized in the relationship class.  In a webmap, if I select a parent object (polygon) and try to select all related records (point), only those with an uppercase are found. I have to manually change in the related record from lower to upper, then it works as expected. The service is a hosted feature service with a polygon layer, a point layer and a table and with relationship : polygon (1) <-> point (n) point (1) <-> table (n) ... View more

Hi, I noticed that the image-map appearance doesn't work in Survey123 Web Form. It only displays the image and then the standard select_one or select_multiple question. Is this functionality in your backlog ? Overall it's working flawlessly in the field app. Thanks ... View more

Hi, As mentioned, there are two ways to do that : 1- Create 36x6=216 fields (eg. Stop1_Spc1, Stop1_Spc2 ... Stop36_Spc6) and use the new grid-theme to organize them. (you could use Note type questions to show species names atop the grid). 2- Since you have a 1->N relationship between a Study and several Stops, you should use a feature service with a relationship class between two tables (one for the study number, allotment etc... and the other for the Stops) and use the Repeat functionality with a repeat-count set to 36. Hope this help ... View more

Thank you very much Ismael it works like a charm. It is not related, but I noticed that your coordinates now have a comma ( , ) as 1000 separator. In my case I have a space, and I get a message "invalid number". I tried to do an int(value) or number(value) but doesn't work. Anyway at the end the value sent is valid but it looks weird for the end user. ... View more

Hi, I found a workaround by turning the related table into a feature class (in this case I have now a polygon FC related to a point FC). Even with no polygon geometry written by Survey123, it works fine. I think that the bug only appears with related tables without geometry. ... View more

Hi, I found a workaround by turning the related table into a feature class (in this case I have now a polygon FC related to a point FC). Even with no polygon geometry written by Survey123, it works fine. I think that the bug only appears with related tables without geometry. ... View more

Hi, I have the same issue, it has been reported here also : https://community.esri.com/thread/226606-cannot-find-matched-feature-service-json-error-survey123  Do you have any idea regarding a potential workaround ? I tried to recreate my feature service with preauthentification but didn't work. Thanks ... View more

Hi, I have a very similar issue, while publishing a table with a related feature class as a hosted feature service. It appears to work with the Survey123 Field App but I have the same error with the web form, which is what I want for this Survey. Any news regarding this issue, is there a bug reported ? Thanks ... View more

Hi, James Tedrick is right, it is more related to security against bots than anonimity. Anyway we found a solution by asking our webmaster to add a captcha before displaying the Survey123 iFrame. ... View more

Hi there, The new EU Regulation regarding the gathering of personal data (https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679) means we now have to add captcha to every public survey which collects nominative information. Addin a captcha, regardless of how effective it is, will be mandatory for such surveys. ... View more