Bug-ID-Nummer |
BUG-000164278 |
Eingereicht | January 11, 2024 |
Zuletzt geändert | September 9, 2024 |
Gilt für | ArcGIS Online |
Gefunden in Version | Oct 2023 |
Betriebssystem | N/A |
Betriebssystemversion | N/A |
Status | As Designed
Nach Überprüfung durch das Entwicklungsteam wurde festgestellt, dass dieses Verhalten wie geplant ist. Weitere Informationen finden Sie im Abschnitt "Zusätzliche Informationen".
|
Zusätzliche Informationen
When listening to trigger on a feature layer, the trigger must always be followed by the 'Fetch updates, changes,...' action in the flow. Within this 'Fetch update...' action, re-confirm the the sub-layer in the feature service that is of interest which was already selected when configuring the trigger. Though the flow is triggered when a feature is created in any of the sub-layers, it does not run beyond the 'Fetch updates, changes,....' if it's not the interested layer.
Workaround
Split the two sublayers into two separate feature layers. Republishing the point and polygon layers as separate hosted feature layers does not return this error.
Schritte zur Reproduzierung