|
IDEA
|
Product Development team, please make this possible! 🙏 We are crossing out of an old custom WAB SDK app to XB on AGOL, and our users are going to miss this functionality when we do.
... View more
02-12-2025
03:36 PM
|
0
|
0
|
1971
|
|
IDEA
|
@RandyCasey - There is certainly an argument to be made for Pro to improve how it should provide the user a way to easily determine which specific map & layer a table is associated with. I suggested color coding up thread. The main issue you pointed out to the idea of using the multiple Pro projects approach was having different geodatabases. However, you can change the default geodatabase for each Pro Project to point to the same geodatabase. Not sure if having them all open at the same time would cause edit lock issues. So maybe that’s a no go. Another workaround approach is to use just one Pro project, but name each layer with some convention that tells you which map a table is associated with. MAP: Editng Editing - Hydrants Editing - Address Points MAP: Analysis Analysis - Hydrants Analysis - Address Points Something like that. This way you can always see which map a layer is associated with. Now it would be cool if there was some programmatic option available in a Pro project to automatically display table titles in such a way so we didn’t have to redundantly put the map name into the actual layer name, but it could function as a work around in the meantime.
... View more
01-11-2025
08:09 AM
|
0
|
0
|
351
|
|
IDEA
|
I kind of feel like making multiple Pro projects might be the solution listening to the workflows described in this thread. That way you can keep things organized how you want them and you know what map tables belong to because they are right there in the same Project app. Pro makes it tempting to load it with 8 maps and 32 layers and open them all, because you can. But that might not be the best approach if you need to look at all that at the same time.
... View more
01-10-2025
03:57 PM
|
0
|
0
|
1046
|
|
POST
|
Isn't that how it always works LOL. Glad it's working now.
... View more
12-06-2024
01:04 PM
|
0
|
0
|
911
|
|
POST
|
Thank you for the clarification. I understand the need for secure access and the benefits that ArcGIS Hub Premium offers. However, this requirement places a significant financial burden on many jurisdictions that have relied on this solution for years. Many of these jurisdictions have grown accustomed to the Homelessness Point-in-Time Count solution without the need for the premium features. It's disheartening to see the solution now behind a paywall, which could exclude those who cannot afford the $10k annual subscription. This change feels particularly abrupt for those of us who have loyally used and contributed to the product over the years. Would it be possible to consider a non-HUB Premium deployment option for the solution, albeit with clear warnings that some functionalities would be limited without the premium subscription? This would allow us to reengineer the solution to fit our budget constraints while continuing to address our community’s needs effectively. We hope Esri can consider the financial realities of all its customers and find a way to make this vital tool accessible for everyone.
... View more
12-06-2024
08:27 AM
|
3
|
0
|
798
|
|
POST
|
It might be related to this known bug in Pro 3.2. The issue is fixed in Pro 3.3. BUG-000164308
... View more
12-06-2024
08:08 AM
|
0
|
2
|
931
|
|
POST
|
The Homeless Point-in-Time Solution now requires HUB Premium, which essentially cuts the solution off for customers who can't afford the $10k per year HUB Premium subscription. I understand some of the neat benefits of this new offering inside HUB Premium, but those benefits mean nothing if the customer can't afford to add the HUB Premium subscription. Is it too much to ask ArcGIS to offer a non-HUB Premium solution for the Homeless Point-in-Time survey like they always have in the past?
... View more
12-04-2024
11:38 AM
|
3
|
2
|
858
|
|
IDEA
|
It would also be super useful to have this ability in QuickCapture. Any mobile app where photos can be attached should have this ability so it's the same experiences across the platform.
... View more
11-08-2024
10:30 AM
|
0
|
0
|
2233
|
|
IDEA
|
Also, the measurement tool in Experience Builder (and others) doesn't allow someone to create a circle with a radial measurement. That's a pretty common need. Also, having the ability to make multiple measurements should be part of the tool offering because users want to make comparisons, measure multiple objects and distances between multiple objects, etc.
... View more
10-30-2024
08:58 AM
|
0
|
0
|
444
|
|
IDEA
|
The Idea
Provide a "manual" override for column width in ArcGIS Pro map layer attribute tables which persists and lives with the layer. Click-and-dragging the right side of an attribute column would continue to be the primary method for manually overriding the column widths, but those overrides should be stored and optionally controlled in the "Fields" data design view, like so:
These settings would be saved with the map/table layer, so that they persist from session to session, and migrate along with the layer if it is saved out and shared.
Why?
Currently, when you open an attribute table, column widths are automatically adjusted, but often not in a way the user needs. Yes, you can double-click the right side of a column to have it auto adjust to the width of the longest value, however that width resets after a table refresh/calculation. Frustrating.
Yes, you can click-and-drag the right side of a column to adjust the width, and this will allow the width to persist after a table refresh/calculate and persists between ArcGIS Pro sessions. However, the settings do not persist in a saved out Layer (.lyrx) file or when copy/pasting the layer. The user needs to manually go through again and laboriously manually click-and-drag all the column widths. Ugh. There has to be a better way!
It's almost there!
As mentioned above, the current manual override (click-and-drag to adjust column) is very close to achieving the objective, it just lacks the transparency (in Field settings) and persistence of living inside of the layer if it leaves the map or is duplicated. Let's make column widths work just like symbology, labels, and other layer settings and bake them into the layer to live forever no matter where it goes.
... View more
09-24-2024
12:05 PM
|
4
|
0
|
460
|
|
POST
|
Glad it helped 🙂 Seems like this behavior is still the case, too. I really hope we get a way we can bake column behavior into the layers in the future.
... View more
09-24-2024
07:40 AM
|
1
|
0
|
2210
|
|
POST
|
Looks like the West Coast has been fixed, which is all I cared about. North East Coast is still missing, but that's no worries for me, so I'll consider it fixed.
... View more
08-26-2024
02:47 PM
|
0
|
0
|
840
|
|
POST
|
I'm trying to look at this USA SSURGO - Soil Hyrdric Class for California but the data on both the West Coast and North East appears to be missing from the tiled cache for all but the smallest scales. Can someone over at Living Atlas kick the tires on this service so it will start serving up imagery for the entire area it's supposed to cover? Thanks!
... View more
08-23-2024
12:49 PM
|
1
|
2
|
894
|
|
POST
|
Hi @RDCOGIS, Apologies for lack of clarity on this. It turned out that our County's security policy (not in my control) does a bot challenge for traffic originating outside of the US, and for some reason this causes Hub to basically break for the end users outside of the US. I wasn't sure if that's what was happening, but both my IT staff said it should be happening a and a user upthread from here confirmed that was their experience with a screenshot. So, there is no solution to fix it, but at least we know why so if others experience it and can change it, that would be the solution; to remove the bot challenge.
... View more
08-13-2024
03:09 PM
|
0
|
0
|
436
|
|
POST
|
I wanted to use AGO Assist but we could not login as that user as the IWA user account no longer existed. We needed to use the methods outlined here to delete the hidden ("disconnected") contents, which turned out to be a bunch of replication packages from distributed collaborations. With those deleted, we could then delete the user, finally.
... View more
07-24-2024
04:22 PM
|
0
|
0
|
2318
|
| Title | Kudos | Posted |
|---|---|---|
| 3 | 09-15-2025 01:02 PM | |
| 3 | 12-06-2024 08:27 AM | |
| 1 | 03-07-2024 09:45 AM | |
| 3 | 12-04-2024 11:38 AM | |
| 4 | 09-24-2024 12:05 PM |
| Online Status |
Online
|
| Date Last Visited |
5 hours ago
|