Latest Contributions by DanWade

For clarity ArcGIS Enterprise 10.9.1 has not been officially released yet. If we are in fact running version 10.9 I do not see a patch for this yet so, development is perhaps still working on a patch. Version 10.9.1 should be released soon. Eric provided a simpler workaround in his post. ... View more

Hello Elias, I am not certain we are working with version 10.9.1 just yet, but maybe you are. As for version 10.9 if you are using the Filter and drilling down to a definition name ($DEFINITION_NAME) which is a property filter there is an existing bug: [BUG-000141761: Filter expressions configured do not support the internal properties of event records]. It might be possible to filter on enough field names to create a distinction between definitions the workflow (filter) would still work. While also reviewing the provided screen capture, vnfFiltering, I believe you might want to take advantage of the GeoEvent Manager Choice Filter which is new at 10.9. This behavior still exist here, but I wanted to make you aware of a great new filter that is cleaner and more efficient for the workflow. What are choices? https://enterprise.arcgis.com/en/geoevent/latest/analyze/choices.htm GeoEvent 10.9: Introducing Choice Elements https://community.esri.com/t5/arcgis-geoevent-server-blog/geoevent-10-9-introducing-choice-elements/ba-p/1053353 ... View more

This array behavior for the inbound GeoJSON adapter has been submitted as the following bug: [BUG-000142930: Inbound GeoJSON adapter is not handling arrays of strings as multicardinal attribute values.] ... View more

The "brackets" you speak of are what is called an array. It sounds like the data has been modified from what it was at the start of your project. I might suggest allowing GeoEvent to create a new definition automatically. This should then show this object with an infinity icon instead of the number one. It is possible your existing output layer will require modification as well. You might then experiment with using this handy processor to break the array: Field Splitter Processors for GeoEvent Server   ... View more

Hello Vicky, Please check the GeoEvent Manager > Site > Data Stores page and see if the registered ArcGIS Enterprise site is validating. If the connection is not validating check the GeoEvent Server logs for SSL Handshake errors and if those errors include "Path building". Kind regards, Dan ... View more

Hello @Jordan, Would you by chance be able to submit a case with Esri Technical Support with the Enterprise-Ext team?  ... View more

Hello, I just wanted to add the detail related to this functionality not being supported. ArcGIS REST API > Query (Feature Service/Layer) (The last paragraph of the "Description" section) "To use pagination with aggregated queries (queries using either returnDistinctValues, or outStatistics with groupByFieldsForStatistics) on hosted feature services in ArcGIS Enterprise, the supportsPaginationOnAggregatedQueries property must be true on the layer. Hosted feature services using a spatiotemporal data store do not currently support pagination on aggregated queries." ... View more

Hello Fabio, Please submit a case with Esri Technical Support with the Enterprise Ext team to troubleshoot this behavior. Kind regards, Dan ... View more

Hello Craig, I appreciate the GeoNet post about ArcGIS for AutoCAD. I see you mention Autodesk version 2019. When working with this particular version of the Autodesk products with ArcGIS for AutoCAD there have been display issues observed. If at all possible you might try the 2018 or 2020 version of the Autodesk product and then monitor this display behavior. Kind regards, Dan ... View more

The outcome of the Support case was as follows: There was sporadic behavior with GeoEvent Server geofences. These geofences were being used together with the spatial ENTER for a Filter. While ENTER can be finicky for a spatial filter it was determined that the cause of this geofence behavior was that the third-party mobile application was sending a large amount of events with NULL values which was then leaving the last known ENTER event in an unknown state prior to entering the geofence. However, a solution was found where the first Filter being used to separate all deviceIDs was added onto with an AND filter that filtered for the devideID and an additional attribute field that had a valid value.This filter then eliminated all NULL events going to the Filter performing the spatial ENTER. ... View more

Hello Matthew,   I want to first apologize for the wait time you have experienced with your post. To answer your question I can say what you are seeing is the out-of-the-box behavior, however, there is an enhancement for this topic.   [ENH-000125501: Provide additional security controls for the GeoEvent Server REST endpoints]     Kind regards, Dan ... View more

Hello Nathan, I am glad you found the blog helpful with your workflow. I want to thank you for pointing out the bad screen capture too, which has now been updated. Kind regards, Dan ... View more