Skip to main content
June 18, 2025
Question

Base member that becomes a parent member

  • June 18, 2025
  • 2 replies
  • 0 views

Hi all,

 

How should it be managed in case a base member containing data should change to become a parent member? Is there a preferred procedure to follow?

 

Thank you for your help.

Best regards,

Carlos

2 replies

June 18, 2025

If a base member has data and you now need to make that base a parent, you will lose data unless you:

Option 1 - not preferred if you are live

  1. Rename that current base member as 3110_Base as an example
  2. Create a new 3110 and put 3110_Base under it
  3. Update your mapping and reload all data (including journals and you may need a spreadsheet to grab any O#Forms data if entered to 3110

Option 2

  1. Create a new member called 3110_TOT and make it the parent of the existing 3110
  2. In this way you will not lose any data that went to account 3110

If you are live or far along in data validation and development, I would lean towards #2.

 

 

June 20, 2025
New   
CreateTOT_3110  
Move3110 under TOT_3110  
Rename3110 to 3110_NEW  
RenameTOT_3110 to 3110  
update rule, form if you have base member ref or replace DIM#3110.base