Latest Contributions by AmyRoust

Per Esri's documentation, Attribute Rules and Contingent Values are not supported in geodatabase replicas. I reached out to Esri Technical Support to ask what would happen if we implemented Attribute Rules on a child geodatabase participating in a two-way replica (Esri case 03438244). They tested that workflow and did not turn up any issues, but reiterated that it is not a supported workflow and recommended against implementing it without taking regular backups for disaster recovery purposes. I would like to see Esri create a supported workflow for using Attribute Rules on replica databases. While I do not need to replicate the rules between the parent and the child, I can imagine that it would be useful functionality. Here is our current workflow: - County GIS has the master NG911 geodatabase. This includes, but is not limited to, address points and road centerlines. - City GIS (my organization) has a child two-way replica database of the master NG911 geodatabase. We are responsible for maintaining geodata within our city limits, as we are the authoritative source for addressing in this area. - Each address point and road centerline has attributes related to the zones that intersect. For example, an address point must be assigned a fire response zone and a law response zone. The city uses Attribute Rules to auto-populate these fields based on their intersection with the polygon layers that track that information. We have several other rules (auto-incrementing IDs, for example), but one example of the utility of Attribute Rules should be sufficient.   ... View more

I'm in the process of upgrading all of our automated data maintenance Python scripts from 2.7 to 3.x. In our current setup, we have two cases where the parent SDE GDB has a geometric network in one more more dataset, but the child replicas do not. Syncing works fine in 2.7, but in 3.x, I get the following error message: ERROR 003131: Replicas containing geometric networks, parcel fabrics, or cadastral fabrics are not supported Has anyone else had an issue using arcpy.management.SynchronizeChanges on an existing replica when running the tool in Python 3? ... View more

I would like to see improvement in the load times for resources on network drives. My organization has excellent hardware and resources for connecting to different drives and databases on the network, but the response times are noticeably slower in ArcGIS Pro. I don't believe that it's a latency issue, but I could be wrong. As a simple example, if I have an Excel spreadsheet saved on a network drive, I can open it almost instantly from Windows Explorer. If I want to add a sheet from that same Excel document to a Pro project, I open the Catalog pane and then expand the spreadsheet. In my test case, it takes 18 seconds for the list of two sheets to appear. That test was with a very small Excel document (21 records in each sheet). ... View more

I love that we have the option to sort related records in a pop-up, but I don't always need to display the sorting field. I'd like to have an option to hide that. Example: I am displaying a list of surveyors assigned to a county. I want to sort by surveyor's last name, but I don't want to repeat the last name, nor do I want to put the first name on one line and the last name on a second line (I blurred the last names for privacy): AmyRoust_0-1688584144748.png I'd like to just hide the second line. I could switch and sort by OBJECTID, but then end users would wonder what the number meant.   ... View more

I'm stuck in Map Viewer Classic for any web map that has a related table with records that need to be displayed in the pop-up because I can't hide unnecessary fields from the related table. Here is an example of a related record in a pop-up: AmyRoust_0-1688583720855.png At minimum, I need to be able to hide OBJECTID, ContactActive, and CCC, which can be done in Classic. Ideally, I would be able to create a custom table where I could concatenate the first and last name into one field, and then concatenate the phone number and extension into one field. ... View more

When setting up a line chart with the Chart Widget in Experience Builder, you have minimal options for the "Value Point" styling. You can have no endpoints (flat end to the line) or you can have circles of varying size and color. AmyRoust_0-1687377201345.png   It would be nice to have more than one symbol for the value points (squares and triangles at minimum, with the option to rotate them to get diamonds or arrows pointing in specific directions respectively). That gives the designer more options for making their data points distinct for people who are living with vision impairments such as color blindness.   ... View more

In an effort to make a line chart more accessible to people experiencing disabilities, we changed the line pattern for each line. Unfortunately, the legend isn't wide enough to show which lines are using which patterns: AmyRoust_0-1687376986136.png   It would be nice to have the option to expand the patch width/height so that the different line patterns were easier to distinguish. Alternative: if the Legend widget could be connected to a chart, that might give us the flexibility we need. ... View more

Not surprisingly, I get a lot of requests for ArcGIS products to provide similar functionality to Tableau dashboards. One request in particular that I get is to customize the tool tips that display when you hover over a data point in a chart. Right now, there doesn't appear to be much control over what is included in the tooltip beyond the column name and a second row with "Sum of {columnname}" or "Count of {ColumnName}" depending on what summary statistic being used. I would like to be able to add custom text to the tooltips, much like what you can do with pop-ups. At the minimum, it would be nice to be able to change the data labels for the statistics. Even better, it would be great if I could write a sentence like we can already do in map pop-ups. So, instead of ColumnA: Value Sum of ColumnB: Value It could say, "In Nowhere County, 17 samples were collected." ... View more

Quick question since I can't find this clearly stated anywhere: if you use a locator, are the results always a point layer? Or if you use a polygon feature class as your data source, is it possible to have it return a polygon? ... View more