POST
|
I thought I was getting lucky by publishing one table at a time and then copying the successfully published sections in to a merged survey until I got to table number 16 where I started going through the same error. I wonder if it is a coincidence with my first bigger merge that it started failing at table 16. I wonder if 15 is a magic number of related tables. I'd really hate repeating the whole process though. Can you please rephrase what you mean by: " either as one for (extended by using a repeat with repeat_count of 1"? If I understood this correctly you are assuming that for each table there is only one feature count. The number of features per table is dynamic. For the second one, how can a 'component inspection' be reused as a group question for each table? Is there an available samplthat you have in mind?
... View more
09-26-2017
11:43 AM
|
0
|
2
|
658
|
POST
|
I followed your suggestion and it did not work for me. I am in the tedious process of publishing a service for each of the table to validate the form, field names, schema and see if it publishes. So far out of the sixty, I'm halfway and each form published successfully. I'll merge groups of twenty later and see if it works. The biggest concern I have is size of the form - questions and the choices. But I've seen comments on the forum which has far more excel rows than Even if I merge all these sixty tables together I'll still be below the 500 question limit of Portal. While the nulls show up on the schema I assume publishing ignores them, right. Do you have any suggestion on what to look for in the diagnostics why the form is not being created?
... View more
09-26-2017
05:01 AM
|
0
|
4
|
658
|
POST
|
I've been having some challenges trying to publish this form. Its a QA form and when its finished it will include about 60 x 15 questions (six are esritype::null). The number 60 represents sixty tables to be QC'd separated by groups in the survey. The survey will be used by a QC analyst and on each group there's two select_multiple list which are pre-populated from the choices worksheet. I automated the creation of each group of questions into a temporary csv table. From this csv I copy and paste each grouped questions to the survey xlsform, incrementing the process one group of questions at a time. As I add a group or questions, I save the xlsform, test and then publish. (Note: This iterative process created multiple feature layers for each publish. At some point I started deleting duplicates, retaining only the last FL from the most recent successful publish) After going through the iterative process 18 times, the publishing stopped working. Creating form will progress bar will stay in the middle and then after 15-20 minutes will get to the end and it just stay there until I terminate. I'm attaching my last successful excel file (1_QA) that was successfully published and the version that where failure started (2_QA) . attribute_count.csv is an external choice csv for both. We use Portal for ArcGIS 10.5. Any ideas to troubleshoot or fix are welcome. Thanks!
... View more
09-25-2017
10:15 AM
|
0
|
6
|
901
|
POST
|
Your workflow is my end goal although slight different using Portal and not AGOL. I wonder if you are using an existing feature layer or created your schema from Survey123? I think using an existing feature layer to build your Survey may help. I've tested a feature layer but have not gotten as far as combining the two workflows (Survey123 and AGOL web map) yet.
... View more
09-21-2017
05:18 AM
|
0
|
0
|
442
|
POST
|
After I read the thread on AutoIncrement integer that's how I ended up with this question. A hidden, null field with a default value of 1. Not ideal but it works.
... View more
09-19-2017
10:01 AM
|
0
|
1
|
1307
|
POST
|
I just asked this question in the blog. I agree the number is already there its just a matter of exposing it.
... View more
09-19-2017
09:33 AM
|
1
|
0
|
6681
|
POST
|
I wanted to know the number of repeats in my repeat section and store it as an integer. Questions in my repeat section are multi-select questions so I'm using count-selected and I cannot use them to count the number of repeats. So on the picture below, I want to capture the number 3 or whatever the max number of the repeat.
... View more
09-19-2017
07:17 AM
|
0
|
3
|
2269
|
POST
|
This is a great workaround for the email or notify feature.I'll definitely use this. Thanks for sharing your xlsform.
... View more
09-06-2017
10:20 AM
|
0
|
1
|
960
|
IDEA
|
On the schema preview of a survey, it would be nice to have total number of questions or a line number before the Field Name of the table.
... View more
08-23-2017
09:16 AM
|
1
|
1
|
196
|
POST
|
James Tedrick, that's good news. I did figure out a workaround to the 500 questions limit for my survey. I made the question for each attribute into a select multiple question inside a repeat, then use the count-selected function. So instead of number of attributes per feature; it becomes a feature score. It is unlikely that there would be more 400 features in any given job.
... View more
08-21-2017
02:03 PM
|
0
|
0
|
1649
|
POST
|
I wonder is there a way that a question can only stay in memory and not as a stored value. I'm using a question to calculate points or to score and I have about 2,000 questions that all I'm doing is accumulating a point for every question that's been checked. This is for a QC project that checks every field of 60 tables. A point is an error. And the accumulator is used to subtract from the perfect score. I'm only concerned with the points accumulated on the 60 tables.
... View more
08-17-2017
12:48 PM
|
0
|
3
|
1649
|
POST
|
Would changing this basemap with my own online base map and my own default location help?
... View more
08-12-2017
08:36 AM
|
0
|
1
|
811
|
POST
|
Mine is similar but on a select_one, having a default value based on an expression or calculation on survey load or when I open a form. If I hard code a choice name in Default it works. If I use a survey column name in default, select_one breaks. If I use pulldata on the calculation column, select_one breaks as well. Lastly, I tried the survey name of the field that used the pulldata calculation and the behavior is the same.
... View more
07-27-2017
04:45 AM
|
0
|
1
|
670
|
POST
|
I figured out the cause of the error message. It was the implementation of the code for the deep linking URL created by a hyperlink calculated and stored in a note or text box. This implementation is illustrated in this post: https://community.esri.com/message/694045-mobile-app-url-scheme-in-survey123-not-working The solution is remove the calculated note or text box. Does not allow me launch the Foreflight app from Survey123 unfortunately. Interesting the Connect did not catch the error in validation, the sending of the data in Portal is the one rejecting the surve.
... View more
07-27-2017
04:09 AM
|
2
|
0
|
2802
|
POST
|
On Survey123 app, I completed my survey and I always get this error. I also have three other users get this error message. We are using Portal for ArcGIS 10.5 and Survey123 app 2.3.29. Any ideas?
... View more
07-26-2017
11:43 AM
|
1
|
5
|
3813
|
Title | Kudos | Posted |
---|---|---|
1 | 06-25-2017 08:18 AM | |
1 | 11-08-2017 04:20 AM | |
1 | 09-19-2017 09:33 AM | |
1 | 04-24-2018 01:36 PM | |
1 | 06-15-2017 04:01 AM |
Online Status |
Offline
|
Date Last Visited |
03-13-2024
07:47 AM
|