Latest Contributions by AdamMesser1

‎09-15-2021

Correct CCGT_UAV, however, I indicated that I checked those and created a test user with no privileges to verify. Thanks for pointing folks to the API reference.

‎05-18-2021

I did a bit of looking for an solution and checked out @KellyGerrow posts as she does such a great job with AGOL articles. For some reason it didn't show up on the community pages when searching, but @TonyViveiros2 asked the same question.

‎05-18-2021

Field order is being sorted alphabetically in the popup configuration when a feature service is added to the New Map Viewer. Is there a way to make the map viewer honor the original field ordering as shown in the feature table? Resorting the original order is problematic as field order is set to facilitate ease of data viewing or entry. Unfortunately, the caveat on the popup configuration mentions "Popups offered in map viewer are not compatible with all apps." This appears to be the same issue that @MarkEastwood experienced with his collector post. We are working on a configurable editing app which apparently does not honor new map viewer popup configurations. I tried using Experience Builder, assuming that the problem may be due to the underlying javascript api 3x/4x compatibility, but EB does not yet have an editing widget. It does not appear the popup reorder is honored in Field Maps either. Given this we are spending time to redo our work to use the Map Viewer Classic unless Esri has recommendations on using the new map viewer for editing wit original field order.

‎05-18-2021

Will do. Thanks @DanPatterson

User Delete - not licensed by user error · ‎05-07-2021

Our code for deleting inactive users on AGOL is failing on the user.delete() command after upgrade to Pro 2.7.0 using the python api 1.8.4. The final return is "Exception: not licensed by user (Error Code: 400)" with full return in attached file. These users do not have content or own groups or have any special licensing. To verify, a new test user with no content, etc. was created and exhibited the same issue. Upgraded to Pro 2.7.3 and api 1.8.5 did not solve the issue. Going back to the base python 3.7.9 install from the ve also did not change the error. As it seems related to entitlements, I added a license to the user to see if the error changed, it didn't. The user can be deleted manually via AGOL, and a different machine running Pro 2.3.2 and I believe api 1.6.2, can run this command without error. None of our other python api commands seem to be failing. Ideas on what I'm missing?

‎01-31-2020

How does content get ordered in a Gallery with Dynamic display on a Hub page? We have several galleries on our Hub Page that were set up as Dynamic display, before Manual display became an option. In exploring these, sorting does not appear to be determined by usage, date modified, or title. I found a question asking if sorting could be set via these parameters, but there is no indication of how sorting currently is determined. We could set this manually, but prefer the ability to control gallery content via a group, which is irrelevant with manual display.

‎09-09-2019

Thanks Derek. Hopefully the idea will get the votes to allow enabling that functionality.

‎09-05-2019

In Operations Dashboard, the Map Layer Actions enables a selection tool that is not active in the map by default. Is there any way to enable the selection tool by default? I have found a post indirectly asking this question and an idea related to this issue and was hoping Esri staff could clarify. Thanks.

‎06-05-2019

We are using a hosted feature layer that contains dates prior to 1900. I am using the ArcGIS Python API to save a queried feature set ( featureset.save() ) from this layer to a local geodatabase for analysis. All dates prior to the year 1900 are incorrect in the locally saved feature class. All other dates are saved with their correct UTC time. Using the Export Data option from the hosted feature layer using AGOL returns the correct results. Has anyone else experienced this, or know if this is a bug?

‎06-04-2019

After running through this issue with Esri support we ended up having to unregister the existing relational and tile cache data stores, upgrade from 10.5.1 to 10.6.1, and then configure the new data store. We were never able to successfully re-register the tile cache data store, but it no longer was a dependency of our system. The following were the documented support steps. RECAP Running the configuration wizard in Firefox, user showed me where the error message occurs during the prerequisite check. Attempted to run the configuredatastore.sh to see if the error message is the same. Different error message "Attempt to configure the data store failed…Extended error message. The specified GIS Server site already has a managed data stored." Navigated to Server Manager and noted that there is registered Data Store that is not validating successfully. Ran the describedatastore.sh tool and received error stating that it is not initialized. Ran netstat -aon | grep 2443 and that port was listening, but running netstat -aon | grep 9876 and that port was not listening. User showed me that the Firewall is turned off completely. Informed user that we could temporarily unregister the Data Store and reconfigure the Data Store. Unregistered the Data Store and attempted to run the configuredatastore.sh. This was successful. Successfully configured the Tile Cache Data Store, but it does not show up in the Server Manager. Trying to unregister or register from the browser gives an extended error message. User informed that he will restore to a snapshot and attempt to run this again to see if he can get the Tile Cache to store. Will update me on the progress. Noted that in the syntax, only one "-" was referenced instead of two "--" for the stores option. RECAP #2 User rolled the Data Store back to 10.5.1. Unregistered both the relational and Tile Cache Data Store and began the upgrade process. Successfully registered through the configuredatastore.sh in the terminal, but only the relational works again. The Tile Cache returns the same error message. Ran netstat -aon | grep 29080 29081 and those ports were not listening. Verified that firewall is turned off and that there is no third-party anti-virus software. Mentioned that port 5968 relates to the couchdb folder relates specifically to the Tile Cache. User mentioned that they may not need the Tile Cache as they upgraded from 10.1-10.5.1 and there may be some clutter leftover. Temporarily disabling it and starting their services appears to have no affect; everything is still working just fine.

