POST
|
Ismael, shortly after posting my problem with the leading zeros, I found a way to make it work. I'm not sure exactly what I changed, I think it may have been defining the field type as string, but it has been working. Here is what the xlsx looks like now.
... View more
08-23-202301:17 PM
|
0
|
0
|
161
|
POST
|
@IsmaelChivite DM sent containing XLS and associated CSV. However, some more digging into this reveals that using the select_one_from_file was preventing the form opening correctly in the browser and giving me this error. The issue was that the name of my CSV contained a "_". Renaming it to remove the "_" resolved the error and fully populated the select_one_from_file
... View more
10-21-202205:26 AM
|
0
|
0
|
157
|
POST
|
Hey Zachary, That seems to have done the trick. Thanks again!
... View more
05-14-202112:58 PM
|
0
|
0
|
1120
|
POST
|
Hi @BarryKeight, This is expected. The username field is hidden and does not get updated (overwritten) when the form is opened in edit mode. Similar to other questions/fields in the survey, when you open from Inbox or Sent folder in edit mode, calculations do not automatically execute if they have an existing value. The user must select the recalculation button to update the value. Therefore as username is hidden the value cannot be udpated by user, and will not be overwritten by default. Regards, Phil.
... View more
04-29-202106:44 PM
|
1
|
0
|
696
|
POST
|
Looks like we see the error in Console, but everything is working correctly with our webhook. Thanks!
... View more
04-09-202107:40 AM
|
0
|
0
|
1148
|
POST
|
I just recently started seeing this problem in the Field App, but believe the Web Form to be OK. I can't say if it's new or not, but my users just started reporting that the leading zeros are being removed from select_one and select_multiple questions. I tried a few things like setting the TEXT field type and using the =TEXT() function, but when I test in connect, I can see the values are coming in as integers still, with the leading zero dropped. See screenshot below. Is there another way to do this?
... View more
03-25-202102:57 PM
|
0
|
0
|
1054
|
POST
|
Dear Survey123 Team: Do you have plans to include a fix for this issue in an upcoming update to the Survey123 application? Sincerely, Joe Flannery
... View more
03-16-202102:37 PM
|
1
|
0
|
379
|
POST
|
谢谢组长Albertus,但我相信有一个问题with that scenario. Both the form and feature layer need to be shared to the Group so the user can use and submit data through the form. Because my feature layer is used elsewhere with full permissions in other forms, the feature layer has full Add, Update and Delete permissions. In your scenario, the Add Only user could come across the feature layer and if they desired, delete or update a record outside of the Form...say in Data view of the Feature Layer page or similar. In order to make it so the users in the Add Only group can never delete or update a record, I have to create a View of the Feature Layer, set edit permissions on the Feature Layer View to be Add Only, and then share that with the Add Only group and connect the Survey to it via the submission url.
... View more
08-25-202004:28 PM
|
3
|
0
|
837
|
POST
|
Hello, I am following the code below from Attribute rule script expression examples—Geodatabases | Documentation almost identically (feature classes and field names differ obviously) and getting errors when executed in the browser/web app. The error is telling me I can't perform the edits outside an edit session (see screenshot of error). When executed within ArcPro the attribute rule is successful. Could this have to do with having Archiving enabled on the feature class being edited/updated? var fsAddress = FeatureSetByName($datastore, "Address_pnts", ["globalid"], true) var fsListAddpnts = Intersects(fsAddress, $feature) var AddList = [] var counter = 0 var noAddress = Count(fsListAddpnts) if (noAddress > 0) { for (var address in fsListAddpnts) { AddList[counter] = { 'globalid': address.globalid, 'attributes': { 'add_district_name': $feature.DistrictName } } counter++ } return { 'result': noAddress + ' addresses found in the district.', 'edit': [{ 'className': 'Address_pnts', 'updates': AddList }] } } else { return 'No address points in district.' }
... View more
02-20-202001:47 PM
|
1
|
0
|
223
|
POST
|
Setting the editing permissions with Survey123 instead of on the Feature Layer worked. Thanks for your help!
... View more
03-09-202001:51 PM
|
0
|
0
|
532
|
POST
|
Thanks Xander Bakker, I had seen that, but not had a chance to try. My preference would be to avoid the relationship class because there is a complicated web of how different feature classes can overlap and relate to each other. I'll give this a try.
... View more
08-21-202009:01 AM
|
0
|
0
|
1069
|
POST
|
This error can also be caused if there is a new query in the database and the if the users of the survey123 still have the complete list. Without any refresh of the inbox, you will get the "FID" message if the record is not more available in the database.
... View more
01-28-202004:56 AM
|
0
|
0
|
2461
|
POST
|
你好,我是难以使用的平均和我an function in an attribute rule. I am intersecting points with a polygon being inserted/updated and wish to get the average of a field value from all intersecting points. I am able to use the Sum and Count functions just find and my current workaround is to use both to get the Average. When I use Average or Mean, I first got an error about how the field name was used to run the function. I was able to fix that by calling it differently (you can see the difference in the expression below). The error I am getting now is below. My Arcade expression: var cpm_field = "Counts_Per_Minute" var fsGS = FeatureSetbyName($datastore, "sde.blah.Gamma_Survey",[cpm_field],true) var fsGSIntersect = Intersects(fsGS ,$feature) var result_avg = null if (Count(fsGSIntersect) == 0) return result_avg ; else //result_avg = Sum(fsGSIntersect,cpm_field)/Count(fsGSIntersect) My workaround //result_avg = Mean(fsGSIntersect,cpm_field) Does not work result_avg = Mean(fsGSIntersect,fsGSIntersect[cpm_field]) return result_avg ;
... View more
12-03-201904:01 PM
|
0
|
0
|
374
|
Title | Kudos | Posted |
---|---|---|
1 | 03-25-202104:28 PM | |
1 | 03-25-202109:56 AM | |
3 | 01-06-202110:25 AM | |
3 | 08-25-202004:28 PM | |
1 | 08-19-202007:50 AM |
Online Status |
Offline
|
Date Last Visited |
2 weeks ago
|