Latest Contributions by JoshuaBixby

Often times when running a script with a service account, the licensing information for ArcGIS Pro is not configured correctly.  Whereas ArcGIS Desktop/ArcMap was licensed at the machine level, ArcGIS Pro is licensed at the user level.  ... View more

Mark, the link you provided was to the tool's page, which doesn't have the historical information.  I did find the toolbox history page, which does address the issue.  Although toolboxes also have a licensing overview page, the licensing information is still documented with the tool as well, so why is Esri handling licensing information and version history information differently?  Why not add history information to the tool as well licensing licensing information? ... View more

Start by going through this site: Esri Careers | Job Opportunities .  There is no one job at Esri, there is a wide range of positions and that wide range has a wide range of degrees and backgrounds that are important.  The bigger question is what do you want to do for a job, specifically.  ... View more

@PhilipWeeks, @LanceKirby2 , @HaseebAnwar , @tigerwoulds , have any of you opened an Esri Support case?  If so, what came of it?  Also, providing more details about your environment is helpful, like version to start. ... View more

Kory, thanks for the update.  Limiting offline time for licenses is definitely a positive step, but lack of "license borrowing" equivalent functionality will definitely keep us using Concurrent Use licensing for the foreseeable future. ... View more

Short answer, not documented, at least that I have ever seen publicly.  However, simple to determine, just run the version.sh or version.bat file in AGSSERVER/framework/runtime/tomcat/bin folder. ... View more

Kory, I agree with Stephen on thanking you for taking the time to put the video together.  I constantly try to tell users in my organization to submit their Ideas, that it can make a difference.  This video will help me promote that argument internally. ... View more

Can you share a stripped down sample of data that exhibits the behavior?  ... View more

SQL date functions tend to vary across data source, so there will be no single SQL that will be widely portable.  See SQL reference for query expressions used in ArcGIS—ArcGIS Pro | Documentation for more information and examples.  A purely Python cursor-based will be much more portable.  ... View more

The error message states some of the form fields are invalid, maybe some requirements changed sometime between 10.9.1 and 11.3 in terms of field values.  I suggest you start troubleshooting by revisiting the form fields and their values. ... View more

The Support analyst that logged this defect didn't realize Esri made intentional corrections to file geodatabase SQL support with Pro 3.3 to be consistent with the SQL standards, including changing how NULL is handled in certain situations.  I saw the documentation for the changes during Holistic testing, but I can't seem to find the public documentation about these changes.  I did find the originally logged defect around mishandling of NULL with file geodatabases that prompted Esri to make the updates, and it shows they made the change at Pro 3.3:  BUG-000168378 for ArcGIS Pro Regardless, I expect this defect gets closed as expected behavior.   ... View more

Ah Luke, don't fall for the Esri excuses!  ArcGIS Pro doesn't support personal geodatabases because Esri doesn't want it to, that is it.  The references to Microsoft retiring the Jet Database Engine and that the Jet Database Engine never had a 64-bit library are true, but that is only half the story, the half where Esri can blame another organization for their business decision to not support personal geodatabases in ArcGIS Pro. Shortly after the Microsoft SQL Server team announced retirement of the Jet Database Engine, the Microsoft Office team announced they would continue to support MS Access through a new Access Connectivity Engine (ACE).  All signs point to ACE being a forked version of Jet that the MS Office team continued development on themselves.  Additionally, and most importantly, the MS Office team already stated in 2005: From A discussion of what's new in Access 12 : Access 12's new data engine: This means Access 12 no longer uses the system Jet engine, but is tightly bound to its own version.  The new version is fully backwards compatible with the old, so it will read & write files from earlier versions without any problems.  So in 2005, ten years before ArcGIS Pro 1.0 was released, Microsoft had already stated they would have a 64-bit, backward compatible database engine that would work with Jet-based MDB files. The real kicker is that ArcGIS Pro accesses Excel files using the Microsoft Access Database Engine drivers. From Install the drivers to work with Microsoft Excel files—ArcGIS Pro | Documentation Microsoft Access Database Engine technology helps bridge communication and external data transfers between files that are proprietary to the Microsoft Office system and other non-Microsoft Office applications such as ArcGIS Pro. So the MS Access Database Engine drivers are necessary for ArcGIS Pro to open Excel files, the same drivers natively open old (*.mdb) and new (*.accdb) Access files, and yet somehow opening personal geodatabases in ArcGIS Pro is a bridge too far for Esri to cross.  <insert head shake> ... View more

What you are experiencing is expected behavior, not just for ArcGIS Pro but for SQL in general.  NULL is neither TRUE or FALSE, it is UNKNOWN.  In your case, the results do not return NULL records because the database engine evaluating the query has no idea whether the NULL record is one of the values you want to exclude.  Only results that are guaranteed to be TRUE are returned by the query. It is always best to handle NULL records explicitly, like you are already doing with the "IS NULL" logic. ... View more