Answered by:
account Licence tracking

Question
-
Hi guys... I'm a newby on crm but love the software and potential, so far with my limited db knowledge i managed to export and import data, create new atributes and connect forms... But im a bit stuck now...
Here is the requirement.
we sell spla licences to clients (accounts within crm) this licenses can be used 1000's of times by many clients, inclueding multiple times by the same client.
I've creates an SPLA atribute , it has:
SPLA name (description)
SPLA key (The actual licence)
At the moment i can go to a account and assign existent SPLA licences to that account. (so far so good)
Even got a custom report running , but that's another story.
Where im stuck is: if i need to add an existing SPLA licence to a client (account) more than once, i cant do it.
I need to be able to add duplicates or add some sord of multiplier ie: number of SPLA licences 1 or 2 or 3....
Any ideas would be very very welcome... i hope the issue makes sence.... pleas help, as this will earn mega brownie points with the boss.
Regards Dre
Thursday, June 24, 2010 5:58 PM
Answers
-
If it's a simple inheritance of a "price" value in the License Key table to the License Deployment table, then I would use the Mappings of the Relationship between the two entities to establish the mapping. However, to utilize the mapping, you would have to create all "License Deployment" records from the context of the License Key. You could populate the price using either Javascript, or a Plugin. The Plugin is a better idea if it's ever possible for License Deployments to be created in CRM without using the forms to do it (like with an import, or some other custom code).
Dave Berry- Marked as answer by Jim Glass Jr Tuesday, July 6, 2010 5:23 PM
Friday, June 25, 2010 3:53 PMModerator -
I would create a "pricing" module as a Plug-in and register it on the Update and Create messages of the "License Deployment" entity, so that it grabs the pricing from the associated "License Key" entity and applies a multiplication using a Deployment-local "markup" value. It may be a good idea to try and reuse the Product Catalog and Pricing schema, already in CRM, to provide pricing rules and adjustments. If, for example, you used a Product in connection with the "License Key" record, and simply configured Price Lists for the Product, your Plug-in wouldn't need to perform any real calculation for the "License Deployment" at all (except to multiply by quantity).
Taking this a step further: instead of putting pricing on either the "License Key" or "License Entity", perhaps it's best to utilize the Order or Invoice, so that a sales-related record with built-in sales processes is utilized to the greatest extent. Say that you create an Order/Invoice with a Plug-in or Workflow that reads the License Key to get the Product, the License Deployment for the quantity, and the Account for the default Price List, and assembles these together as line-items in the Order/Invoice. Now you have access to a complete Pricing system without having to perform calculations, reinvent the wheel, or extend your developments to expand the capabilities of simple calculations later on!
Dave Berry- Marked as answer by Jim Glass Jr Tuesday, July 6, 2010 5:23 PM
Wednesday, June 30, 2010 4:52 PMModerator
All replies
-
Well, you've already outlined the best two processes: duplicate records, or some "quantity" value (I'd prefer the later, personally). However, you're not going to find solace in using a N:N relationship in this case, because I assume that for any given key, the quantity may differ vastly between account records. What I think you should probably consider (for flexibility sake) is splitting your license entity into two entities:
1.) a License Key
2.) a License Deployment
The License Key allows you to properly link and understand the relationships of a Key/Name combination through the License Deployment which manages the quantity and specific relationship to an Account. The License Deployment is a middle-man entity that abstracts the unique properties of the License Key away from the messy entanglement scenarios of "deploying" the key to several accounts in nonuniform quantities.
Dave Berry- Proposed as answer by DavidBerryMVP, Moderator Wednesday, June 30, 2010 4:40 PM
Thursday, June 24, 2010 8:39 PMModerator -
Thank you very much dave... Worked like a charm....
Now need to find out how to pull values ie: price from the spla license to the Deployed table.. (midle man table) look arount the net and everithing i read seems to involve coding. Thats way beyond me.
Thanks again...
Regards
Andre
Friday, June 25, 2010 2:49 PM -
If it's a simple inheritance of a "price" value in the License Key table to the License Deployment table, then I would use the Mappings of the Relationship between the two entities to establish the mapping. However, to utilize the mapping, you would have to create all "License Deployment" records from the context of the License Key. You could populate the price using either Javascript, or a Plugin. The Plugin is a better idea if it's ever possible for License Deployments to be created in CRM without using the forms to do it (like with an import, or some other custom code).
Dave Berry- Marked as answer by Jim Glass Jr Tuesday, July 6, 2010 5:23 PM
Friday, June 25, 2010 3:53 PMModerator -
Got it working in the end.... It was right in from of me... The report run fine now, so the admin people can run the report and see wich clients Have SPLA licences deployed.... Cool
Next i need to do some calculations on the report... ie: add our markup to the prices... As far as i can see , it will involve coding.... And thats where my skills fall sort... I will need to invest on a development book....
Any idias or advice regarding calculations in forms.... i get the prices to add up fine at the end of each page... But like i said need to add mark up...
Also still need to figure it out some sort of multiplier box, in the Deployed SPLA's form as at the moment i have to add them manually multiple times....
Thank you very much again mate, sorry for the delay replying , been very busy.
Regards
Dre
Wednesday, June 30, 2010 10:05 AM -
I would create a "pricing" module as a Plug-in and register it on the Update and Create messages of the "License Deployment" entity, so that it grabs the pricing from the associated "License Key" entity and applies a multiplication using a Deployment-local "markup" value. It may be a good idea to try and reuse the Product Catalog and Pricing schema, already in CRM, to provide pricing rules and adjustments. If, for example, you used a Product in connection with the "License Key" record, and simply configured Price Lists for the Product, your Plug-in wouldn't need to perform any real calculation for the "License Deployment" at all (except to multiply by quantity).
Taking this a step further: instead of putting pricing on either the "License Key" or "License Entity", perhaps it's best to utilize the Order or Invoice, so that a sales-related record with built-in sales processes is utilized to the greatest extent. Say that you create an Order/Invoice with a Plug-in or Workflow that reads the License Key to get the Product, the License Deployment for the quantity, and the Account for the default Price List, and assembles these together as line-items in the Order/Invoice. Now you have access to a complete Pricing system without having to perform calculations, reinvent the wheel, or extend your developments to expand the capabilities of simple calculations later on!
Dave Berry- Marked as answer by Jim Glass Jr Tuesday, July 6, 2010 5:23 PM
Wednesday, June 30, 2010 4:52 PMModerator -
Thanks for the advice, will have a go at it... and try to use the current order invoice system.... wish me luck...
Regards
Dre
Tuesday, July 6, 2010 10:19 AM