POST
|
Thanks for your reply, @ShengdiZhang. We were able to track down the issue on our end. It looks like the map needs to reference the overall feature layer, rather than an individual layer ID, in order for the data to export as a CSV instead of a zipped folder. We didn’t encounter this behavior earlier in the year, so what changed, and why?
... View more
|
0
|
0
|
43
|
POST
|
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
Thursday
|
0
|
2
|
181
|
POST
|
I brought it up with @DavidNyenhuis1 at the Esri UC this past July. The devs are aware of the issue, and have tried multiple times to fix it, but it continues to revert back to doing this for some reason. They can't figure it out.
... View more
4 weeks ago
|
0
|
1
|
68
|
POST
|
Thank you so much, @AkshayHarshe! I really look forward to testing this out!
... View more
08-04-2025
06:07 AM
|
1
|
0
|
77
|
POST
|
@AkshayHarshe, I missed the notification for your follow-up. Thank you so much for the clarification! That really helps. I can’t remember if you mentioned this during your UC demo, but do you know when the update is planned to release? And will it be compatible with Enterprise 11.3? It was great meeting you at the conference! I’m sorry I didn’t get a chance to stop by the kiosk at the expo, but I really appreciated your session. Thanks again!
... View more
07-23-2025
09:57 AM
|
1
|
1
|
336
|
POST
|
@JonM32, agreed! That's solid advice in general. Unfortunately, I was hoping for a solution that does not involve changing the live source dataset (via a new field) or exporting to a static copy. Appreciate the suggestion, though!
... View more
06-26-2025
11:06 AM
|
1
|
0
|
222
|
POST
|
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
06-26-2025
08:47 AM
|
0
|
2
|
271
|
POST
|
Am I understanding correctly that it's not possible to use the ArcGIS Connectors on non-hosted feature layers? I keep getting the error "Webhook creation on Map Services is currently not supported in ArcGIS Connectors for Power Automate." The data I'm trying to access is a feature layer in our Enterprise account published from our organization's federated server. The URL ends in .../FeatureServer/0. If I can't use the ArcGIS Connectors in Power Automate, what other triggers can I use as a workaround? My goal is to automatically send an email whenever a feature's 'Condition' field dips below 4. The features are updated in Field Maps, but this particular field is only calculated weekly. I don't know much about Power Automate so I'm open to any suggestions. I've attached a screenshot of the feature layer's configuration, but I'd like to find a way to accomplish my goal without changing the configuration, if possible.
... View more
05-08-2025
08:02 AM
|
1
|
11
|
1008
|
POST
|
@MCAGIS, nothing stands out to me as being incorrect. Try breaking down the expression and testing the functions one at a time, if you haven't already. That might help narrow down which item is causing the error. First I'd run a test on each FeatureSetByPortalItem command, to make sure nothing screwy is going on with any of the source connections. Then I would test each "for (var x in xx_xxx)" expression block separately.
... View more
04-24-2025
08:32 AM
|
1
|
0
|
1361
|
POST
|
Thanks, but it unfortunately does not work the same as elements. 😞
... View more
04-04-2025
12:39 PM
|
0
|
0
|
328
|
POST
|
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
04-04-2025
11:39 AM
|
0
|
2
|
353
|
POST
|
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
03-13-2025
01:57 PM
|
0
|
0
|
277
|
IDEA
|
@ShengdiZhang, do you know when this template will also be available in Enterprise ExB?
... View more
03-10-2025
01:39 PM
|
0
|
0
|
318
|
POST
|
I'm working with the Add Data widget for Web AppBuilder in Enterprise 11.1 and am wondering if it's possible to reference a group from a different portal in the Allow Curated > Curated filter option of the widget? Perhaps there's a different handle (not "group:") I could use? TIA!
... View more
10-21-2024
12:22 PM
|
0
|
0
|
734
|
Title | Kudos | Posted |
---|---|---|
1 | 08-04-2025 06:07 AM | |
1 | 07-23-2025 09:57 AM | |
1 | 06-26-2025 11:06 AM | |
1 | 05-08-2025 08:02 AM | |
1 | 04-24-2025 08:32 AM |
Online Status |
Offline
|
Date Last Visited |
Friday
|