Closed kgonzago closed 6 years ago
I ran this on Pro 2.2.12776(Beta2) and setting the symbology/labeling on the output layer using a lyrx file seems to be now working correctly for setting the labels. So this issue is dependent on Pro 2.2 final:
There is just a small code change needed (here) to check whether in Pro or ArcMap because a Pro .lyrx file is needed to make the GP output labeling work (a 10.X .lyr file doesn't work for this labeling scenario)
Moving/migrating NumberFeatures tool opened with issue: https://github.com/Esri/military-tools-geoprocessing-toolbox/issues/339
FYI @topowright @BobBooth @dfoll @ACueva
@csmoore - cool! So, an if product == ArcMap use lyr, if product == Pro use lyrx check here is all it would need?
@BobBooth - that is correct. There is an existing method/utility for this - though its behavior is not consistent if run from arcpy outside of the Pro/ArcMap - since it returns: 1. Pro 2. ArcMap 3. Other (standalone arcpy but could be Pro or ArcMap python) - so we may need to add a method
This issue was moved to Esri/military-tools-geoprocessing-toolbox#341
6/13: Tasks remaining
When creating a new feature layer (feature class) during the Number Feature tool process, the tool:
Expected Behavior
Features should be labeled in the newly created feature layer
Current Behavior
Run tool on: Get result: Features are not labeled.
Possible Solution
Update LYRX file to provide labels as well as symbology.
Steps to Reproduce (for bugs)
Context
Your Environment