Update existing members
To import updates to an existing member, the structure data must contain the name of the member and the new property values to use. For hierarchical dimensions, the parent name must also be specified.
To change a member's name, the structure data must contain the member ID and the new name for the member.
Although schedule name is also required; it does not have to be included in the structure data used to define schedule lines. This property can be defaulted during mapping if the schedule lines in the structure data belong to the same schedule.
This diagram uses the Schedule dimension to illustrate how structure data is affected by updates to existing members. Member updates occur when a member listed in the structure data matches a member that already exists in the database dimension. See the example structure file:
- Line, Acct, Sign
- SchedLine D, PE, D
- SchedLine B, BA, C
Is imported into this Schedule dimension:
Schedule line | Account type | Natural sign |
---|---|---|
SchedLine A | PR | C |
SchedLine B | BA | C |
SchedLine D | PE | C |
SchedLine E | PE | D |
Then SchedLine B and SchedLine D are changed as shown here:
Schedule line | Account type | Natural sign |
---|---|---|
SchedLine A | PR | C |
SchedLine B | BA | C |
SchedLine D | PE | D |
SchedLine E | PE | D |