Latest Contributions by KathrynWesson

We’re running into an odd issue with the “Export to CSV” option in Experience Builder. When exporting from the Legend widget, instead of a CSV, we get a strangely-named alphanumeric zipped folder that's completely empty. Other export formats are working fine, and the issue only happens to one of our layers (a referenced feature layer service), which suggests something might be problematic with the service. However, when I pull the same web map into Web AppBuilder and use “Export all to CSV” on that layer, it works with no problems. We’ve double-checked all settings to confirm that exporting is allowed. From the attribute table in Experience Builder, “Export to CSV” produces the same empty zipped folder unless I first make a selection. In that case, exporting the selection works and gives me a valid CSV. Has anyone else run into this behavior? ... View more

A coworker is running into issues when creating new polygons in a feature class that's symbolized using unique values from two fields in a joined table. She accesses the data as a layer file through a traditional versioned connection and uses feature templates generated from that layer file to create the new features. As I understand it, the template should automatically attribute the record and consequently apply the correct symbology based on the joined fields. However, after creating a new polygon, the feature appears with the default symbol instead of the correct symbology, even after reconciling and posting. The attribute values are correct in the table, but the symbology doesn’t update unless she removes the layer file from the map, re-adds it, re-applies the table join, then rebuilds the feature templates. It's such a lengthy process to do every time she creates a new feature. This issue was rare in earlier versions of ArcGIS Pro, but since our upgrade to version 3.3, it’s become a daily problem. It seems like the symbology engine no longer recognizes joined attributes immediately after feature creation, and needs a full refresh to align the rendering. In short: - The layer is symbolized using joined fields. - The data is traditionally versioned in an enterprise geodatabase. - Templates are configured to auto-symbolize new features. - Joined fields drive symbology directly. - After saving edits and reconciling/posting, symbology still defaults to the generic symbol, despite correct attributes. Has anyone else seen this behavior in 3.3? Is it a known issue or bug? Would love to hear if others have found a workaround or logged it with Esri Support. ... View more

Is there a way to "nudge" annotations in ArcGIS Pro like you used to be able to do in ArcMap? I haven't found much information about it besides this thread, which did not help me. ... View more

I published a service with multiple layers from the same data source (but filtered differently), plus a couple of other layers from another source that have the other layers' source table joined to them. When I set up the filter action through the date selector and point the target field to the joined table's date field, it ends up filtering out all of the layers from the map element. The only compromise I have found to get the date selector to stop clearing all the features from the map element when triggered, is by pulling the map image layer item IDs into Map Viewer one at a time. However, this gets rid of the symbology I defined in ArcGIS Pro, which is not ideal. I'm including a recording of what happens when I apply the same date range in both test dashboards. *First dashboard has the map image layer added as-is, and the second dashboard has each map image layer item ID added separately. Everything else is set up exactly the same between the two test environments. Is this a bug or am I doing something wrong? ... View more