IDEA
|
This is f'ing insane. Get your head out of your a$$ esri. FIX THIS!
... View more
06-27-2022
11:20 AM
|
0
|
0
|
928
|
IDEA
|
I think that a good solution to mitigating privacy concerns would be to allow users to create a geofenced tracking exclusion zone. Its pretty common that field work is not based directly around where you live. So if all of your field work is done outside of the city in which you live you could exclude the whole city from your track logs. Or if your field work is done throughout your city, you could just geofence your neighborhood. It would at least make users feel that they had some level of control over any privacy concerns they may have. Also, please bring back the ability to set up a tracking schedule. It doesn't seem that this is possible from field maps.
... View more
06-08-2022
10:52 AM
|
0
|
0
|
920
|
POST
|
Can anyone else confirm that this actually works? Last summer, I did all of the things outlined in Aaron's response. Everyone in two different orgs had the "view location tracks" privilege. There were track views set up for each org with the necessary users added to the trackview. Then both trackviews were shared with the group containing members of both orgs. But still the trackviews were invisible to members of the opposite org. I have not tried it yet this summer but I'm very skeptical that it will work.
... View more
06-08-2022
10:01 AM
|
0
|
0
|
521
|
IDEA
|
How has this still not been addressed??? A truly fundamental feature that has been missing for many many years now. Its been obvious since the beginning that this is a bug. There's a column specifically for the date. It's just not populated. What exactly do you do with the billions of dollars you take in from governments and private industries around the world? Obviously your not spending enough of it on coders and programmers, when major flaws like this persist for half a decade or more. ESRI, you frustrate me to no end...
... View more
05-13-2021
09:23 PM
|
0
|
0
|
1639
|
POST
|
Yes the username is definitely correct. If I use crew_usernames=${username} it works as expected. I just have to make sure that there is only one username in the crew_usernames field.
... View more
04-21-2020
04:28 PM
|
0
|
0
|
1759
|
POST
|
Was there a change made that affected the use of ${username} in the inbox query statement? I am exactly copying the syntax as it is displayed on the Survey123 help page: Creator LIKE '%' + ${username} + '%' The only difference is that instead of "creator", I am using 'crew_usernames' which is one of my fields. So its actually: crew_usernames LIKE '%' + ${username} + '%' If I input my actual username instead of ${username} the expression works as expected. So that looks like: crew_usernames LIKE '%Andrew.MoskaLee@dec.ny.gov_nysdec%' So there is definitely a problem with the syntax surrounding the username variable. Does anyone know the correct syntax? Or have any other ideas? Thanks, -Andy
... View more
04-14-2020
12:33 PM
|
0
|
6
|
1879
|
IDEA
|
I also ran into this issue and created a different Geonet question about it. Subsequently this idea was pointed out to me, so I am pasting in my questions comments below: Before updating Arc Pro to version 2.5 when reducing the size of a pop-up window, a long field name would have its text wrapped so that it used multiple lines. This allowed you to see the corresponding data array on the right side of the pop-up with out scrolling over. Now the text does not wrap, so if you have one very long field name, you have to make the pop-up very wide, or you have to scroll over every time you want to see any of the corresponding data. Is there a way to turn text wrapping back on for field names in pop-ups? Can anyone at ESRI explain why this change was made? And does anyone know an easy way to add this functionality back to version 2.5? The comparison below uses version 2.0 because that was the only older version that I had access to, but the pop-ups behaved the same through version 2.4. The behavior changed when I updated to 2.5. Narrow pop-up on arc pro 2.0 (text automatically wrapping so you can see fields and data without scrolling) Wide pop-up on arc pro 2.0 (fields and data displayed in single line) Narrow pop-up on arc pro 2.5 (text not wrapping, can't see data without scrolling) Wide pop-up on arc pro 2.5 (must be this wide in order to see fields and data without scrolling)
... View more
03-31-2020
07:39 AM
|
1
|
1
|
1438
|
POST
|
Thank you Kory for your quick response, and thanks for pointing me towards the Idea page. I had done quite a bit of searching before I created my question, but I had not come across Pamela's question/Idea, as we seem to have used very different terminology to essentially describe the same issue. I will add my usecase to her idea. and give the idea an upvote. I appreciate your couple of quick workarounds and they may come in handy as a compromise between a fully tailored pop-up vs leaving things as is. The reason that I have so many long field names, is that they come directly from Survey123 questions. And since I deal with many different layers that were created from Survey123, having to individually set up all of the details of formatting each layers pop-up seems overly burdensome. Especially when the default behavior worked so well for all cases, up until the 2.5 update. Thanks again for your quick thoughtful response. It is very much appreciated.
... View more
03-31-2020
07:28 AM
|
1
|
0
|
557
|
POST
|
Hi Kory Kramer, Can you take a look at my question/issue above concerning pop-ups in Arc Pro 2.5? If my pop-up issue is not something that you are familiar with, could you point me towards someone else on the Arc Pro team that might have some insight. Thanks in advance for your time and consideration. Cheers, -Andy
... View more
03-31-2020
05:20 AM
|
0
|
2
|
557
|
POST
|
Can anyone at ESRI explain why this change was made? And does anyone know an easy way to add this functionality back to version 2.5? The comparison below uses version 2.0 because that was the only older version that I had access to, but the pop-ups behaved the same through version 2.4. The behavior changed when I updated to 2.5. Narrow pop-up on arc pro 2.0 (text automatically wrapping so you can see fields and data without scrolling) Wide pop-up on arc pro 2.0 (fields and data displayed in single line) Narrow pop-up on arc pro 2.5 (text not wrapping, can't see data without scrolling) Wide pop-up on arc pro 2.5 (must be this wide in order to see fields and data without scrolling)
... View more
03-25-2020
07:51 AM
|
0
|
0
|
557
|
POST
|
Before updating Arc Pro to version 2.5 when reducing the size of a pop-up window, a long field name would have its text wrapped so that it used multiple lines. This allowed you to see the corresponding data array on the right side of the pop-up with out scrolling over. Now the text does not wrap, so if you have one very long field name, you have to make the pop-up very wide, or you have to scroll over every time you want to see any of the corresponding data. Is there a way to turn text wrapping back on for field names in pop-ups?
... View more
03-18-2020
02:09 PM
|
1
|
4
|
710
|
POST
|
I am having this same problem. Can you elaborate on how to accomplish the workaround?
... View more
05-14-2019
09:29 AM
|
0
|
4
|
863
|
POST
|
I have a Username field type followed by a note. The 'name' of the Username field is 'user_nm'. The note is named 'usernote' with a label that says "Username: ${user_nm}". I'm using the android app. when i select 'Collect' the usernote field displays a note correctly. If i select Inbox and open up the survey from there the usernote field displays "Username:" and that is all. It is just blank after the colon. I am trying to get the username to display properly so that I can try to create a "Where clause" for my inbox . I have a field in my feature service that I populated with the usernames of the people that are assigned to each particular site. None of the "where statements" that I have created work. I've tried using "Contains" statements and I've tried using "Like" statements and nothing works. If I delete all other users in my "assigned_crew_userID" field, and just leave one username, then the where statement works correctly. But I need each site to show up in multiple users inbox's. Currently, within the "assigned_crew_userID" field i have the usernames separated by a single space. This post Help with Inbox? explains more about my situation. The two responses that I got were not very relevant. Any help would be appreciated. -Andy
... View more
05-13-2019
09:40 AM
|
0
|
1
|
268
|
POST
|
Our program does invasive plant control. We have about 2500 sites in our database, that we try to visit each year to do control work. We use Survey123 to document our control efforts. Much of the data about each site, such as owner information and site descriptors, is the same each year. Still crews must have the ability to edit all data points since owners do occasionally change. Our survey is quite long and detailed and has a number of repeats to capture multiple site visits and herbicide applications within a season. So we are trying to use the "inbox" and "sent box" features to manage bringing forward our old relevant data while being able to collect new information. Then access sent sites using the "sent box" to add repeat site visits. We have around 15 different crews that are each responsible for a portion of the sites. For the most part crews are only responsible for their assigned sites, but sometimes crews trade sites and so they need to be able to fill out a survey for a site that is assigned to a different crew. Currently I'm trying to figure out how to best manage the "inbox" feature. If I don't use a "where clause", then crews can see and access all sites, but the inbox feature only holds 1000 sites, and loading the surveys is quite slow. So then I tried adding a field to the connected feature service that contained the usernames of the crew members assigned to each site. Then using the where clause, I can set the field 'assigned_crew_usernames' to equal ${username} of the person filling out the survey. But that solution doesn't allow crews to access any sites that were not originally assigned to them. My next thought was to make 15 separate surveys that all point to the same feature service. The surveys would be identical in every way except for the inbox where clause, which would be set to equal the 'assigned_crew' field. That solution should work ok, but since this is our first year using Survey123, after many years of using SurveyCTO, I anticipate having to make changes to the Survey as the season progresses. Having 15 separate surveys to have to make identical changes to each time seems especially onerous. So does anyone have any suggestions as to how to best accomplish this work flow? One thing I thought about was trying to use the "username" method and making a separate survey with just one or two questions that points to the same feature service. The main question on the supplemental survey would be; What are the assigned_crew_usernames? Then crews could change the assigned_crew_usernames themselves, then return to the main survey and update the inbox. Would that method work? Would the inbox update with all of their assigned sites, each time they use refresh, including assigned sites that had already been completed earlier that season? Any help would be greatly appreciated. Thanks, -Andy
... View more
05-07-2019
12:10 AM
|
0
|
3
|
478
|
IDEA
|
I would like to be able to use conditional statements in the label field of XLSform. My current use would be to change the font color of a group label based on how many or which questions in the group had been completed. (i.e. The label would start out red. Then if all required questions, but not all optional questions were answered, the label would turn yellow. Then if all questions in the group were answered, the label would turn green.) I'm sure there are many more use cases for changing the font type and even the actual text of a label, based on the results of other parts of the survey.
... View more
04-08-2019
05:57 PM
|
6
|
0
|
564
|
Title | Kudos | Posted |
---|---|---|
1 | 03-31-2020 07:28 AM | |
1 | 03-31-2020 07:39 AM | |
1 | 03-18-2020 02:09 PM | |
2 | 04-06-2019 04:30 AM | |
6 | 04-08-2019 05:57 PM |
Online Status |
Offline
|
Date Last Visited |
07-12-2023
07:04 AM
|