Latest Contributions by DamonPettitt

So i tried the alias route (and appreciate the spice puns), but then something else didn't work later in the code.  So I ultimately opted to simply import the datetime stuff after arcpy. And pardon the ignorance, so does this mean that arcpy has a class somewhere called datetime?  I understand that arcpy is clobbering the namespace, but I'm unclear as to why.  And wouldn't importing datetime after arcpy mean that datetime is potentially clobbering something for arcpy? ... View more

So slight wrinkle.  It doesn't have the issue when you're using the interactive python window in Pro, but it DOES have the issue when using in a standalone script.  I'm using the propy.bat to run the script from a windows scheduled task. ... View more

I just experienced this issue on ArcGIS Pro 2.5.2 (i.e. Python v 3).  I only discovered it after getting the "now()" error and then manually moving my "from datetime import datetime" statement until i figure out it was the arcpy import that was clobbering it.  So maybe not fixed, unless i'm doing something wrong? ... View more

Not sure.  All my scripts use some non-default packages (e.g. pyodbc), so I just have to clone the environment (yes, on the server that's running the script).  I would suspect you needn't clone the environment if you aren't using non-standard modules, but I guess there's one way to find out! ;>) ... View more

I stumbled across this thread recently as i was having a similar problem trying to apply some logic to the "relevant" field of a "begin group" type where i had some required fields within the group. For me, i didn't need the fields to be required on my form, they were just set up to be required in the original feature service. Anyway, in case this helps someone else, the way i achieved only having the "relevant" logic on the "begin group" was to put dummy fields inside the group (putting in "null" in the "bind::esri:fieldType" column for these fields since they weren't in my feature service) and then have my original, required fields outside this group with values in their respective "calculation" columns that referred back to the dummy fields. So for example, inside the group you might have a field called HomeOwnerName_Initial. Then, outside the group, you would have a field called HomeOwnerName where in the "calculation" column it could say something like this: if(string-length(${HomeOwnerName_Initial})>0,${HomeOwnerName_Initial}, 'N/A'). Again, for me, i was just trying to deal with a situation where my original feature service fields required, but they didn't necessarily need to be required in the form itself. ... View more

The scenario i've described is one where we're using the concurrent licensing.  You just have to make sure you do step #3 in my above message (i.e. authorize ArcGIS Pro to work offline). For Windows Scheduled Task, we use this for the Program/Script value:  "C:\Program Files\ArcGIS\Pro\bin\Python\Scripts\propy.bat" and then the path to the script (UNC if on a server). If this still doesn't get you going, let me know. ... View more

In case someone else stumbles across this thread, we are running our ArcGIS Pro, Python 3.x scripts on a Windows Server 2008 R2 machine (same machine that runs our ArcGIS Desktop/Python 2.x scripts) and it appears that you need to do a few things to be successful with running ArcGIS Pro/Python 3.x scripts: 1) Install latest version of ArcGIS Pro on the server where you're running the scripts.  We're currently running ArcGIS Pro 2.3.3 at the time of this writing. 2) "Allow License Borrowing" on your ArcGIS License Server Administrator 3) On the server where you're running the scripts, log in as the user who will run the scripts, open up ArcGIS Pro, logged in as the user who will be calling this scheduled task, and go to backstage>>Licensing...and check the "Authorize ArcGIS Pro to work offline" option.  Otherwise, you have to have ArcGIS Pro set to sign in as a user automatically that is the same name as a named user in ArcGIS Online (we don't have Portal). One thing to note, that makes your scripts not work (and could make you think something else is going on), is if your ArcGIS Pro Python Package Manager is pointing to the default environment and/or your Python environment doesn't have particular libraries installed that you may be referencing in your script.  So make sure you've got all those libraries installed on whatever environment you've chose in ArcGIS Pro! ... View more

I thought this was only an issue in ArcGIS Online, which still seems to have the issue... ... View more

I just stumbled across this limitation as well.  I would love to hear if anybody has found a workaround or if ESRI knows when the problem will be fixed. ... View more

I just checked the status of the bug # previously referenced and the status is "In Product Plan", so i guess that means it hasn't been addressed yet. :<( ... View more

Maybe in the title bar of ArcMap it can say what version of MXD the MXD is currently at.  And maybe include which license level you're using too (like it used to show :<( ). ... View more

Maybe look into the arcpy.Statistics_analysis tool and use MIN for the earliest time and MAX for the latest time? ... View more

I ran into a similar problem and I ended up creating a Python AddIn (works in ArcGIS 10.x) which basically allows a user to go forward/backward through the features of a feature class (or a selection set on that feature class) by clicking on forward/backward buttons in a Python AddIn toolbar. One of the complications is setting up the AddIn environment in the first place, but I'm attaching the code for the actual AddIn if that's helpful for anyone.  If anyone needs help setting this up, I'd be happy to help. ... View more