App projects: Difference between revisions

Jump to navigation Jump to search
Line 113: Line 113:
* For information about the child project’s parts, whether they are inherited or changed in the child project, please check this additional [https://youtu.be/iLZ43KxGEW0?t=37m10s webinar]. {{Badge|Webinar}}
* For information about the child project’s parts, whether they are inherited or changed in the child project, please check this additional [https://youtu.be/iLZ43KxGEW0?t=37m10s webinar]. {{Badge|Webinar}}
* [https://blog.resco.net/2015/10/27/woodford-project-hierarchy/ Woodford project hierarchy] {{Badge|Blog}}
* [https://blog.resco.net/2015/10/27/woodford-project-hierarchy/ Woodford project hierarchy] {{Badge|Blog}}
=== Merge child changes to parent ===
The '''Flatten''' function allows you to merge changes in the child project into its parent.
For example, imagine three projects in a hierarchy:
* Parent
** Child
*** Grandchild
You have to select the project on the lowest level (in this case, the grandchild) and then click '''Flatten'''. As a result, all changes made in the grandchild project are merged into the child project. Depending on whether you’ve made changes in both child projects on the same item, the changes from the grandchild overwrite changes in the child.
Then, you can use flatten until you reach the highest parent-level project.
Before flattening the projects, please remember to back up all projects you wish to merge. Remember that sync filters of all entities are joined into one file, therefore, if you changed the grandchild's sync filter, flattening will overwrite sync filters in the child and parent project.


== Project menu ==
== Project menu ==

Navigation menu