‎06-04-2019

We are using an ArcGIS Online application to collect data. We are in Mountain Time (UTC -7) currently under daylight savings time (UTC -6). The date entered is 6/1/1903 12:00 AM; timestamp of -2101312800000 or 6/1/1903 6:00 AM UTC. Staff are using Edge and Firefox to enter and view data (image below of query result in Firefox). When viewed in Chrome (second image) the date is 5/31/1903 11:00 PM; still with a timestamp of -2101312800000 or 6/1/1903 6:00 AM UTC. The field in question was created on ArcGIS Online after the feature class was published and when combined with the UTC time is 6AM I do not believe the following post applies (Problem: ArcGIS Online pop-up windows and attribute tables display the date as a day earlier ). My assumption is AGOL in Chrome is not honoring daylight savings time and is subtracting 7 hours instead of 6. Oddly enough, the record edit dates are both returning the same datetime regardless of browser. Can someone out there with more insight into datetimes or AGOL provide any insight? The ironic thing is that we don't even care about the time, we just need date (but AGOL doesn't have just a date option) so staff are defaulting to 12AM during data entry, else we may never have noticed the inconsistency. Correction: ArcGIS Python API notes were removed from this post as it was not an error.

‎01-30-2019

Jake, Thanks much for the response. We have reviewed our system and meet all requirements. The only change from 10.5 to 10.6 are memory requirements. I assume you were asking us to verify requirements for SUSE Linux Enterprise Server 12 - Service Pack 2, and not suggesting we roll back to SLES12 SP2, as it was end of life March 31, 2018. With no subsequent security upgrades rolling back to SLES12 SP2 is not an option. The authorization wizard was run, and it is how we activated ArcGIS Server 10.6.1 with the new provisioning file. The patch notification tool was run, and while there are listed patches, I see nothing for Server or Portal that seems it would impact Data Store. If you are aware of specific patches that would impact the install please let us know what those would be. Does that address your suggestions? Adam

‎01-29-2019

Attempting to upgrade ArcGIS Enterprise from 10.5.1 to 10.6.1 on Linux SLES 12 SP3. Upgrade has been successful for Portal/Web Adaptor and Server/Web Adaptor. When upgrading Data Store we received an exception (see attached) "com.esri.arcgis.datastore.common.DatastoreException: Invalid parameter (dsSettings)" for the Prerequisite Check. We rolled back to a pre-upgrade snapshot and removed all registered data stores before upgrading as a test. Same error. Has anyone seen this error and what it might indicate?

‎01-22-2019

When I asked this question, I did not understand that user.esri_access is set up as a getter and a setter. To set you designate user.esri_access = True. The documentation provides guidance on this. It would save a step if enabling esri_access was included with user.update.

‎05-30-2018

The api documentation suggest the esri_access function of the user class is a means of enabling/disabling esri access. In v 1.4.1 this is not functioning, perhaps because user.esri_access is defined twice. The first sets an attribute of the user which returns user_type. This appears to take priority over the second which is a function to set the user_type, as noted in the documentation. In addition user.update includes user_type=None in the function but does not include that parameter in the arguments. Can you clarify the future functionality for user.esri_access? And with that, is there a reason the ability to set user_type is not included as a parameter in user.update? Thanks.

Online Status	Offline
Date Last Visited	‎10-10-2025 11:52 AM

My Ideas

Latest Contributions by AdamMesser1

Re: User Delete - not licensed by user error

Re: New Map Viewer Popup Field Ordering

New Map Viewer Popup Field Ordering

Re: User Delete - not licensed by user error

User Delete - not licensed by user error

ArcGIS Hub Dynamic Gallery Sorting

Re: Can map layer selection tool be enabled by default?

Can map layer selection tool be enabled by default?

Date error using feature set save

Re: Data Store upgrade error: Prerequisite Check

What is causing inconsistent AGOL date between browsers?

Re: Data Store upgrade error: Prerequisite Check

Data Store upgrade error: Prerequisite Check

Re: Clarify user esri_access in arcgis api for python

Clarify user esri_access in arcgis api for python

Re: Problem with "Identify deprecated Configurable...

Re: Is it possible to get a list of outside organi...

ArcGIS Pro Named User programmatic check out for s...

Re: Problems with Shared Instance Services

Re: New Map Viewer Popup Field Ordering