POST
|
Hey All, I have written some Attribute Rule Constraints in Pro for a feature class that I have published into Portal to use in Collector. The Constraints and Constraint error messages that I have set work perfectly in Pro. However, when go into Collector and trigger a constraint, it simply gives a generic "Unable to submit - Unable to complete operation" message. So the Constraints themselves work fine. The issue is that my error message explaining what the issue is not transferring over. I know the field users will be confused when it doesn't really tell them what they did wrong that prevents them from submitting the point. Does anyone know if these messages actually transfer over into Collector somehow?
... View more
08-20-2020
11:26 AM
|
1
|
0
|
298
|
POST
|
Hello, Is there any chance of this functionality being available in an update in the future? I think this would be a great feature. My company hasn't been using Survey123 very long, but we have already been hung up a few times because of the fact you can't edit someone else's Survey. It would be great for others to be able to familiarize themselves with someone else's project and then be able to fill in for them if the Survey needs to be quickly edited if something arises. Especially when the original creator may be out of the office or on vacation and quick action is needed.
... View more
07-21-2020
05:46 AM
|
2
|
1
|
4344
|
POST
|
I did find a work around for this. Instead of "Displaying by Location", I displayed by the attribute (in my case, the Job_Status attribute). When you display it by the attribute, you then get the option to edit the symbology as well as change the names. Instead of giving it a real name, i just tapped the space bar so it would appear blank.
... View more
06-04-2020
09:54 AM
|
0
|
0
|
292
|
POST
|
I created some view layers off of a Survey123 form and put them in a web map to eventually use in an Application. The issue I'm having is that its showing the name of the survey (Field Inspection Survey Updated) next to each point. Is there a way to get rid of this, since it carries over into my Legend in my Application? I can obviously edit the name of the layer, but I can't figure out a way to get rid of that annoying text next to the point.
... View more
06-03-2020
09:24 AM
|
0
|
1
|
312
|
POST
|
I am having the exact same problem and came on here to check. I basically want to have a safety mechanism set to where the field users are protected from accidentally typing in the wrong date field in Collector, since we have multiple date fields. I'm getting the same weird date of 12/30/1899 as well. Here is how my attribute rule is set Have you heard anything on this yet?
... View more
05-06-2020
08:01 AM
|
0
|
2
|
1219
|
POST
|
James, I tried to set bot No and NA to 0 but when I did that, it would select both of them at once automatically if I chose either one (since they were both the same value). Even with the select_one option, it would pick them both no matter what unless I chose the Yes option. We still want to make sure that we capture when someone pushes the NA button so we can take that into account when we average the scoring later. If there's an NA, we will simply omit the question so that way they don't receive 0 points for something they didn't have the option to do. Here is the way that I fixed this issue. I used a max(int(${question1}), 0) + max(int$(${question2}),0) ....etc calculation to get my total points. Since the only thing of value was a "Yes" answer in my survey, it only looked for that and turned everything else into a 0 in my total calculation of points at the end. The issue now is that after I published it, the survey works perfectly fine on my mobile device. However, when I try to take the survey in the web browser format, it's still showing blank data in the calculation if a NA option is selected. That may be a bug from what I'm hearing, waiting for the team to get back to me on that one.
... View more
04-14-2020
02:00 PM
|
0
|
0
|
1402
|
POST
|
Hey all, I am trying to do a survey in which there is a scoring system set up. At the end, I want to add up all of the results into a grand total of points. Each question I have follows the same point system based on if you answered Yes, No, or N/A. "Yes" = 4 points. "No" = 0 points "N/A" = NaN When I add up all of the survey answers to a final "Grand Total" field, it gives me a blank answer if any of them are "N/A" (NaN). The calculation I have set up is this: int(${field1}) + int(${field2}) ....etc. All of my calculations work just fine when they select either "Yes" or "No"....but as soon as even one of the options is set to "NA", the result is totally blanked out (due to the use of the "NaN"). Is there any work around for this?
... View more
04-09-2020
11:35 AM
|
0
|
3
|
1547
|
Title | Kudos | Posted |
---|---|---|
2 | 07-21-2020 05:46 AM | |
1 | 08-20-2020 11:26 AM |
Online Status |
Offline
|
Date Last Visited |
01-11-2021
09:29 PM
|