|
DOC
|
@AndreaB @& @monmonberry that's great news about the rss feed... maybe it's because I haven't had my coffee yet, but I'm looking on https://trust.arcgis.com/en/, and can't find the RSS feed, can you share the xml link to add to outlook? Thanks!!
... View more
03-31-2025
06:40 AM
|
0
|
0
|
7248
|
|
POST
|
We haven't yet. The best thing we've come up with is nearest neighbor with the address point... but the address point layer isn't in the same database that we're editing in, so we either have to copy the address layer in weekly, in advance - OR - geoprocess against the layer in Pro weekly after edits are made... We are still so frustrated with the lack of replacement features..
... View more
03-14-2025
09:59 AM
|
1
|
0
|
959
|
|
IDEA
|
@AlfredBaldenweck Thank you for confirming it doesn't work for any kind of relationship. It worked for all kinds in Desktop. Is there a good reason for this not to work anymore? Otherwise, how do we get this reported as a bug?
... View more
08-26-2024
06:25 AM
|
0
|
0
|
1119
|
|
IDEA
|
@AlfredBaldenweck Well that is crazy talk, but yes, that is the problem I am having. I haven't checked to see if it is a problem in a one-to-one relationship, but it wasn't an issue in ArcGIS Desktop.
... View more
08-22-2024
12:48 PM
|
0
|
0
|
1222
|
|
IDEA
|
No Relationship Class. Relates in a map in Pro - between a geodatabase layer's table and a table that came from Excel, that I've imported into the project's geodatabase. Steps to recreate are above.
... View more
08-22-2024
12:22 PM
|
0
|
0
|
1228
|
|
IDEA
|
In Desktop, when you set up a Relate between tables, it worked in both directions. In Pro, when you set up a relationship, it only works in one direction. It is not a huge deal, but an annoyance to have to create a relate from table A to table B, and then have to recreate a relationship from table B to table A. When I receive a table from someone to use in a join, I like to confirm the cardinality, if there are duplicate values, and if all records will have a match by using relates: 1. Create a relate between the tables. 2. Select all the records in the table I am exploring, note the count of records. 3. Hit related records, to have the related table pop up with related records selected. Note the count of records. 4. Hit show related records in the original table to see if the count is less than the first time. ***Nothing further was needed to do this step in Desktop. Now in Pro, you need to create the relationship back to the original table*** in one and see related records in the other table and visa versa... I hope there's a good reason that I'm overlooking for this "feature change" aka reduction in functionality??
... View more
08-22-2024
09:04 AM
|
4
|
7
|
1290
|
|
DOC
|
Can I please receive notifications in email, so I do not have to use my personal device to access work related notifications?
... View more
07-20-2024
02:21 PM
|
0
|
0
|
10585
|
|
DOC
|
I completely agree. I've hidden the app notifications because they were constant. I will turn them back on when I have a new case. I will add that it is ridiculous that the only place to get these notifications is on a mobile device; I don't have a work-provided cel phone, so I've got this work application loaded onto my personal phone sending me irrelevant notifications constantly. I love geography, but don't need to think about my work all the time, thanks!
... View more
07-18-2024
06:15 AM
|
0
|
0
|
10640
|
|
POST
|
In Desktop, when you set up a Relate between tables, it worked in both directions. In Pro, when you set up a relationship, it only works in one direction. It is not a huge deal, but an annoyance to have to start from one table and set it up, and then recreate the relationship on the related table, when you might want to select records in one and see related records in the other table and visa versa... Can someone please tell me if there was a good reason why this changed between Desktop and Pro?
... View more
05-07-2024
09:36 AM
|
2
|
1
|
624
|
|
POST
|
Has anyone been able to figure out how to set this up referencing boundary layers in another database? Attribute Assistant could do it in the map, but since Attribute Rules are in the database, it can only look at other layers in the same database. I'm not adding the parcels, neighborhoods, zip codes, addresses, municipalities, and county boundary to each database where we edit to make something work in Pro that worked in ArcGIS Desktop...
... View more
04-15-2024
01:50 PM
|
1
|
0
|
1027
|
|
POST
|
Thank you for posting this question and solution. We have done a ton of testing and finally took down production data to make schema changes this afternoon - I thought I was going to have to disable this rule since it threw this error when I tried to add a point as an editor and not the layer owner... but adding the layer owner login name did the trick! Now if Attribute Rules could allow calculations from geocoders, or from layers in another database, I'd be in business replacing Attribute Assistant..
... View more
04-15-2024
01:46 PM
|
0
|
0
|
1355
|
|
POST
|
We have been able to use the $map to do the following in AGOL, but our need is for auto-filling certain attributes in Pro as well as in AGOL. Can you use that FeaturesetByPortalItem() variable to connect to other FCs in other databases on your Portal for use in Intersect and Nearest Neighbor Attribute rules for use in Pro?
... View more
03-29-2024
05:51 AM
|
0
|
0
|
3029
|
|
DOC
|
We are having a few challenges trying to migrate to Attribute Rules from Attribute Assistant - our challenges currently are: 1. When a point is created, we would like to get the Name from an intersecting polygon (neighborhood, park name, zip code, city, etc) from a FC that is in the map from another database on the same ArcGIS Server instance. The fact that Attribute Rules can only work between data in the same database is not working for us - we are having to make duplicate copies of those layers into our database, and in some cases a View to another database - if our DBA will let us get readonly permissions to the other database for one of our logins. 2. Not being able to use a geocoder to fill in an address is also a hang up... we are going to have to copy our constantly updated address layer in, and use nearest neighbor... it's making more work. Finally, and not related - we also tried to make an incremental id and have been given a work around to make a db sequence, but we first hit the wall of Pro being updated frequently - which gives us access to new Arcade versions, but when we tried to publish the layer with that Attribute Rule attached onto our Portal that is only updated every couple of years... the rule was incompatible as it was too new.. Until there are replacements for all these items we had in Attribute Assistant, we are getting to do a lot more manual tasks... not making me feel warm and fully about having to replace ArcGIS Desktop with ArcGIS Pro, which is no longer under maintenance for security patches, so we are being urged to uninstall it 😞
... View more
03-13-2024
12:43 PM
|
0
|
0
|
4853
|
|
POST
|
With ArcGIS desktop going away, we are trying to migrate our Attribute Assistant items to Attribute Rules and can't find how to replace this geocoding rule. Help!! We are running out of time and don't see this feature being replaced?!
... View more
03-12-2024
12:58 PM
|
0
|
0
|
1989
|
|
DOC
|
Users are not local administrators on their pcs in my organization. We need to request IT to install updates, so we need a way for the IT department to be notified when there is an update to install, or so that I can forward the update message again. Functionality via an App might be a nice extra convenience, but should never replace email/website notifications. Please bring the SUBSCRIBE option back to the website. Thanks!
... View more
02-06-2024
09:20 AM
|
0
|
0
|
12230
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-14-2025 09:59 AM | |
| 4 | 08-22-2024 09:04 AM | |
| 2 | 05-07-2024 09:36 AM | |
| 1 | 04-15-2024 01:50 PM | |
| 1 | 06-29-2021 12:23 PM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|