Solved! Go to Solution.
Thank you for reporting this! You are correct; late in 2.4 development we changed the CamelBack format of the object members to be consistent with the managed API. I failed to update example 3 and you caught it. The script was corrected and will appear in the next help publication.
The missing line that you added is NOT required if the symbol already has a dashed effect. What the line did essentially was generate the effect. This is something you need to be very careful about doing. The Developer Summit plenary video does show the line you added. That particular example is a simple use case but due to the complexity of object creation where new objects have dependencies on addition objects, it is easy to create objects that may fail in the application.
The arcpy.cim module is necessary for CIM support but we intentionally did not document it. We hope that with future builds we will provide helper functions that will make it easier and more reliable to create new objects.
Thanks again,
Jeff
Python CIM access—ArcPy | ArcGIS Desktop
and in your install path for exploration
C:\YourInstallFolder\Resources\ArcPy\arcpy\cim
Thank you for reporting this! You are correct; late in 2.4 development we changed the CamelBack format of the object members to be consistent with the managed API. I failed to update example 3 and you caught it. The script was corrected and will appear in the next help publication.
The missing line that you added is NOT required if the symbol already has a dashed effect. What the line did essentially was generate the effect. This is something you need to be very careful about doing. The Developer Summit plenary video does show the line you added. That particular example is a simple use case but due to the complexity of object creation where new objects have dependencies on addition objects, it is easy to create objects that may fail in the application.
The arcpy.cim module is necessary for CIM support but we intentionally did not document it. We hope that with future builds we will provide helper functions that will make it easier and more reliable to create new objects.
Thanks again,
Jeff
Hi Jeff,
It's been about a year since you wrote the note above. Would you say that at this point the helper functions that you anticipated have been released? Or are they still a work in progress?
Or would you say the trajectory of fine-graded access to symbology changed so that arcpy users are more likely to need to learn the nuances of CIM?
Thanks in advance for your insights.
Laura
Hello Laura,
Yes, at 2.5 we introduced this. THere is a new section in the Python CIM Access topic titled Creating CIM Objects.
Python CIM access—ArcGIS Pro | Documentation
Jeff