Renaming the line item - Best Practices

Hello all,

I need to rename a line item in a large model, I am wondering what are the best practices to do this?
What should I consider before renaming to avoid destroying the model?

Thank you in advance for your help!

Accepted answers

abhay.kanik

@Dominika_Dudzinska

I don't think it will have any impact, Name of line item wherever it is referenced will be changed automatically whether be it a formula or line item subset, or even if you have used select statement with LISS .

MarkWarren

A line item can be safely renamed, it will not affect any functionality. Every line item has its own internal ID that is used for the references within Anaplan.
The only best practices are to avoid using special characters or emoji in the name.

All comments

Thank you for your help!

jczimbal

One thing to consider is if you are using the line item as a source or target within an action, whether model-to-model or external source-to-model. If you are using 'Match on names or codes' for the line items and you change the name of a line item then it will not be part of the mapping. If 'Map items manually' is selected then you will be fine.

Vinay VaradarajM

Hi @Dominika_Dudzinska , @jczimbal ,

Renaming a lineitem which is used as a source in any import action will break the mapping (even if you use Map items manually)

Please consider revisiting such actions (if any), to do the remapping!

Regards,

vinayvm

philip.austin

Anyone reading this thread, please upvote the following Idea from Idea Exchange.

https://community.anaplan.com/discussion/160270/renaming-a-line-item-dont-break-import-actions/

Quick Links

Can you help?

Unanswered questions

How to use Client ID and Client Secret for API request directly?
Hi all, The Client ID and Client Secret are available, intended for uploading and downloading files. Could anyone advise how to use these credentials DIRECTLY to make API requests? Thank you!
New UX Filtering for Hierarchy sibling
I have A6 as the parent list and two sibling lists: A6.5 and A7. The A7 list includes an attribute that maps to A6.5. In the UX, the user will select A6.5 using a content selector, and the grid (dimensioned by A7) should display only the A7 items associated with that selected A6.5. Since the selector is a page context and…
A reminder of Bulk Copy - Current year to Prior year version for YoY analysis
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…