You may find that you need to rename a Database Map folder or move it to sit under another folder or at another level of the tree.
If you edit a Database Map folder that has lower level child components, e.g., you rename a practice level folder which contains Client level items, the child items will become orphans and are lost. To avoid this, use the right-click menu in the Database Map Explorer pane to copy the item to be edited to the current level before the edits are applied at the higher level. In this way, the child components are retained in the lower level version. The copied item will be saved at the Practice or Client level depending on the level at which you opened Report Designer.
If you modify a Database Map item that is referenced by a Format, you will also need to modify the Format accordingly as there is no flow-through of the update to the Format when a Database Map item is changed. For example, if you change the Database Map folder CashFlow to Income, any references within Formats to the Database Map folder CashFlow will not automatically be changed to Income, and will therefore fail.