Latest Contributions by AllenDailey1

I wonder if this behavior is because in Pro you don't have to formally open an edit session, you can just click and start editing in the table?  so it's like always in edit mode?  not sure.  Anyway, yes, it would be helpful if it didn't have a lock when you're viewing the table. ... View more

Hmm, it's hard to think of one word that clearly communicates the meaning, so I can see why Esri does not already have a better word here.  I think "select" would be good, because "select" says that you're picking the highlighted rows and they'll be blue (rather than yellow) because we know that selected rows are blue.  "Reselect" - with the "re" prefix - implies to me that I would be returning to some previous state (instead of going to a new state where the currently selected (blue) rows become unselected), like where the highlighted rows are returning to be a part of the original larger selection, which we know is not what the button means. Here are my favorite word choices: Select Refine Limit Only Maybe also "cull," but that might sound weird because it's usually used in scenarios like, "We need to cull the herd of cattle and kill some of them," which sounds violent or sad! ... View more

I agree.  Whenever I see "reselect," I envision returning the highlighted features back to "regular/plain" selection, while also keeping the other regularly-selected features selected.  In other words, keeping all current selections, but make the yellow features blue.  Since that's not what the button does, I do find it confusing and I have to read the button description every time. ... View more

Hi there, I went through a really long saga trying to troubleshoot a script that worked with Pro but not with ArcGIS Server Python.  I went through a service ticket with Esri and it took a lot of back and forth.  After much work, we finally determined that my script didn't work when run with the Server python because it was not connected to the license manager.  Arcpy geoprocessing tools have to be connected to the license manager in order to run, even though you can run basic Python (other than geoprocessing) (I REALLY wish Esri made this fact more evident!! It took untold hours and weeks for us to learn this fact).  In my case, I was trying to run it on a server in our public DMZ, and our license manager is on a server in our internal network, and those cannot connect in the desired way, so it was impossible for the public DMZ server's python to be licensed.  We came up with a workaround to run the script in the internal network and it would copy files to the DMZ server rather than directly working on those files from the DMZ. Sounds like in your case, you are logging into a portal rather than using a license manager?  I'm not familiar with the intricacies of that.  But I wonder if it could be a similar situation, where somehow ArcGIS Server python has limitations when it comes to certain kinds of connections??  I dunno.  Sorry I don't have an answer.  But I thought I'd share all this in case it happened to be of any use to you or someone else looking at this post. Good luck!!! ... View more

@AlyciaRajendran_esri , Thank you for the info! 🙂  That's interesting to know it's a bug.  Thanks! ... View more

* Edit: I like BlakeTerhune's reply! That's better than my idea. * That's great that you're trying out cursors! When you say "each row in a field," by "row" do you mean feature/record, and by "field" do you mean an actual field/attribute?  I ask because usually with cursors, the word "row" can be a variable that might refer to attributes of one feature/record, in certain forms of syntax.  Just wanting to make sure I understand what you're getting at.   Say you are wanting to assign those values in your list to three separate features/records in your table.  One way to achieve what you mentioned is to use a counter.  There might be a better way to do it; I'm experienced but not an expert.  Just keep in mind that the first item in your list is index number 0, of course. Also keep in mind that which value gets applied to which record in your table depends on how the table is sorted when you run your code.  It does not necessarily run in order of ObjectID's.  I'm not sure what the scenario could be where you are doing what you're describing - maybe it would help if you explain that. Here's an example of using a counter:   import arcpy arcpy.env.workspace = r"path\to\geodatabase" fc = "fc_name" field = "fieldname" valuelist = ["a", "b", "e", "z"] # Values to be inserted with arcpy.da.UpdateCursor(fc, field) as cursor: count = 0 # Starts at zero because list index starts with zero for row in cursor: # For each record in the table: # This is supposed to prevent the following line from erroring # out if count exceeds the length of the list while count < len(valuelist): # Assign value from the valuelist to the record in the table row = valuelist[count] # Increment count to select next valuelist item next time count += 1 cursor.updateRow(row)   ... View more

I agree with the previous two comments! ... View more

I came up with a workaround.  Instead of using a "where clause," I just added an "if" statement later in the script to exclude records that would have been excluded by the "where clause." Basically, within a Search Cursor, I put lines to this effect:   with arcpy.da.SearchCursor(fc, fields) as cursor: for row in cursor: # Only include records where APN exists: if row[0]: # row[0] is the APN # then do stuff     This works, but it would be less clunky to just be able to use a "where clause" in MakeTableView.  I'd still be very interested to find out why it doesn't seem to work with the type of table I'm using. ... View more

Later in the script, data from the table view is manipulated - hyphens are inserted between the numbers in the field "APN".  This throws an error, because that action can't be done on Nulls.  So that means the records where APN is null were mistakenly included in the table view (meaning the Where Clause was ignored).  For troubleshooting, I also included a print statement that prints out the APN's of the records included in the table view - print("APN is " + APN).  For the records that have a value in the APN field, it prints, but for other records it errors out, saying it can't concatenate string and NoneType. For troubleshooting, I tried running MakeTableView, including a Where Clause, on a geodatabase feature class rather than a SQL Server database table (which was the original data format I was running it on), and the Where Clause worked!  So now my theory is that the problem is the data table type.  Maybe I will try adding code to my script to first convert the database table into a geodatabase table or something, before doing MakeTableView.  That would defeat the purpose of having intermediate products just be in memory, but that could be okay. ... View more

Thank you very much for your suggestion! I tried your suggestions, and sadly, the "where clause" is still being ignored.  So weird. ... View more

I also got this error, and for me, the solution was this: I had added a new feature class to an enterprise geodatabase in a dataset, and this undid the original settings like making the geodatabase versioned.  So I eventually found that I needed to re-enable versioning for this enterprise geodatabase.  This solved the problem, and I was then able to edit the feature class. ... View more