I would like to know how your organization handle cases where customer A and customer B have a subscription together but the subscription they share is on customer A's record. Does your organization track such information in special requests at the lineitem level, or in associations, or somewhere else? What's the good and/or bad of doing it your way?We want to start tracking these cases with an eye toward treating customer B as a subscriber, and would like to hear your perspectives.
Thanks very much.Matt
Most of our consortium members also use an association. As an added layer of helpfulness, some of them also create a "sits with" alias so they are both immediately searchable from the constituent module. This allows you to pull up the correct record without first having to click through the association.
~Dan
So everybody's doing it the association way? Hm.... I was guessing the line item/special request method was the way to go since it offered more granularity, but maybe I'm over thinking things.
We do the special request method. It usually ends up in the order notes as well. In v11 we'll probably move to something more association-like.
I think why you are seeing the overwhelming use of associations is that the association is easier to see at a glance, and is an easy way to put something in a header to alert the box office that there is a 'sits w'. It also requires less digging if you are in the main account and not in the actual order module.
The other reason is that we often have groups of sits w and the special request only allows for one other account to be tagged. We have gaggles of ladies and some have seats in their own account, some share, etc. It can get to be quite complicated trying to keep track!
- Heather