Core data is an incredible interface between the underlying database and you as a programmer.
Though there are many things which need a deeper understanding of how core data handels things you’ll notice steep learning curve.

Once you have your model defined and core date generated your accessor methods you’re ready to start.

You access core data class properties in KVC manner wether with dot syntax „myClass.myProperty“ or [fusion_builder_container hundred_percent=“yes“ overflow=“visible“][fusion_builder_row][fusion_builder_column type=“1_1″ background_position=“left top“ background_color=““ border_size=““ border_color=““ border_style=“solid“ spacing=“yes“ background_image=““ background_repeat=“no-repeat“ padding=““ margin_top=“0px“ margin_bottom=“0px“ class=““ id=““ animation_type=““ animation_speed=“0.3″ animation_direction=“left“ hide_on_mobile=“no“ center_content=“no“ min_height=“none“][myClass valueForKey:@“myProperty“].

In the second case it wouldn’t it be nice to have a unique identifier used through all your classes and whenever it comes to property name changes only one place needs to be changed.
You might say a global search and replace is a good remedy but what if you have to classes with the same property name?

If you faced the same problem use the automator service attached to convert a @dynamic myPropertyName captured from the .m file to #define k_PRE_MyPropertyName @“myPropertyName“ and replace the _PRE_ with whatever you find appropriate to distinguish the same property names between different classes.

Download the automator action here[/fusion_builder_column][/fusion_builder_row][/fusion_builder_container]