|
POST
|
This bug is marked as not to be addressed but it may be working now? First test failed but then I got it to go I think. https://support.esri.com/en-us/bug/the-make-feature-layer-tool-does-not-honor-feature-sele-bug-000144726
... View more
06-12-2025
01:17 PM
|
0
|
0
|
1210
|
|
IDEA
|
We have been trying for months to get this to go working with Esri teams and we are still stuck. I thought I posted as an idea but I guess not. We have a org wide ArcPro toolbar with all our shared tools on it that has been great. But it only allows regular toolboxes and not geoprocessing services. This means we have no way to share these services out. Regular toolboxes are rather limited in needing the correct packages, have to backhaul data to Pro, and need for extension licenses. Geoprocessing services solve all of these issues. But with no way to add to a toolbar or even favorite the services we have no way to get them to our users besides a search in the Portal section of catalog. Seems like it would a pretty easy add so hoping this can happen. We want to be able to use geoprocessing services toolboxes anywhere we can use toolboxes really. Should be interchangeable. Thanks @KoryKramer for looking into this! thanks a lot
... View more
06-12-2025
12:43 PM
|
4
|
1
|
504
|
|
POST
|
I figured it out. This new checkbox to Remove Default value in Pro 3.3 while publishing a GP tool totally breaks the ... menu. That is a weird one and must be a bug. Also note you must manually set the Input mode above that to User defined value. And it will flip back to Choice List every single time you overwrite as it flips back all the time.
... View more
06-12-2025
08:09 AM
|
0
|
0
|
1785
|
|
POST
|
Still cannot find this. Tools seems to add and remove from the list at random. I also wonder why this list is not a checkbox vs a radio? In Pro for that exact same tool we can pick a layer, add from file, or draw. I thought at saw this before in WAB but we cannot get it. We had a demo for users all setup and then the tool we wanted disappeared from the Set as input list and we cannot figure out why. Thanks
... View more
06-11-2025
01:48 PM
|
0
|
0
|
1801
|
|
IDEA
|
We would really like a way to group tables in the layers widget. Even better we would like to add tables in with the layers in groups. We have 3 divisions that look great when the layers are grouped but the tables just end up in a pile at the bottom. The users are getting confused as to why the tables are not right in with the layers as the tables are related to the main layers. I am not sure why tables are forced to be separate? If we could have them all together it would match our logical organization. At the very least we would want to also group the tables so the list is not so long and is better organized. We have way more tables than layers which is common. Thanks a lot
... View more
06-09-2025
11:50 AM
|
2
|
6
|
1112
|
|
POST
|
We were hoping to color code these so they are not all Blue but not seeing a way. Is this possible? thanks a lot
... View more
06-06-2025
01:24 PM
|
0
|
1
|
573
|
|
POST
|
Can you use that concat field for the relevant of pulldata? Or still dependency?
... View more
06-05-2025
11:10 AM
|
0
|
0
|
1100
|
|
POST
|
That almost sounds like a speed issue hitting the service. Hmm long shot but try adding a calculationMode=always to the pulldata line. It may not like it but worth a shot. Are you using a concat to make treatment points?
... View more
06-05-2025
09:32 AM
|
0
|
2
|
1111
|
|
IDEA
|
I have talked to @ChristopherAllen on this in the past but I guess I never made an idea. I would like to be able to match the colors in a histogram chart to the map symbology. Currently a histogram is all one color. We have users doing this in R with ease. For now we are having to make the map in Pro and also do the histogram in R and it is a ton of work. I am really trying to get users from R to Pro but this one has been a big stopper for us. Pro has to keep up with R! Example from R. thanks a lot!
... View more
06-05-2025
06:34 AM
|
6
|
1
|
611
|
|
POST
|
Still looking for this or chart across layers in general. We are trying to see causality. I do not really get charting just one layer.
... View more
06-05-2025
06:20 AM
|
0
|
0
|
795
|
|
POST
|
Forgot but have you tested setting a relevant on the calls to check for the lat/long being filled in first. like string-length(${DLat}) > 0. I am still not sure on the round as the order of operations it runs the calcs comes up again and again. There are tons of posts of pulldata not working properly when it is inside a function. The form does not run calcs from top to bottom. It does things more by the type. So runs defaults, then appearance, then calcs, then pulldata kind of thing. pulldata is just so picky and you are stringing them together by pulling the lat/long. It could be running the PLSS calls before the lat/long is there. And the fact it happens on all of them. You could also test calculationMode=always on these just to see.
... View more
06-05-2025
05:30 AM
|
0
|
0
|
944
|
|
POST
|
My thought would be its running the search before the geopoint gets filled in. Does the question have say a relevant on it to wait for the geopoint to populate first? I think you are saying you have a geopoint calc from another geopoint? That could cause the delay or the order is off. It probably does a the search appearance before the calc for the geopoint. Common issue.
... View more
06-04-2025
02:38 PM
|
0
|
4
|
1147
|
|
IDEA
|
I asked this in person a few years ago now and they said it was and "easy add" but 2+ years later I am still not seeing it so starting a post. It may have been @JonathanUihlein who I love talking to each year Dev Summit! New Map Viewer We can group layers which is nice esp on big maps. Big use case is to have our Reference layers in a different group than our own data. But you cannot group the tables section at all. So it turns into a garbage pile fast. Can we please add grouping to tables. Most of our data is tables so we really need it. In general we should be able to work with tables the same as layers at all times. Even better would be to NOT separate tables into a different section than the layers. I personally cannot think of a single use case where I would not want to see my layers and related tables all together in a nice neat group. Our users are always having to go hunt around and complain about it daily. Esp now that the Show Related Records button is gone (BTW bring that back ASAP) it is so hard for users. Pro can now group layers and tables (which is sweet thanks) but even if we do this and publish Map Viewer just pulls them back apart. Even in Pro tables are still stuck at the bottom which I also wish would fixed. Why do we want tables and layers right next to each other - for related tables! Esp with Survey123 if I have a main parent layer and then a related data of table from a repeat the user needs to somehow know which table matches the layer. Now they have to go hunting down to the bottom, or worse go to a completely different map section and try and find it. With several forms in one map this gets to be a lot of work flipping back and forth. BTW I would love to be able to add other items in the map too like links to PDF help files. thanks a lot!
... View more
06-04-2025
02:00 PM
|
5
|
0
|
368
|
|
POST
|
This seems to point to that and makes some sense Performing an Intersect on a Service: When performing an intersect analysis on a layer service, the resulting layer will inherit the scale visibility settings of the original layer service. If the intersect analysis is performed within the layer's defined scale range, the resulting layer will be displayed. If the intersect analysis is performed outside of the layer's defined scale range, the resulting layer will not be displayed.
... View more
06-03-2025
01:03 PM
|
0
|
1
|
2948
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 07-08-2026 07:34 AM | |
| 1 | 4 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 |
Online
|
| Date Last Visited |
Thursday
|