Timeline for Accessing "valueField" property of layer's symbology using ArcPy?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 26, 2020 at 7:58 | comment | added | FelixIP | @PolyGeo mxd should be first. | |
| Feb 26, 2020 at 4:57 | comment | added | PolyGeo♦ |
Your lyr and mxd objects are created in a different than expected order. Did you create your original mxd object in an identical way to the way you overwrote it?
|
|
| Feb 25, 2015 at 23:00 | comment | added | Marco_B | PolyGeo: I wasn't trying to show code, I was trying to illustrate a possible issue with auto-completion / property presence that I thought relevant. FelixIP: yes, I am glad it now worked out, cost me a day though as I was on some sidetracks before suspecting the problem with the failed script, and model chain it was part of, was in the symbology related code... | |
| Feb 25, 2015 at 22:17 | comment | added | FelixIP | Glad it works for you | |
| Feb 25, 2015 at 22:17 | comment | added | PolyGeo♦ | I think it is always best to include code as text rather than pictures to aid searches and tests by future visitors. | |
| Feb 25, 2015 at 22:06 | comment | added | Marco_B | Thanks. I had actually tried it this way too, but now noticed I had another issue going on: I actually was processing a small list of layers, and one, although strictly speaking "unique values", actually uses two fields, and registers as "OTHER" symbology type because of that. That type unfortunately doesn't support accessing the valueField property (of course, there are multiple in this case). Skipping it, and implementing your code, made it work. | |
| Feb 25, 2015 at 22:03 | vote | accept | Marco_B | ||
| Feb 25, 2015 at 21:39 | history | answered | FelixIP | CC BY-SA 3.0 |