MahargNala
asked on
Customizing Products in CRM 4.0
We have just started to look at Microsoft CRM 4.0 for a client and we have a very basic problem
Out of the box the Product entity assumes that the client is selling a "widget", however our client is selling insurance policies. Therefore each "Product" would be a unique price.
We would like to set up the product to reflect this but are cannot seem to amend this entity because it is a "system" entity
Does anyone have any suggestions or experience of this type of issue with the insurance industry?
I may not have explained very clearly but I am unsure where to start
I look forward to any advice received
Out of the box the Product entity assumes that the client is selling a "widget", however our client is selling insurance policies. Therefore each "Product" would be a unique price.
We would like to set up the product to reflect this but are cannot seem to amend this entity because it is a "system" entity
Does anyone have any suggestions or experience of this type of issue with the insurance industry?
I may not have explained very clearly but I am unsure where to start
I look forward to any advice received
When you add products to the product catalog in CRM you have to provide certain pieces of information including price.
If you are selling an item that will have a different price every time then enter a notional price in the catalog and then when you add the product to an order you may override the price with the specific price for that customer.
What is that you are trying to customize?
If you are selling an item that will have a different price every time then enter a notional price in the catalog and then when you add the product to an order you may override the price with the specific price for that customer.
What is that you are trying to customize?
ASKER
Hi Guys
Thanks for your response
My plan was to use the product entity as a starting point because it has all the relevant links re relationships, attributes etc.
I would then clone this and amend for each policy area i.e. liability, household
I would then further amend to allow different screens for the different policy types within each area i.e. Liability for tradesmen, hosue contents or buildings cover
I suppose I was being a little lazy and not creating a custom entity which I think will end up being the solution
I hope this extra information helps
Regards
Mahargnala
Thanks for your response
My plan was to use the product entity as a starting point because it has all the relevant links re relationships, attributes etc.
I would then clone this and amend for each policy area i.e. liability, household
I would then further amend to allow different screens for the different policy types within each area i.e. Liability for tradesmen, hosue contents or buildings cover
I suppose I was being a little lazy and not creating a custom entity which I think will end up being the solution
I hope this extra information helps
Regards
Mahargnala
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Feridun
Thanks for replying so promptly
First point - I will have a look at this shortly and get back to you
Second - You are correct with regard to different data to be stored
Thanks for replying so promptly
First point - I will have a look at this shortly and get back to you
Second - You are correct with regard to different data to be stored
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Aftab
I am seeing your point and it would appear that due to the fact that there would be a number of varying "product types" the custom route could cause less issues further down the work flow line
I think I need to experiment with both suggestions and get back to you guys
I really appreciate the assistance and guidance given so far
I am seeing your point and it would appear that due to the fact that there would be a number of varying "product types" the custom route could cause less issues further down the work flow line
I think I need to experiment with both suggestions and get back to you guys
I really appreciate the assistance and guidance given so far
ASKER
Thanks for the assistance it has confirmed the actions I need to take
let me know the details and i will provide as much information required