POST
|
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
09-18-2020
12:33 PM
|
0
|
0
|
466
|
POST
|
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
09-17-2020
07:10 PM
|
0
|
4
|
1260
|
POST
|
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
09-17-2020
06:55 PM
|
0
|
6
|
1260
|
POST
|
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
03-08-2020
10:03 AM
|
1
|
0
|
1960
|
POST
|
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
01-22-2020
05:46 AM
|
0
|
0
|
2069
|
POST
|
We have an existing Survey123 form that we've been using to have citizens report limited broadband areas. There now is a desire to collect the results of a citizen-performed speed test and have those results automatically put into one or more Survey123 fields. Up to this point, we've told them to manually enter the results into some Survey123 form fields, but we were hoping to avoid that manual data entry. I could see how you could have the citizen initially go to the speed test (here's the one we're using), run the test, and then create a URL parameter string that launches a Survey123 form with certain fields pre-populated (assuming we can figure out how to capture that info in the speed test app...). But I was wondering if we could instead have the speed test itself be embedded inside the Survey123 form, and as the citizen is filling out the Survey123 form, they could then run the speed test and have the results fill in either visible or hidden fields within the Survey123 form, i.e. the speed test is just like another question. I wasn't sure if this was even possible (or practical), so I'm curious if anyone has any thoughts.
... View more
12-05-2019
07:16 AM
|
0
|
1
|
624
|
POST
|
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
07-16-2019
10:33 AM
|
0
|
2
|
1960
|
POST
|
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
06-10-2019
02:46 PM
|
2
|
4
|
1960
|
POST
|
I thought this was only an issue in ArcGIS Online, which still seems to have the issue...
... View more
02-06-2019
12:15 PM
|
2
|
1
|
3829
|
POST
|
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
11-08-2018
08:14 PM
|
2
|
0
|
3829
|
POST
|
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
11-18-2016
03:51 PM
|
0
|
1
|
987
|
IDEA
|
So currently you can remove the thousands separator for number fields in ArcGIS Online by configuring the Pop-up for that field. But when you edit a feature in ArcGIS Online that has this same field, the thousands separator appears and it can be confusing for the editors. I would like a way to hide the thousands separator in this Edit dialogue as well. It would also be nice if the number formatting that you can establish in ArcGIS Desktop, at the time of the service publishing, would carry forward into ArcGIS Online. In other words, if you aren't showing the thousands separator in ArcMap for that field, can that carry through all the way to ArcGIS Online?
... View more
11-01-2016
06:51 AM
|
27
|
12
|
3568
|