IDEA
|
@SStopyak_BruceHarris, yes, exactly. Even the good old standalone dbf is still supported in Pro.
... View more
10-30-2023
10:31 AM
|
0
|
0
|
1180
|
POST
|
Looks like this issue was logged as a bug in April and already updated to "fixed" with the recent June release. The "fixed bug" appears to still be present when published in Survey123 web however. The workaround is to publish via Survey123 Connect. BUG-000157777 for ArcGIS Survey123 (esri.com)
... View more
07-04-2023
05:52 AM
|
1
|
0
|
1677
|
POST
|
Having the same issue. Curious if you've ever figured this one out?
... View more
04-06-2023
08:45 AM
|
0
|
0
|
373
|
IDEA
|
Sorry, should have specified wanting this in Web designer. The current Calculation of an address field almost achieves this. I just would have liked to see an "address only" option added which we'd want in all our surveys. Was not aware of the pulldata() function though. At least it's an option - thanks.
... View more
07-13-2022
09:06 AM
|
0
|
0
|
668
|
IDEA
|
While collecting data in QuickCapture, it would be great if additional data could be collected from one or many closest or underlying feature layers. For example, when performing a road patrol for deficiencies and a "pothole point" is collected, it would be great if it could "grab" the street name from the road network feature it's closest to and appended that to the collected point (or closest address, or the zone in which it falls, or ... etc.). I realise this could easily be done post-processing but would be great if it could be done during actual data collection. I also realise doing so in real time may consume credits for geoprocessing but given that an AGOL identity is required to use QuickCapture, this should be manageable. To me, this is basic and should be available out of the box.
... View more
06-14-2022
06:33 AM
|
3
|
4
|
661
|
IDEA
|
When performing a Calculation on an Address question, the ability to extract just the address number, street, and street suffix would be great. That means that the result would ommit the city, province, postal code, and country. This would be useful when labelling the address on a map where the City, postal code, province, and country aren't necessary... Thanks, Denis
... View more
05-10-2022
12:52 PM
|
0
|
2
|
854
|
POST
|
Got it to go multi-line by viewing and adding <br> into the HTML via the Custom Attribute Display dialog.
... View more
11-19-2021
10:33 AM
|
0
|
0
|
356
|
POST
|
Seeing the same on my end. (Enterprise 10.8.1) Was this ever resolved?
... View more
11-19-2021
09:00 AM
|
0
|
1
|
358
|
IDEA
|
Yup. Based on the 'Interactive Legend' Instant App's description, I'm thinking this may even be a bug... or at least not intented behaviour (since it still appears even with the Help panel disabled). If it's going to be forced upon users, the ability to at least change the wording would be nice. https://arcg.is/8CfLL
... View more
11-16-2021
08:06 AM
|
0
|
0
|
1106
|
POST
|
After contacting Support for help in resolving this, it has ultimatly been logged as BUG-000130693.
... View more
05-08-2020
10:51 AM
|
0
|
0
|
896
|
IDEA
|
...and also, layer IDs occasionally/randomly don't honor the layer ID that I assign to them in Pro. For example, if I know that AGOL layer being overwritten has "20" as layer ID, I force the ID of the source layer in Pro to have an ID of 20...but after the Sharing->Overwrite web layer is completed, the ID of the newly overwritten layer on Pro's end changes to some other random ID resulting in broken Web Map(s). The workaround that I found is to open a new blank Pro project, bring in that single source layer, and publish from there. Perhaps this is more of a bug, but not exactly user-friendly nonetheless.
... View more
05-29-2019
01:14 PM
|
0
|
0
|
2470
|
IDEA
|
...and also, layer IDs occasionally/randomly don't honor the layer ID that I assign to them in Pro. For example, if I know that AGOL layer being overwritten has "20" as layer ID, I force the ID of the source layer in Pro to have an ID of 20...but after the Sharing->Overwrite web layer is completed, the ID of the newly overwritten layer on Pro's end changes to some other random ID resulting in broken Web Map(s). The workaround that I found is to open a new blank Pro project, bring in that single source layer, and publish from there. Perhaps this is more of a bug, but not exactly user-friendly nonetheless.
... View more
05-29-2019
01:14 PM
|
0
|
0
|
484
|
IDEA
|
Yes, especially given how concealed and unknown the Layer ID option is and the resulting havoc it can cause in existing published webmaps. For someone who only uses Pro to publish and update feature layers (via Overwrite) and only authors maps in AGOL, having to first check the layer's numeric ID in Pro, then check the layer's REST properties in its details in AGOL to make sure the IDs match is not at all user-friendly. Trying to fix the broken WebMaps by jumping into AGO Assistant to edit its JSON isn't exactly ideal or user-friendly either. I guess that, at the end of the day, I'm probably not using the "Overwrite Web Layers" as it was intended to be used. There needs to be a better way of updating an existing published feature layers from Pro that will not break Webmaps if the IDs happen to not match. Enhancement ENH-000108149 is on the right track. Maybe rejigging the entire "Overwrite Web Layer" functionality in Pro to "Updated Existing Web Layer" is the way to go.
... View more
05-01-2019
06:44 AM
|
1
|
0
|
2470
|
IDEA
|
Yes, especially given how concealed and unknown the Layer ID option is and the resulting havoc it can cause in existing published webmaps. For someone who only uses Pro to publish and update feature layers (via Overwrite) and only authors maps in AGOL, having to first check the layer's numeric ID in Pro, then check the layer's REST properties in its details in AGOL to make sure the IDs match is not at all user-friendly. Trying to fix the broken WebMaps by jumping into AGO Assistant to edit its JSON isn't exactly ideal or user-friendly either. I guess that, at the end of the day, I'm probably not using the "Overwrite Web Layers" as it was intended to be used. There needs to be a better way of updating an existing published feature layers from Pro that will not break Webmaps if the IDs happen to not match. Enhancement ENH-000108149 is on the right track. Maybe rejigging the entire "Overwrite Web Layer" functionality in Pro to "Updated Existing Web Layer" is the way to go.
... View more
05-01-2019
06:44 AM
|
1
|
0
|
484
|
Title | Kudos | Posted |
---|---|---|
1 | 07-04-2023 05:52 AM | |
3 | 06-14-2022 06:33 AM | |
1 | 05-01-2019 06:44 AM | |
1 | 05-01-2019 06:44 AM | |
5 | 04-29-2019 12:13 PM |
Online Status |
Offline
|
Date Last Visited |
01-26-2024
09:04 PM
|