IDEA
|
I just go to this issue in our evolution. We use SQL Server as the back end DB. Traditional versioned DB starting to slow down? Just consolidate it. Worked great for the last 15 years. Branch Versioning is the only method being used by the Utility Networks and there's no way to get rid of old rows? That's totally unacceptable in my book. You can't tell me that all that edit history hanging around won't affect performance. Our DB's are growing at an exponential rate! Not to mention that any SQL drilling returns the garbage rows too (as was said above). Pretty sure I can make a view in SSMS to find the latest record on the base table, drop the garbage, but resolving the branches is harder. Come on ESRI, I WANT to like Pro and the direction we're going, but they sure are making it harder than it needs to be.
... View more
03-16-2023
01:10 PM
|
0
|
0
|
1487
|
IDEA
|
We also need a way to capture signatures in Field Maps similar to Survey123. Field Maps is a great addition to the toolbox but signatures are a fundamental part of almost any forms. Please escalate this!!
... View more
12-05-2022
04:49 AM
|
0
|
0
|
631
|
POST
|
That is totally awesome. I had a feeling it was possible. It navigates to the correct feature without reloading which was my main objective. I see it pops up the attribute list version as opposed to the custom popup. Not a huge deal. If the user clicks the 'searched' feature, it brings up the custom popup and away we go to the next hydrant. Don't suppose you know how to force the custom popup from the search result? Regardless, this is winner, winner, chicken dinner. Thank you!!!
... View more
03-12-2021
11:51 AM
|
0
|
1
|
533
|
POST
|
In Field Maps I would like to have a feature's popup be able to navigate to a different feature. For example, for hydrant flushing, once the staff person completes this hydrant, the user could click on a link to the next hydrant. My features already have a field that contains the next hydrant ID. This is like a hyperlink parameter but I don't want to reload the map each time. It would effectively put the hydrant ID into the search box and reposition map to the result.
... View more
03-08-2021
05:13 PM
|
0
|
3
|
626
|
POST
|
Pretty sure we are doing this right and meet all system requirements (Collector etc work just fine). From an Android device. Confirmed we can get to our AGOL data.
... View more
11-03-2020
02:49 AM
|
0
|
1
|
945
|
POST
|
Feature Service support definitely fits our workflow much better. I wasn't aware of the new functionality. I set it up and just went into maintenance mode. Definitely will look into that. Thanks!
... View more
08-05-2015
11:35 AM
|
0
|
1
|
461
|
POST
|
They are feature layers that are edited in the web map. I am not bumping into the 256 character issue. It has been a while, but I believe I started with the .csv workflow in the storyboard documentation. Appears that there is some intermittent cases where the Enable/Disable Editing option for each feature layer is reversed from what I would expect to see. Changing the state of this option (sometimes twice) then saving the layer gets the job done, but the fact that there is an inconsistent option state is odd. It is almost like the option state is not carried while reloading the map and/or the function state refreshed on changes. At minimum, the “EDIT” function on the attribute popup and the "save layer" ability on the feature layer dropdown don’t always agree. Again this is intermittent. I did notice this on two different PC’s running IE. Did not confirm this same situation on other browsers. We are back up and running with our live public site and the work-around is a bit awkward, but I just wanted to bring this to everyone's attention in case others run into the same issue. This might just be an isolated incident. Here's our link: http://gis.townofbethlehem.org/ida/
... View more
08-05-2015
09:26 AM
|
0
|
3
|
461
|
POST
|
We currently have a shortlist story map up and running. Until recently we were able to edit/update the attributes of the point layers. New points created are able to be saved - no problems there. Making any edits to the attributes of existing points will not save the changes. Not sure if anyone else is had or experiencing this issue. Only appears to happen with story board related file(s). Sor far: Confirmed AGOL health status was OK; saved a copy of the feature collection, same result contacted ESRI Support, they screen shared and agreed something was wrong, looking into it
... View more
08-05-2015
07:12 AM
|
0
|
5
|
2876
|
Online Status |
Offline
|
Date Last Visited |
2 weeks ago
|