|
POST
|
We are seeing it on the Active 2 also. Do you have lots of apps open at the time? How much free space on the tablet? Do you have any management software like MaaS360 or anything else that encrypts the device? We are testing all of this.
... View more
05-14-2019
10:17 AM
|
1
|
7
|
2042
|
|
POST
|
You cannot remove it that is impossible. Use a constraint to yell at them if they do it. Note your text field needs to be outside the repeat. It should all be in the post. Put this is the constraint of the large text field not(contains(substr(${AllPlantsCheck}, 0, string-length(${AllPlantsCheck}) - 3), ${SpeciesList})) Create a large txt (or note) field outside the repeat. i did text so users can copy and paste it. Add a calc joining the fields from the repeat join(", ", ${SpeciesList}) Set a constraint on this join field (not the field) - the trick here is to remove the last entry since it is the one you are trying to add currently. So like this not(contains(substr(${AllPlantsCheck}, 0, string-length(${AllPlantsCheck}) - 3), ${SpeciesList})) --If you do not do this it immediately adds to the list then complains it is already there. --(note my plant codes are 4 chars. so if i remove the last 3 chars it will not find what I just added) It can be funky if you go backwards and then change something but it still seems to work ok. I even built on exceptions to the rule. If it contains a XXXXX generic code then the repeat is allowed. Like contains(${SpeciesList}, "XXXX") or not(contains(substr(${AllPlantsCheck}, 0, string-length(${AllPlantsCheck}) - 3), ${SpeciesList}))
... View more
05-14-2019
08:42 AM
|
0
|
5
|
4103
|
|
POST
|
This has been posted a few times - See my post here. https://community.esri.com/thread/233596-populate-values-in-selectmultiple-from-previous-repeat
... View more
05-14-2019
07:40 AM
|
0
|
7
|
4103
|
|
POST
|
How about create a second field that is hidden. Use a calculate on this field then base the relevant off this second field. Use once but You may need to add a if so once(${Field1}) or if(${Field1} != '', once(${Field1}),'')
... View more
05-14-2019
07:37 AM
|
0
|
1
|
2402
|
|
POST
|
See my workaround here. https://community.esri.com/thread/232052-counting-unique-selections-across-repeats
... View more
05-10-2019
08:10 AM
|
2
|
1
|
3572
|
|
POST
|
Are your choices a set size? My plant codes are all 4 chars. So you could have a field outside the repeat that has a calc of join(). Then you could calc in the next repeat something like (just pseudo code) substr(joinfield, stringlength-4) to pull off the last value and use. I am using this method to check for dups in my repeats. If the size varies you would need a find in string type operation but 123 does not have this yet.
... View more
05-10-2019
08:07 AM
|
0
|
0
|
1099
|
|
POST
|
Just had a big field training day. Several users ran into memory errors I think. In this case we have a large repeat that we set to a repeat_count of 50. Randomly it would blank one of my main calc fields - which breaks my entire form. The user is then stuck as they cannot go forward or backward. It is usually between repeat 11 and 15. Same tablet may be fine for a few runs then dies. We also see some relevant fields never show up when this happens. These are Samsungs but my iOS dies sometimes also. It did seem to be when the user had other apps open, but not always. It also seemed to happen only on tablets that had the Mass360 management software on them - but this is not confirmed. So the guess is memory issue. For now we are taking out the repeat_count in the hope that a user could delete the bad repeat and try again. Crew is very nervous about this as they may be out in the field for a week at a time. This is also an issue on 3.4. We also are trying to teach users to get around the repeat wrong error issue I posted about earlier. Basically our last repeat has some questions that do not appear on repeat 49. If a user is on 50 it tells them they are missing a required - even though they are not. Go to 49 and then it submits. So far this bug is still in 3.4. Big bug. And of course the required issues bug. I now have 4 major bugs open in 3.4. I am rather disappointed that 3.4 is now pushed back again to June! Letting the major bugs of 3.3 go this long, and past the standard field season kickoff, is really not cool. If anything roll back to 3.2 at this point (can we get it). You cannot leave core bugs out there that long. I am personally taking a LOT of heat for this. Please in the future consider lining up new releases with field season. Also more testing please. We have a crew of hundreds siting and waiting on this! If there is a bug like this it could cause a crew to stay late - and maybe get hurt out there! Again please consider how some of these things affect us and how many people are on us about it. The 123 team has been awesome the last 3/4 years but this one was a big opps. Thanks
... View more
05-10-2019
07:28 AM
|
0
|
1
|
3557
|
|
POST
|
https://community.esri.com/groups/survey123/blog/2018/07/06/understanding-reverse-geocoding-in-survey123-30
... View more
05-07-2019
08:25 AM
|
1
|
0
|
4024
|
|
POST
|
We do this using a web map/collector to store the features then launch from there passing the ID to 123. Then there is a backend relationship class that ties it all together. This way 1 form is 1 record in the FC (so editor tracking, GPS of the visit vs assuming they were at the correct spot, etc all come along). Plus then they cannot change previous data. I think the inbox method would be a mess and keep getting larger. You can then have 1 map per crew. As said above use an assigned to field.
... View more
05-07-2019
07:37 AM
|
0
|
0
|
1116
|
|
POST
|
When a field is hidden due to a relevant it is always blank string ''. So you are passing it in but it is blanking due to the relevant.
... View more
05-03-2019
09:58 AM
|
1
|
1
|
1062
|
|
POST
|
I do it this way. I get the names via relates since I need to. #-------------------------------------------------------------------------------
# Name: Survey123 Export Photos to File System.py
# Purpose: Exports the photos from the Survey123 Photos form from a exported GDB
# Assumes state dir is already there
# Will check for and create PrimaryKey dir if needed
# For now it will overwrite every file as it goes. Plus and minus to this.
#
# Author: dbrowning
#
# Created: 10/31/2018
# Modified: 10/31/2018
#
#
#
#-------------------------------------------------------------------------------
import os, arcpy
# vars--------------------
inDB = r"Survey123InputDataOct11.gdb"
# to get the names and PrimaryKey
photoForm = "AIMPhotos"
# actual attachements table
attachName = "AIMPhotos__ATTACH"
outDir = r"SurveyTest\Photos"
# should be standard
fldBLOB = 'DATA'
fldAttName = 'ATT_NAME'
dateLoadedInDb = "2018-09-01"
# vars--------------------
# join to AIMPhots form to get the PrimaryKey and state info
# Note the first year they called it PlotKey instead
arcpy.MakeTableView_management(inDB + "\\" + attachName, "attachView")
arcpy.AddJoin_management("attachView", "REL_GLOBALID", inDB + "\\" + photoForm, "globalid")
# funky due to the join
fieldList = [attachName + "." + fldBLOB, attachName + "." + fldAttName, photoForm + ".PlotKey", photoForm + ".Office", photoForm + ".filename_T1", photoForm + ".filename_T2", photoForm + ".filename_T3" \
,photoForm + ".filename_Soil1", photoForm + ".filename_Soil2", photoForm + ".filename_Soil3", photoForm + ".MiscPhoto1filename", photoForm + ".MiscPhoto2filename", photoForm + ".MiscPhoto3filename"]
with arcpy.da.SearchCursor("attachView", fieldList) as cursor:
for row in cursor:
binaryRep = row[0]
# save to disk
# build output path of base + State + PrimaryKey (PlotKey + DateLoadedInDb)
# for now need to check for blank PlotKey and blank Office - which should be fixed already
if row[3] == None or row[2] == None:
print "Warning Null values found in the Office or PlotKey field. Skipping photo. Must fix!!"
print " ATT_NAME is " + row[1]
else:
baseOut = outDir + "\\" + row[3][:2] + "\\" + row[2] + dateLoadedInDb
# check to see if already PrimaryKey dir there - if not create it
if not os.path.exists(baseOut):
os.makedirs(baseOut)
# Need to get the actual file name from the right field. No real other way to do it with a SC so had to write it out
whichPhoto = row[1].split("-")[0]
if whichPhoto == "T1":
fileName = row[4] + ".jpg"
elif whichPhoto == "T2":
fileName = row[5] + ".jpg"
elif whichPhoto == "T3":
fileName = row[6] + ".jpg"
elif whichPhoto == "Soil1":
fileName = row[7] + ".jpg"
elif whichPhoto == "Soil2":
fileName = row[8] + ".jpg"
elif whichPhoto == "Soil3":
fileName = row[9] + ".jpg"
elif whichPhoto == "MiscPhoto1":
fileName = row[10] + ".jpg"
elif whichPhoto == "MiscPhoto2":
fileName = row[11] + ".jpg"
elif whichPhoto == "MiscPhoto3":
fileName = row[12] + ".jpg"
# in case some / got in there. this should not happen now!
fileName = fileName.replace("/","")
# save out the file
open(baseOut + os.sep + fileName, 'wb').write(binaryRep.tobytes())
del cursor
... View more
05-03-2019
09:04 AM
|
2
|
0
|
5544
|
|
POST
|
Esri starting blocking this back at 10.2. We went round and round with them trying to get it back. Some said it was on purpose, others not. Never got anywhere on it. I got around it by keeping a machine around with 10.1 on it. The other way was to make a Mosaic dataset with the service inside of it. Sorry do not remember the details on how to do it exactly but give it a shot. I could ask if someone really cannot get it. Be careful on the size you use. Download too much basemap in 1 day and they will block you. Oh and I think Pro worked for a bit but not sure it still does.
... View more
05-03-2019
08:40 AM
|
0
|
0
|
2481
|
|
POST
|
Only works in Aurora builds but you can use Arcade to calc the lat long. I have also done distance in a 123 form. Have not done area yet. var originShift = 2.0 * PI * 6378137.0 / 2.0;
var lon = (Geometry($feature).x / originShift) * 180.0;
var lat = (Geometry($feature).y / originShift) * 180.0;
lat = 180.0 / PI * (2.0 * Atan( Exp( lat * PI / 180.0)) - PI / 2.0);
return lon + " " + lat;
... View more
05-03-2019
08:21 AM
|
1
|
0
|
2964
|
|
POST
|
Survey123 has full exif support. You could launch a 123 form from Collector at each spot - sending over the LineID each time. Have a GPS question that logs it in the form and/or use exif. Then create a relationship class from the lines to the forms. Each photo then becomes its own feature. There is a lot you could do with this. Launching 123 from Collector has been great for us. Hope it helps.
... View more
05-03-2019
08:09 AM
|
1
|
0
|
1855
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 07-08-2026 07:34 AM | |
| 1 | 3 weeks ago | |
| 1 | 07-08-2026 03:46 PM | |
| 1 | 07-08-2026 03:08 PM | |
| 1 | 07-08-2026 03:15 PM |
| Online Status |
Offline
|
| Date Last Visited |
Thursday
|