|
POST
|
How can I do leading spaces? It keeps striping them out when using Arcade in a Pop up. This return "\n" + " Line Number Issue! Found: " + txt Does this - notice no spaces - I want to indent it. Ideas? Thanks
... View more
04-17-2019
09:25 AM
|
0
|
7
|
3717
|
|
POST
|
Our Users also hate the new large and centered Update Point button. We keep having users change a Attribute then tap Update Point - which then moves the point on us! It should really say Update Point Location or something like that. With Submit hidden way at the top right it seems to the user the only way to save. I would personally hide that Update Point Location button down at the bottom or something also. Changing a location should not be that easy.
... View more
04-17-2019
09:00 AM
|
0
|
0
|
2703
|
|
POST
|
Also tried using FeatureSetByName($map,"Name") but that did not work in the app either. Thanks
... View more
04-17-2019
08:56 AM
|
2
|
2
|
3590
|
|
POST
|
Same question. I switched mine to use $map so it theory it should work. But I just get blank. if ($feature.EvalStatus == "Eval") {
var sql = "PlotKey = '" + $feature.PlotKey + "'";
var tbl = Filter(FeatureSetByName($map,"GAP"), sql);
var txt = ''
for (var f in OrderBy(tbl,"LineKey")) {
txt = txt + Right(f.LineKey,1) + '-'
}
txt = Left(txt,Count(txt)-1)
if (txt != '1-2-3') {
return "\nLine Number Issue! Found: " + txt
}
else {
return ''
}
}
else {
return ''
} Thanks
... View more
04-17-2019
08:51 AM
|
0
|
13
|
6048
|
|
POST
|
Use an if statement. So one field does a pulldata. The next field does an if on that pulldata field to check if it found anything. So something like if(q1='','use value since feature not found",q1) Number of questions is not really a concern for the user. If you can get the form fast the backend does not matter. I did have a form that did some calcs like the above. In the end we took them back out because 1 - it did slow down the form since my lookups were huge and 2 - people were then using these temp calcs in actual analysis without doing QA and all that. Also just to check - are your lookups and lookup values inside of a repeat? I found a speed bug with that.
... View more
04-17-2019
06:54 AM
|
0
|
3
|
3896
|
|
POST
|
I think there was a post somewhere about hacking the registry to get the HKEY Local User set properly. I can't find it now. I never tried it though. One of the reasons we are doing 123 is to dump windows tablets and go to Android/iOS. I did have a coworker trying and never got it just right i think.
... View more
04-16-2019
02:18 PM
|
0
|
0
|
3462
|
|
POST
|
The old 123 versions would look at your list, pick the longest item, then use that as the field size. This of course becomes a pain so now 123 will default all the lists to 255. How old is your Connect? The newer versions can handle some of these changes now.
... View more
04-16-2019
07:23 AM
|
0
|
3
|
3081
|
|
POST
|
No the new version will only update if you hit the green refresh. You can also stick a once() around it. And I meant use the Calculation column not the type. So say text type and then calculation.
... View more
04-16-2019
07:15 AM
|
0
|
1
|
2797
|
|
POST
|
Best way I have found is Rename your current survey to SomethingOLD.xlxs Upgrade your Connect In Connect create a brand new form Open your Old form Select all the data form rows in the old - skipping the top row of field names Go into the new form and Right Click - Paste Values!! Very important part or you will bring all the old formulas over. Go in and check the End columns. Since there were some adds now you will see some columns a bit off near the end. Esp field length for me. If you do move them again make sure to use Paste Values. Note This also helps fix up all those times you Ctrl C-V too fast and move formulas to the wrong column. Which i do a lot. Then don't forget to do the Settings page and Choices page! Save this new form with the original form name in the original form directory. Then just open in Connect as normal and it will pick up all the changes. I was able to update forms from 2.1 to 3.3 this way. Sometimes the drop downs are still a pain. If so look at the old form - click the field/row then Data Validation button. You can copy and paste the part where it is grabbing the list over the new form. (Note this is also where you can turn off those annoying hovering yellow boxes - by going to Input Message tab then uncheck Show input message.) I wonder what this does to the .info file but I have had no troubles. Hope this helps.
... View more
04-16-2019
07:08 AM
|
0
|
2
|
1734
|
|
POST
|
I have been using a calculation for now to get around it. But it has been a year on this one...
... View more
04-16-2019
06:48 AM
|
0
|
3
|
2797
|
|
POST
|
You may be hitting this known issue. https://community.esri.com/thread/231800-survey-allowed-to-be-submitted-when-required-questions-are-not-answered Workaround is to put a group around it.
... View more
04-15-2019
03:08 PM
|
1
|
1
|
7079
|
|
POST
|
I worked with the admins some more and we may have a workaround. Posting in case it helps someone. If we make the Profile of the user that is not being found Public - then it does find them. We do not allow public normally but the admins are willing to make it public, add to group, turn public back off to get around the bug for now. We think we could also change owner each time but not tested. Thanks
... View more
04-15-2019
11:50 AM
|
0
|
0
|
1482
|
|
POST
|
See this post for a kindof workaround. https://community.esri.com/thread/231800-survey-allowed-to-be-submitted-when-required-questions-are-not-answered
... View more
04-15-2019
09:50 AM
|
0
|
0
|
3652
|
|
POST
|
Thanks that totally worked! In my case I have a few questions that naturally could be a group and so this helped me get around most of what I needed. Not all though. This really helps with one of the big requireds we needed. Thanks again.
... View more
04-15-2019
08:00 AM
|
0
|
0
|
5785
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 2 weeks ago | |
| 1 | yesterday | |
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago | |
| 1 | 2 weeks ago |
| Online Status |
Online
|
| Date Last Visited |
2 hours ago
|