Latest Contributions by JoshuaBixby

Part of the reason Esri has moved away from documenting single-service recommendations like the old "n+1" limit is that any such recommendation is so generic that it isn't really applicable, or at least isn't really helpful.  Unless your ArcGIS Server site only has a single service published, which I doubt very few do, how a single service is tuned really depends on all the services on the machine.  A rule like "n+1" may be a reasonable suggestion in a vacuum, but what if you have published many heavily-used services and tuned them all the same way?  It won't be pretty for any of the services when the machine is maxing out its CPU (and likely memory as well) because many heavily used services all have "n+1" max instances. Tuning an ArcGIS Server site has so many factors to consider that it is hard for single, simple suggestion to be made.  Unless you are trying to maximize or optimize computing resources too eek every last penny out of some capital expense or monthly hosting bill, at the end of the day the most basic metric of whether a service is tuned well enough is whether you are getting complaints from users.  Start with the defaults Esri provides and see what feedback you get from users. ... View more

The answer to this need used to be ArcGIS Engine, but that product was never migrated to ArcGIS Pro runtimes, and now Esri is retiring it this March.   ... View more

@AliTalaat22 , wildcard behavior is fairly standard across programming/scripting languages and commands.  Is there specific wildcard behavior that you are finding unexpected?  If so, can you provide an example? ... View more

Unfortunately, I can't re-link to the public defect listing because Esri appears to have yanked it from being publicly available.  I have never had that happen before, where a defect is logged and made public and then Esri removes it from public view.  Here is the defect and description: BUG-000181467: When running the updateFederatedServerUrl operation after changing the server Web Adaptor name, all feature services become inaccessible and are not updated. ... View more

Not sure if the following is related, but our organization just logged the following defect a couple weeks ago: BUG-000181467 for Portal for ArcGIS ... View more

I have a hard time believing the data source itself is a factor, at least the difference between different types of geodatabases, but it is definitely worth looking into some more.  If I can find some time I will run some additional tests. Regarding one of my earlier questions, what is the full REST call?  Is f=json&token=Foo really the full URL that is causing changing ETAGs?  ... View more

Does your understanding come from documentation, experience, or somewhere else?  If documentation, please share links to specific Esri documentation to back up the information.  If experience, how much have you tested this specific situation?  A quick 5-min check on a couple of the multi-machine ArcGIS Server sites I manage, so the opposite behavior you describe as expected.  If you can share a reproducible test others can try to generate the results you expect, I would be interested.   ... View more

A quick check on a couple of the multi-machine ArcGIS Server sites that I manage show the same ETAG being generated from different machines in the same site when the same REST API calls are made to the different machines.  Without knowing more about the specific REST API calls being made (is f=json&token=Foo really the complete URL?), I can't offer any additional comments. ... View more

The way you worded your question, it makes me believe you are not using ArcGIS Web Adaptors, is that correct?   ... View more

In this case, i.e., trying to NULL a shape file field that doesn't know/support NULL, the DA update cursor will generate a RuntimeError instead of populating the field with "None": Traceback (most recent call last): File "<string>", line 4, in <module> RuntimeError: The field is not nullable. [TXT_FLD] ... View more

I am glad you got a solution.  Since you are using a mobile geodatabase, I was going to suggest a more complex definition query, and it seems you went down that route on your own.  I will note that the code as shared here does not guarantee a single record for each GpsNumber (I am assuming each GpsNumber represents a different collar/animal), i.e., there may be edge cases where multiple GPSTime records exist in the layer for a single GpsNumber. ... View more

To quote myself from an earlier response: @JoshuaBixby wrote:   It helps to: Provide your data schema (field names, data types, etc...), or at least the relevant parts Even better, provide sample data.  If sharing data itself isn't possible, create an example dataset that can be shared. Share code snippets of what has been tried so far Share expected result and what results you are currently getting. Item #3 could be replaced with an explanation of a workflow instead of code snippets.  For example, how exactly are you interacting with the data?  You state: I have a dataset with 100,000 records, each one taken about every 15 minutes. I only need one per day for most cases. I'd like to make a view to grab just one record per day. Most cases?  What exactly does that mean, and what are the cases you wouldn't need just 1 record per day?   And what are you doing with a collection of 1 record per day?  Are you interacting with it in Pro for data exploration, are you making a static/hardcopy map, are you publishing it as a GIS service to make an interactive web map, etc....? Sharing what the requirements are will help people determine if there is a completely different approach entirely than focusing on how to manage date fields and objectids in a table view. ... View more

It helps to: Provide your data schema (field names, data types, etc...), or at least the relevant parts Even better, provide sample data.  If sharing data itself isn't possible, create an example dataset that can be shared. Share code snippets of what has been tried so far Share expected result and what results you are currently getting. ... View more

@HannesZiegler , great news, thanks for sharing and for getting the functionality fixed/updated. ... View more