POST
|
Hi @RyanUthoff, There's no easy way to change item IDs. I'm attaching here a simple script (based on ArcGIS Python API) for cloning surveys - it should also clone all the related items and create the relationships on the target portal. Just fill the form Item ID, source and target portal details (url, username and password) and run. Hope that helps, Uri If this answer solved your question or if you found it helpful please mark it accordingly to help others who have the same question.
... View more
06-09-2021
07:54 PM
|
0
|
0
|
1317
|
POST
|
Hi Larry, It took me a while but I think I found a solution. 1. Add the 'EditDate' field from your feature service as a hidden question (make sure it's a null in esri:type). When the survey is first created, this field will be empty because the feature was never submitted. Upon first submission the field will be populated with the submission time. 2. Add a question 'Are you ready to finalize your survey?' with only one answer in choice list - 'Yes'. 3. Put a condition in the question's read only field, that if EditDate is not empty (string-length(${EditDate})>0), then it's read only. This way, if the survey is re-opened, the user can't 'unlock' the finalize question. See attached xls as a sample. Of course in your case your read only condition should be string-length(${EditDate})>0 and ${edit_permission} = 'not allowed'. This way when an editor opens the survey it will be readable, but when a viewer re-opens it both conditions will be filled and the survey will be locked. Alternatively, you can skip the 'finalize' question and apply these conditions directly to all your questions. Let me know how it goes, Uri If this answer solved your question or if you found it helpful please mark it accordingly to help others who have the same question.
... View more
06-09-2021
07:25 PM
|
1
|
0
|
3463
|
POST
|
Hi Leigh, would you be able to provide the survey (or even better a cut down version with relevant rows only) that will allow to replicate the issue?
... View more
06-08-2021
11:12 PM
|
0
|
0
|
681
|
POST
|
Hola Cristian, Mi español es muy malo, entonces prefiero escribir en ingles...: Use repeat and count the number of repeats in a new hidden field: https://support.esri.com/en/technical-article/000021664 let's say that your count field is called 'count_repeats'. Add a constraints to this field that it must be >= 10 and a constraints error: 'You must submit at least 10 records'. Until the user fills 10 repeats it will return a constraint error and will not allow to submit. If this answer solved your question or if you found it helpful please mark it accordingly to help others who have the same question.
... View more
06-08-2021
10:36 PM
|
1
|
0
|
691
|
POST
|
Hi Larry, If you’re using the app (this solution is not applicable in the web version), you can: Add a list of permitted usernames (to your choices list) that are allowed to edit the survey. You can also have a list of approved users in a csv in the media folder and use the pulldata to check if the user is in the list or not. Bottom line: create a question by which you can differentiate if the user is allowed or not allowed to edit. Let’s call that question ‘edit_permission’. When the survey is opened it will automatically be populated as ‘yes’ or ‘no’ depending on your list of allowed users. For each question of the survey, add in the readonly field a condition: ${Survey status} = ‘completed’ and ${edit_permission} = ‘no’ This way, after the survey is initially submitted, the survey status becomes ‘completed. Then, next time it opens, if the user is not allowed, the condition above will be filled and the question will be read only. If the user is allowed, the condition will not be filled and the questions will not be read only, so it can be edited. If this answer solved your question or if you found it helpful please mark it accordingly to help others who have the same question.
... View more
06-08-2021
09:57 PM
|
2
|
6
|
3486
|
POST
|
Hi Taylor, Grouping determines the appearance of questions in the form. If the fields are hidden, why do you need them in a group? If you just want them to be easily located you can mark these questions with a different color in your xlsf. If you still want to group them, you'll need to add at least one visible question in the group, or maybe add them to another group that already has visible questions. If this answer solved your question or if you found it helpful please mark it accordingly to help others who have the same question.
... View more
06-08-2021
09:09 PM
|
1
|
0
|
945
|
POST
|
The errors above can also occur because items cannot be shared with group having users_update_items=True. This is defined when the group is created and cannot be changed later:
... View more
04-12-2021
09:56 PM
|
2
|
1
|
5846
|
POST
|
Hi @PatrickMcGarry1, Yes, all you need to do is replace date(decimal-date-time(today())+int(${number_of_days})) with date(decimal-date-time(${date_the_defect_was_reported_on})+int(${number_of_days})) Note that this solution doesn't work well on the web version, but seems to work fine on the Survey123 app. Cheers, Uri If this answer solved your question or if you found it helpful please mark it accordingly to help others who have the same question.
... View more
04-06-2021
10:59 PM
|
0
|
0
|
5587
|
POST
|
Hi @Unschuur , My solution above will hide fields for group B when they fill the survey, but you're right - viewing through the Survey123 web interface assumes they have certain rights that allow them to see all fields. As you mentioned, a Web App will probably be your best solution.
... View more
04-06-2021
09:52 PM
|
0
|
0
|
1227
|
POST
|
Hi @gihgigih It's a bit of an indirect solution, but what you can do is: 1. Convert the polygons to lines - you'll get one line for the perimeter of each building 2. Split lines at vertices - now every face of the building will be a separate line 3. Multiply the length of each line by the height attribute to get the frontal area (assuming it's rectangular). 4. If you want to know the direction of the front, create a new field and use the Line Bearing option in the Calculate Geometry tool. Subtract (or add, depending on the direction the line was drawn) 90 degrees to get the direction the front is facing. Hope this helps, Uri If this answer solved your question or if you found it helpful please mark it accordingly to help others who have the same question.
... View more
03-31-2021
08:11 PM
|
0
|
0
|
949
|
POST
|
Hi @RachelBu, To workflow to add your web map to your Survey123 is: 1. Add it in the linked content 2. In the Map tab, click on the basemap gallery icon and select your web map: 3. In your xlsf form, for the geolocation question, under body::esri:style colum, add: map=map ID. For example: map=de26a3cf4cc9451298ea173c4b324736 (you can get the ID from the web map's AGOL overview URL). 4. Publish your survey. If this still doesn't work, try to check permissions on layers. Hope this helps, Uri If this answer solved your question or if you found it helpful please mark it accordingly to help others who have the same question.
... View more
03-31-2021
07:31 PM
|
0
|
1
|
1103
|
POST
|
Hi @Unschuur, Create two view layers from your master layer. View A shared only with group A and View B shared only with group B. Duplicate your survey. Make survey A submit to View layer A. Make survey B submit to survey B (in submission URL in setting sheet in xlsf). On AGOL, in the view layer 'Visualization' page, determine which fields are viewable for each view layer: Give survey A to group A and survey B to group B. Whatever they submit will end up in your master layer for you/administrator to view and edit, but they will only be able to see what's on their view layer. Hope this helps, Uri If this answer solved your question or if you found it helpful please mark it accordingly to help others who have the same question.
... View more
03-31-2021
07:14 PM
|
0
|
2
|
1280
|
POST
|
Hi @PatrickMcGarry1, Just had to shuffle a few lines - see attached xlsf with corrected fields. Note that currently 'P4 Routine Maintenance' = 100 days. Change it in the calculation field to fit the number of days you're after. Also, consider changing the constraints error messages of the date to something that will explain the reason of error, e.g., 'Completion date must be in 7 days'. If this answer solved your question or if you found it helpful please mark it accordingly to help others who have the same question.
... View more
03-30-2021
05:51 PM
|
0
|
0
|
5610
|
POST
|
Hi @PatrickMcGarry1 , See attached xlsf with a sample on how to achieve that (sample is for 7 days). First you need to get the number of days as an integer. You can set this up in your choices or create another hidden field, let’s call it number_of_days to return an integer by using an if statement, for example if(selected(${priority_code},"P1 - 24HRS", 1, if(selected(${priority_code},"P2 – 1WEEK",7, etc.). Now that you have the days you can create a calculate field and calculate it as date(decimal-date-time(today()) +int(${number_of_days})) or date(decimal-date-time(now()) +int(${number_of_days})) Then put a constraint on your completion date field forcing it to be equal or bigger than the calculated field. Hope this helps, Uri If this answer solved your question or if you found it helpful please mark it accordingly to help others who have the same question.
... View more
03-29-2021
05:04 PM
|
2
|
0
|
5626
|
POST
|
Hi @Danielle_Journey, Would you be able to share the XLSForm? Or at least a cut down version of it with the problematic question?
... View more
03-25-2021
11:59 PM
|
0
|
2
|
1490
|
Title | Kudos | Posted |
---|---|---|
1 | 03-20-2022 04:24 PM | |
1 | 02-12-2020 03:12 PM | |
1 | 08-01-2021 05:04 PM | |
2 | 09-30-2021 06:22 PM | |
1 | 09-29-2021 10:46 PM |
Online Status |
Offline
|
Date Last Visited |
06-05-2022
05:38 PM
|