Delete orphan records from a Properties module

DeepakK · 2023-04-20T22:56:04+00:00

There was an error rendering this rich post.

Hello all,

I want to change the rollups of Cost Center into its parent Division in hierarchy (i.e. Cost Center 100 belongs to Div 1 today. I want to change to Div 2).

I can make teh change and write the data correctly. But I can't think of an automated way to delete 2 levels of hierarchy under the existing cost center. (i.e. Employees belong to Cost Center. All employees rolling up to Div 1 should now go to Div 2). When I build the new mapping and delete the old cost center rollup, everything underneath it gets orphaned (as it should). But my data is doubling since I now have 2 records.

Does anyone know how to just delete orphan records?

I did a ISBLANK(PARENT(Item) in the Employee properties module. But when I have orphan records, it doesn't show in the module at all. It only shows what's in hierarchy.

Accepted answers

DeepakK

@pyrypeura Not sure why but I couldn't see those orphan records in the module. Once teh parent is deleted, they are visible in list, but not module.

@Emmeline That's a good idea, maybe I can try that next time.

For now, I did a comparison of the Parent level with a lookup to the Parent's module and a FIND from the current row's code. When they are not the same, it checked a boolean box. I used that boolean to do a Clear list action. I have to delete everything before I add the new mappings.

Thanks for the help!

All comments

pyrypeura

Hi,

The orphans are also visible in bottom of the module (after the total item). If you don't see any orphans there you have either updated the old cost centers to new parents or already deleted the orphan items.

Best regards,

Pyry

Emmeline

Hi,

Maybe you could use number line items to identify parent levels?
For instance, create a line item dimensioned by parent level with "1" as formula. On a second line item, get the 'parent line item number'[lookup : parent]. Then with a boolean, identify items equal to 0: they are orphans. Finally, use an action "delete from list using selection".

DeepakK

@pyrypeura Not sure why but I couldn't see those orphan records in the module. Once teh parent is deleted, they are visible in list, but not module.

@Emmeline That's a good idea, maybe I can try that next time.

Thanks for the help!

Quick Links

Can you help?

Unanswered questions

Best way to Architect Financial Statements in Anaplan for Scalability
I have seen two methods used to build financial statements and I am wondering what others have experienced in scalability/maintenance between the two or if there is a better approach. Assume that we have a flat data source for our general ledger within Anaplan. Our line item we are focused on within the source data is the…
Curious Comparison: Forecast Modeling for Unusual Products
I've been experimenting with some forecast modeling techniques in Anaplan recently and decided to test them on a few quirky, offbeat product categories just for fun. One of the categories I played around with was love dolls—yes, you read that right. It actually turned out to be more interesting than expected. Unlike…
OData Rest API for
Hi, Does anyone know how to get an outbound OData Rest API, (OAuth2) to establish a connection between SAP and Anaplan. Thanks Khaled