We want to ensure that after the Account assignments have been made that each of those members has a code.
@ChrisMullen A few related questions about account assignments:
I am a little confused with assigning accounts to territories. I am viewing customer accounts as a numbered list that includes the country they operate in. If there is only one customer account per country how could I assign an account to multiple territories? If I use USA as a filter for my system and show the list of accounts in the USA, I can allow a user to input through a drop down which territory they want to assign that account. Since their are no duplicate accounts the user would be unable to assign an account to multiple territories.
Each country has 2 to 4 territories. Would a territory include multiple countries? So Company A USA and Company A CAN should be assigned the same territory? The solution is Company A USA and Company A CAN should both have the same territory even if one of them throws a flag for having a territory in another country?
Or are you saying an account has multiple products and each product should be assigned a territory? Company A has Prod 1 and Prod 2. Prod 1 can be assigned to a product territory specialist and Prod 2 to a different territory?
I guess I am just confused as to why I would build a system that allows users to assign multiple territories to the same customer account? Feel like I am missing something.
A Country has multiple territories.
For Example in the United Kingdom, You have 3 Territories UK England - UK Wales - UK Scotland & NI
MetaCandy is an Account that is located in the London, the request that we have is that we want Assign this account to a territory. For Example, UK England.
Hi @ChrisMullen,
I will post again my question of 4 weeks ago:
Why are you so keen on using the Assign function?
My first intuition also says: why using the assign functionality at all. Why not start with the simple drop down (filtered on only the country's territories) to assign an account to one territory. This will make both user stories 2.2 and 2.3 unnecessary.
I would advise to start as simple as possible, and only add complexity if really required.
What is the functional benefit of using the Assign function in this use case?
Would the country sales operations manager(s) be open that we will showcase multiple options and after that we can choose to use the assign function or not.
Is the requirement of the assign function purely for us to demonstrate we can use it?
NB: I have not start building anything yet for level 3 (so maybe my understanding is still limited).
Thanks.
Kind regard Guido
it is a requirement because we want those who are level 3 model builders to know how to use it.
Hi @Guido.kaandorp ,
In a real life scenario we might use a different approach which is more solid in terms of code creation. The main reason for using this way of creating the items, as Chris pointed out, is to practice a different way for managing lists items. For example when we work in the new UX, one of the features for creating items in a list is highly similar to the Assign function from Model 3.
I wish you all the best with the build! Hope this helps.
Kind regards,
Costa
@Guido.kaandorp nice to read that you have the same line of thinking. 😎