Latest Contributions by se2539

Glad I found this thread. Our organization seems to have encountered the same issue as the OP and others have posted; we've discovered that the Join Field tool in arcpy corrupts the input feature class. Just as some background, we had a script on a server that would run nightly via task scheduler. It would take a polygon feature class and join it to records from a standalone table to populate a feature class on our SDE and a map service (note we are running 10.4.1 and have SQL as RDBMS). The script had been in place for at least a couple of years running smoothly, however, sometime in early November of this year it was failing during the join step. After reviewing the error log we set up, a colleague and I attempted to troubleshoot. We spent a good amount of time trying to figure out why it was failing but were coming up dry. It was driving us crazy because nothing had changed on the code end; it just stopped working. After looking at the intermediate output data (we had a scratch GDB set up to see what was going on), we encountered an error on the staging join feature class. We couldn't open it up in ArcMap/Pro, view properties, nor could arcpy delete it ... it became corrupt. Personally, I had a suspicion that it may have been due to security updates that were installed on the server where the script resides. But I honestly don't really have a way to prove that besides timestamps when this script started failing and when updates were installed. We needed to find a workaround. Basically we modified the code to use Add Join and the in_memory workspace in place of Join Field. While it did indeed at some lines of code to our script, overall, it's been good in the sense that we went from a task that took an hour and 15 minutes to run, to a task that only takes roughly 10 minutes to complete. So at least something positive came out of the issues we were having. Overall, it was just highly annoying when you expect a tool to work, and it does for an extended period of time, but fails suddenly without any rhyme or reason. ... View more

Mark Johnson wrote: I'm a little confused on the SetLogHistory option, I like to be able to refer back to my history in Desktop/Pro, I just don't want it attached to my data. I agree, I am also confused about the SetLogHistory option; is there just a way to turn it off completely against an enterprise GDB? I've cleared Geoprocessing history using the GUI tools referenced in this link ... it was successful in assisting with some performance issues we were experiencing.  But turning it off completely; how is that performed exactly? ... View more

You provided some pretty simple, yet extremely valuable information.  I was wondering why my buildings were extruding artificially high, all the while not realizing CE defaults to meters.  Obviously I needed to convert my data to feet, but I must have missed that in the tutorials I was following ... in any event, I am appreciative of your post.   ... View more

Thank you for the reply Andrew. I'll most likely log a support ticket, however, you response makes me feel a bit more comfortable with the upgrade.  We'll probably just upgrade to 10.6 for the moment and then per your advice, come up with and follow an update cycle on a regular basis.   ... View more

Hey Andrew, Your response was helpful, but still a bit leery on some things.  I understand that running ArcGIS License Manager at a lower level than the Desktop installations could be problematic; I'm actually surprised our client machines at 10.5 run hitting the 10.4.1 License Manager.  Perhaps we found a glitch? In any even, you are basically recommending that we upgrade to the latest version of ArcGIS License Manager, which at the moment is version 2019.1?  And then keeping up to date with the most current release?   One of the items that makes me a bit hesitant to jump on this upgrade is the authorization number differences for versions greater than 10.5 ... honestly, the process confuses me and I'm unclear on the workflow needed to upgrade.  As a result it makes me a bit hesitant to perform upgrades on the server side, especially since we have to perform these upgrades during the evening or on weekends when support is not directly available.    Note this link was another one I consulted, for those following this thread. ... View more

 ... and why has this post been marked as 'Assumed Answered'?  ... View more

I'm glad I'm not the only one who like to have a list of questions/fields that a worker and/or dispatcher would fill out at the beginning of an assignment and then get automatically transferred to Survery123.  We currently have a small pilot project going on for a particular department and this limitation is a hold up; without this functionality I am not sure we can proceed going the 'paperless' route. ... View more

As a user that is part of organization that is really pushing for the usage of Pro over ArcMap, I found the hard way that there are indeed many different between the datetime modules/submodels.  Suppose I need to get to studying the link you provided ...  ... View more

...I changed the name of the 32 bit python to python32... What exactly did you change the name of?  python.exe?  pythonw.exe? Right now I am struggling with this issue on a server, both 32 and 64-bit versions of python are installed.  Even if I manually try to run a script using the 32-bit version, it always runs in 64 ...  ... View more

Glad to hear that this is a known issue and it will be addressed in the next release! As far as the second issue is concerned, I have not seen the behavior repeat itself.  I'm thinking it may have just been a hiccup; but I am not sure on which end ... the ESRI end or the Microsoft side? In any event, I am glad it has 'self-resolved' ... ... View more

Small update with regard to Issue 2.  To see if we could replicate the time issue I experienced yesterday, I had a survey submitted @ 1:28pm.  Lo and behold it triggered the email blast and spreadsheet population in SharePoint.  That appears to have debunked my 1pm time issue theory.  Plus I have not seen the non-triggering flow issue occur again. One thing I've read online is that a flow will not be triggered if a survey is edited after it's been submitted, however, there doesn't seem to be any way for that type of activity to occur due to the way we have this particular form set up ...  ... View more