Latest Contributions by roemhildtg

‎02-21-2022

Update - I found the issue. Using client:requestip didn't work. No reason as to why - but after changing the client to referer and setting `referer=some-referer` I was able to use the token.

‎02-21-2022

As the name suggests, I have a ArcGIS Server federated to ArcGIS Portal. Portal auth takes over here so I can generate a token with ArcGIS Portal `/sharing/rest/generateToken`. I can then take this token and generate a server URL token - or so the docs would lead me to believe. https://developers.arcgis.com/rest/users-groups-and-items/generate-token.htm but when I get the "server token" the response from the `/query` endpoint is always invalid token. I'm using `client=requestip` and `serverUrl=https://...../server/` and `token=<the portal token i got in step 1>` Has anyone gotten this working? More details: step 1 - get a portal token: Step 2 - pass portal token to get a serverToken: Step 3: pass server token to the query endpoint

‎12-07-2021

@elpinguino- finally got access to my account again...sorry for the delay - but for you and for anyone else who has this issue - what I mean is this: Remove index: https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/remove-attribute-index.htm Add index: https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/add-attribute-index.htm you can also go into the layer properties -in pro or arc catalog and go to Indexes. From there - delete the existing index on the GUID field and re add it but be sure to check the "UNIQUE" checkbox. The rules to ensuring that the applyEditsWithGlobalIDs is true are as follows: 1. Check that all layers and tables have a global ID and unique constraint index on them 2. Check that all attachment tables related to each layer and table has global ids 3. Ensure the attachment table relationship USES the global id field/guid in the relationship - so check the Attachments_REL relationship class and make sure that it uses the Global ID field. 4. Ensure each attachment table has the global id unique index constraint 5. Ensure all relationships for layers in the service use global ids to participate in the relationship (including attachment relationships). You can usually browse the /arcgis/rest/services/ServiceName/MapServer/<LAYERID> endpoint of the service for each layer to see which one is the culprit .

‎10-15-2020

Hi Melisa. You would do it in the "Workforce Project" item.

‎10-01-2020

Yeah I just tried renaming that and it fixed it. The old Esri delete and start over fix never fails.

‎10-01-2020

I can't update - this is in a citrix environment. IT has that locked down.

‎10-01-2020

My Pro installation just started missing a lot of GP tools. Any ideas on how to resolve this? For example, searching for "Create enterprise geodatabase" doesn't have any relevant results.

‎09-03-2020

Ah interesting. Could you, in theory, use this to force users to submit at least one repeat record?

‎09-03-2020

Hi Doug - can you proved a more detailed example? I'm not 100% clear on what you mean. It sounds super useful.

‎06-11-2020

James Tedrick‌ have you seen my previous message? We were just wondering because users keep running into the issue and I'm fairly certain this is pretty simple to reproduce. Just submit a survey, then from the sent folder, choose the option to copy the data into a new survey. It seems the calculated fields do not update and are instead copied over.

‎06-11-2020

I would also add that swagger API for portal/AGO rest services would be handy as well.

‎06-11-2020

I would also add that swagger API for portal/AGO rest services would be handy as well.

‎06-05-2020

Problem: Whenever you publish a service to ArcGIS Online or ArcGIS Server, the layer gets cached and there's no easy way to update it. Cases where we may want to refresh include: 1. I published the service with an additional layer 2. I published the service with some different symbology Solution: Add an option in AGO layers to "refresh" the layer. Make it useful so that users can easily add additional layers from the service or refresh symbology, or refresh labeling.

‎06-03-2020

ArcGIS pro places a lock on a database when you open the map. It does not release the lock until you close pro. This idea is to automatically release the schema locks when the data is not in use (IE when a map is closed inside a project). Detailed workflow: We use multiple different user accounts in SDE to restrict editing schema to administrator users. When a database connection is opened to a table that doesn't have schema editing capabilities it puts a schema lock on the table. The administrator user is now unable to modify that table, cannot update alias, add/delete fields, etc. Benefits: Time savings - it costs tons of time to release locks put on by a Pro project as the only solution is to close all the open maps that may be locking the data, then save the project and shut down. You have to close the maps because otherwise it will re-lock the data when you open the project up again. Restarting pro takes upwards of a minute or 2 and multiply this by every time we need to modify a field throughout the day and the time quickly adds up - as well as the frustration of trying to add the field and getting the little error message: Related Idea: Manual Release of ArcGIS Schema Locks

‎06-03-2020

ArcGIS Pro's schema locking is far more aggressive than even ArcMap. If you even touch an SDE connection with Pro - it schema locks everything and you cannot release it until you reboot Pro. We regularly work with different user connections in SDE to restrict access to the database and this is incredibly painful. Having good security practices, like limiting user access through user connection files should not be this troublesome. What's the risk in not having schema locking? If I'm being honest - I'd almost rather not have to deal with schema locking at all. It causes so many headaches and so much lost time in: - rebooting arcgis - searching for services that may be locking - Trying to find users that may be locking I imagine the worst that could happen is a user editing a database while a user deletes a field is the worst case scenario. At which point they might receive an error about a column not existing and the edit can't be applied. This is a scenario any dba should be aware of anyways and not be making changes while users are editing databases.

Online Status	Offline
Date Last Visited	‎06-28-2022 12:44 PM

My Ideas

Latest Contributions by roemhildtg

Re: Generate a token to query features from a federated arcgis server

Generate a token to query features from a federated arcgis server

Re: Enable Apply Edits With Global Ids on ArcGIS Feature Services

Re: AGO assistant Workforce Apply more than one Survey

Re: ArcGIS Pro Missing GP Tools

Re: ArcGIS Pro Missing GP Tools

ArcGIS Pro Missing GP Tools

Re: Limit repeat count in Survey123 without the _count field in schema

Re: Limit repeat count in Survey123 without the _count field in schema

Re: Survey123 3.9 Issues - Start Date/ select_one's

Re: Support Swagger for ArcGIS Server REST endpoints

Re: Support Swagger for ArcGIS Server REST endpoints

Add method to refresh updated layers in AGO

ArcGIS Pro - automatically release locks after closing map

Re: Manual Release of ArcGIS Schema Locks

Pro Schema Locking

Re: Generate a token to query features from a fede...

Re: Enable Apply Edits With Global Ids on ArcGIS F...

Re: ArcGIS Pro Crashes when labeling

Re: Esri API 3.13 Dojo Build Errors