Timeline for Use updatcursor to replace values in multiple fields
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 3, 2014 at 13:18 | comment | added | Scott Fierro GISP | I see what you are saying, I only tested for it there as a 1 time check that whoever made the ETL didn't grab a wrong field. We are using set fields that will never change and this will become a fully automated process where the 11 string fields will be the checked parameter inputs that we are interested in. I did at one point run into an error that the arcobject wasn't being properly converted to a python object for the list fields but I think even if I build out the fieldType as you show I'd still have an issue looping through that list in the iterations part. | |
| Oct 1, 2014 at 20:28 | history | edited | Richard Fairhurst | CC BY-SA 3.0 |
deleted 2 characters in body
|
| Oct 1, 2014 at 20:21 | history | answered | Richard Fairhurst | CC BY-SA 3.0 |