Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We have a number of products which have optional features or limitations the customer can elect to have. We operate a SaaS business and these might be things such as geographic regions, number of users, volume bands or modules. These may or may not affect price, and are important for our sales team to know when there are repeat sales.
What is the best way of storing this information? We looked at product family parameters, but they seem very much to be fixed items, whilst this would be different for each sale.
Any help gratefully received
Since these optional features are based on the product item at the time of sale, not the product itself, we can add these additional content to the form of the Product Line Items.
Take number of users of Opportunity Line entity as an example.
1. Create fields such as geographic regions, number of users, volume bands or modules for the Opportunity Line entity.
Here you need to pay attention to the Data Type of field. Geographic regions, volume bands or modules should be Single Line of Text or Option Set. The number of users should be the Whole Number, and the Minimum Value should be 0.
2. Add these fields to the OpportunityProduct form. Save and publish.
3. Go to the Opportunity page. When we edit the product of the opportunity, we can edit this information in the Opportunity Line: OpportunityProduct form.
In addition, there are two points to note.
1. In order to add these optional features to Opportunity > Quote > Order > Invoice, you need to create these fields in Opportunity Line, Quote Line, Order Line, Invoice Line.
Then, add a mapping of these fields in their 1:N relationships. (There is no OOB 1:N relationship of Opportunity Line and Quote Line, you need to create it first.)
In this case, when you create a Quote from an Opportunity, the values of these optional features are inherited to the Quote Line. The same operation applies to the Order Line and Invoice Line.
2. In order to analyze these optional features, I recommend that you set the field Data Type of geographic regions, volume bands or modules to Option Set. Otherwise, if it is a Text type, its rules and formats cannot be restricted.
If you are not familiar with the mapping of fields, you could refer to this article:
map entity fields
Hi Lu Hao,
Thank you very much for this detailed reply, it is very useful. One thing additional if that is ok:
With respect to the things like volume bands - there will be a band that is included in the price on the opportunity line and a series of bands that will indicate additional prices. So our example may be:
0-100 items: include
101-1,000 items: $100
1,001-10,000 items: $1,000
We thought the best way to represent this would be to have a "bands" entity which would have a maximum and minimum value, a type (eg "item") and a price. We would then link these items to the Opportunity line and show in a grid.
Do you think that is the best way or can you advise another way to achieve this?
Please post a new theme. This will let other experts participate in the discussion of this problem.
Also, I don't fully understand your needs. Could you elaborate it in the new post? You could provide some screenshots.
If I have a solution, I will definitely reply to your new post. Don't worry.
Finally, if my last answer was helpful, click Yes to mark it as verified.
thank you Lu Hao
I have created a new thread here if you have any comment
Business Applications communities