What is the best practice for users creating list members?
What is the anaplan best practice for creating list members?
Say…. 200 users say they need to create 15 list members in a spoke model….
Is it best for the users to….
- Have them fillout 1 form per member using new UX “form” capability.
- Add 1 member in dashboard at a time with "Create" List Member action on a numbered list.
- Do upload template where users can import 15 at once.
- Input members in a form dimensionalized by a dummy list of 15 members and users. Users input their list members and then press an process/action for “create list members”
I could not find this discussed in OEG articles, but if anyone has a reputable article that discusses this, please do let me know.
Answers
-
I am guessing 3. and 4. are the best options in terms of performance and minimizing downtime.
However, I understand that importing from file to model performs worse than import that is within the model, so this makes me feel solution 4. is ideal.
0 -
@rob_marshall Any opinion or extra considerations here that I am missing?
0 -
Option 4: Create a user specific form within Anaplan, which is nothing but a module dimensioned by the user and a list called Index, which is nothing but has a few items in it like 1, 2, 3, 4, and so on.
This approach will give you the option to validate the data while the user is entering it.
You can give bulk export and import option as well so users can enter the data in an excel and then upload it into anaplan.
You won't have concurrency issues as module is dimensioned by users, so each user has it's own form to fill in and submit.
But if there is very less data that needs to be entered by the users or they just have to add a item in the list but create a NUX form. Option 4 is when you are entering a lot of information and you need real time validations.
0 -
@sychtysz18 - I would suggest you to go with Option 4.
You can create an Exception Dashboard where you can publish a grid with all the members you wanted in your list and simply click the Process to add those members in the list.
Additionally, you can apply additional conditional formatting if a user tries to enter invalid / duplicate record so as to avoid any issues or failure while running the process.
1 -
Sorry, I have been out on PTO.
Question, does every user in the model need to add the 15 members? If so, why? And why not have the list preloaded with these entries?
If it is a selected members, what is that criteria? I would be careful in dimensionalizing it by users because that would be for every user in the model.
Also, if I am understanding you correctly, Options 3 and 4 are basically the same thing, doing a bulk load of 15 "list" members. The only difference is in Option 3 you have a file that they are loading to.
@Dikshant be careful about the concurrency statement because any action created and run (especially run by end users) could be a blocking issue, whether it is dimensionalized by Users or not.
1 -
@rob_marshall
I would say yes, all users need to add 15 members. No source system has all the list members that are needed in the model, therefore, the users need to add these list members according to their discretion.
I would say users x 15 dummy list members is very small, so size wouldn't be an issue.
However, I thought in Anaplan, loading from file to Anaplan takes longer than an import within Anaplan, which I think would be a key difference between option 3 and 4.
If speed is important, option 4 would be the choice assuming there are only 4 options presented.
If concurrency is an issue, an option is to have users make their list inputs in the list in option 4) and schedule an import in off schedule time.
0
