Dear All,
Do I need to use numbered list for the lowest level of the Alternative hierarchies? I read through couple of examples and training, which all use numbered list. I was wonder if this is necessary.
Thanks,
Lily
@LilyLiuAnaplan
You definitely don't have to, it depends on what is contained in the list. If you have members repeating, like products in a reason, then yes. Or if you have employees at the lowest level that can move among different departments, then yes. But if the lowest level is unique and will always be unique, then no.
Does that help?
Rob
First of all, my fingers got ahead of my brain, "reason" in the previous post should have been region. Secondly, tell me more about the list and how it will be used. The reason I ask, will users be able to add to it (Assign action on a Dashboard) or will it be a straight hierarchy used for reporting? If you will need the Assign function, then yes, it will need to be a numbered list, but if not and it just used for reporting, then no. Again, it all depends on what will be in the list and how it will be used.
Thank you so much, Rob. Yes, this is very helpful.
Hi Rob,
Thank you so much for your follow up. I definitely appreciated your quick response!
The list is a very straight hierarchy used for reporting and will not be used in any areas that would require a numbered list (e.g. add member, assign).
I was mostly concerned that the alternative hierarchy would interfere with the original hierarchy for being a clone.
Yajing
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!
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 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…
