Latest Contributions by mpboyle

I'm already handling the dates if they're prior to 1900 (code below).  I'm really wondering why I'm getting an error at all when trying to insert a feature with a date prior to 1900...are these dates not supported by the Python API? def format_date(input_value): if isinstance(input_value, datetime.datetime): if input_value.year <= 1900: return None else: return input_value else: return None   ... View more

Hi @MollyWalkner_1, The URL parameters page you reference is what I eventually found. Below is an example URL using the minimal number of parameters to accomplish zooming the map to the searched feature.  The text in bold will need to be replaced with actual values.  The "widget_number" corresponds to a search widget.   https://...experience_url...#widget_number=search_status:%7B"searchText"%3A"search_string"%7D   Thanks! ... View more

Hi @ShengdiZhang , Thanks for pointing me in the right direction.  For any future users, I referenced the "Search widget parameters" section of the Esri documentation below. https://doc.arcgis.com/en/experience-builder/latest/build-apps/url-parameters.htm ... View more

Hi @Jianxia , For the URL parameters that support zooming to selected features, does this support a search widget configured with a locator service? ... or, does the search widget have to be configured to search a feature layer? If a locator service is NOT supported, are there plans to support this?  We have several of our WAB apps where users make use of the "find?" URL parameter for zooming an app to a particular feature, and our search widget for those apps use locator services. Thanks! ... View more

It seems that the Crowdstrike event on 7/19/2024 corrupted some of the Server files.  Working with Esri support, they provided a repair tool which removed and/or reset a handful of files.  After the repair tool was ran, statistics were once again being collected by the Server. ... View more

ArcGIS Server Windows service is running, and we have no issues consuming services or hitting the REST page. ... View more

@Soobin-Choi  After the June 2024 update, some of our existing dashboards are pretty much unusable.  We have dashboards that display CPU and RAM performance of our servers.  We have one feature layer that stores this information and contains around 60k rows.  Inside the dashboard, we use Arcade feature set expressions to filter the data down to specific machines, resulting in about 8,500 rows per machine.  Each row represents the server performance at 5 minute intervals, giving us about 30 days worth of information. Using feature sets also allows us to set a refresh interval on the data, which we have at 1 minute. After this update, the dashboards with serial charts take forever to draw.  Comparing the same charts using the same feature layers in our ArcGIS Enterprise deployment (11.2, which does not yet have this update) is like night and day.  The ones in Enterprise load almost right away, while it takes several minutes for the ones in AGO to draw or render the browser unresponsive. I have tried creating hosted feature layer views to filter the rows within the parent feature layer, and while this seems to make some improvement, we lose the refresh ability by consuming a direct feature layer. Below are example dashboards using the same AGO hosted feature layers as the source: ArcGIS Online ArcGIS Enterprise ... View more

@Koen  Coming back to this issue... I have created 2 dashboards that use the same AGO hosted feature layer.  One dashboard is in AGO, one is in our Portal (11.2).  Each one of these dashboards is configured the same way, using the same feature layer. When opening the dashboards, please note how slow the AGO one is to load.  It takes several minutes for the dashboard to load the charts and be able to switch between the tabs. The one in our Portal loads almost instantly and you can cycle between the tabs right away. The AGO dashboard become extremely slow after the last AGO update.   AGO Dashboard Portal Dashboard ... View more

I'm not sure what all you want to see in the network traffic.  The fetch statements don't seem to be taking terribly long.  All Status values equal 200.  Below is the network traffic with only fetch types showing. There are approximately 62,000 data points in the source hosted feature layer, but not all are used in the charts.  The charts are powered by a dynamically created feature set using Arcade and are refreshed every 1 minute. As mentioned, prior to the update the charts loaded without issue, and I actually had the dynamic feature sets refreshing every 30 seconds without a problem.  I bumped the refresh rate of the feature sets to 1 minute hoping that would help, but it doesn't seem to. I thought maybe retrieving the data is an issue, but if I test the Arcade expression, data is returned quickly, even though it's only the first 100 features.   ... View more

The dashboards that are noticeable have 6 line charts.  These all loaded in an acceptable time prior to the last AGO update.  There is now a very noticeable delay in the charts loading.  We are limited to using Edge at work, however I tested Chrome on my personal machine and the delay is still noticeable. ... View more

Thanks for pointing me in the right direction.  Esri does have the run time arguments documented. ... View more