We had wanted to get some advise on an issue we have
Using the sample "Ordering" application or even the CRM as an example.
We have a Customer BO in which we need to assign Sales reps to as the customers Primary, Secondary and Third contact point.
We did not want to create 3 different relations but instead have one, and be able to have a field in which we Choose - Primary, Secondary and Third etc.. This obviously does not work as the Salesmen then have a ranking which is changed each time we add a new customer.
ranking maybe not the correct word but here is an example:
We have a customer database and each Customer is assigned 3 sales reps.
Each sales rep is either Primary, Secondary or Third responsible
Solution 1:
On the Customer BO, create three Attributes which are SalesRep1, SalesRep2, SalesRep3 which are all relations to another BO called Employees.
This is the current way we do it but its messy feeling as we have to have
more of the forms space used.
Solution Prefered
On the Customer BO, create one Attribute called SalesReps - allow edit as a grid - and SOMEHOW allow a drop down to Assign each Choosen rep as Primary, Secondary and Third
But in short - We are just seeing if anyone has ideas about reducing the Ref. Attributes.
basicly it would be like a BSV which was for you to rank your top 10 favorite movies. users would login be able to select in a data grid to add movies and rank them somehow.
you would have a BO called Movies, and it would have a relation to RegularUsers BO. As a logged in RegularUser you could somehow rank your top ten movies, without creating 10 Attributes with Relations to Movies.
