Project Service Automation (PSA) for Microsoft Dynamics 365 includes an extension to the product catalog that allows us to define what product properties might affect the total amount. In this post I’ll describe when this might be used and how to configure quantity factors.
Imagine you’re selling software licenses, the unit price might be £115 per user per month. On the opportunity or quotation, you will want to enter the length of the expected agreement and the number of users. So 100 users for 12 months would give me a quantity of 1200 and therefore a sales value of £138,000. You can see below that I have entered exactly this on a product line on my opportunity.
Notice that next to properties I have an edit button, clicking this will allow me to enter the number of users and number of months required.
The concept of properties on a product is a standard feature of the Dynamics 365 product catalog. Properties are defined at the product family level and become available on any product within that family. If you haven’t used product properties before you can find a description of how they operate here.
Below you can see the product that I’d added to my example opportunity. First of all, notice that I have two properties on this product. These have been inherited from its product family. In my example the properties are months and users. Also notice that these have been given a default value. As the default in my example is 3 months and 10 users, when the product is added to an opportunity the quantity would initially begin at 30.
Underneath the product properties you will see the tab heading quantity factors. Its here that we define which of the properties to consider when calculating the opportunity quantity. (or product on quantity on a quote or contract line.)
When we add a quantity factor it’s given a name and we also pick the appropriate product property. Below you can see that the “Months” quantity factor relates to the “No of Months” property.
Note:
the computed transaction field only has one option of quantity, so you do not need to set this. (Who knows, maybe in a future release additional options will be added!)
One tip here is to always ensure your product and product family have been published after making any changes. The quickest way to publish the products is from the family. As then you can use the “Publish Hierarchy” option. (When you are adding products to an opportunity you can only add published products that exist as price list items for the product price list associated with the opportunity!)
Quantity factors might not be required in many situations but I hope you can see that in some sales situations they are a useful feature. J
Microsoft Dynamics 365 
Pingback: PSA – Opporunities | Microsoft Dynamics CRM and Unified Service Desk
Pingback: PSA – Complete Guide | Microsoft Dynamics CRM and Unified Service Desk
Pingback: PSA – Invoicing (Part One) | Microsoft Dynamics CRM and Unified Service Desk
Pingback: PSA – Invoicing (Part One) - Microsoft Dynamics CRM Community
Thank you very much, Neil,
for this clarifications. Unfortunately I am not able to completely reproduce what you have done here. I have a 3 tier hierarchy of product families, the first tier has no properties, the second tier has the property ‘no of users’, the third tier the property ‘no of months’. So, wenn I create a product related to the third tier, it has both properties ‘no of users’ and ‘no of months’, as in your case. So far so good.
Now when I try to create quantity factors and click on the look-up for properties, only one property is presented in the search. I cannot influence that. The whole hierarchy has already been published.
Can you tell me where I did an error in all that? Are quantity factors only possible with properties from the hierarchy tier above the product?
I would appreciate your answer very much.
with best regards
Ralph
LikeLike
That is a great question. I have only used properties from the tier above the product. From what you are describing it does sound like you are correct and the quantity factor can only be applied to the properties directly above.
LikeLike
This is good information, thank you. Unfortunately there is not much information on Quantity Factors and end results. I don’t quite understand how these factor into the quantity calculation. In my testing, the quantity is unaffected when populating the properties. How, exactly, does this work when adding products to a quote? Thanks.
LikeLike
Hi Mike
The idea is that you’d have quantity factors like number of months and number of users. Something like 10 users for 12 months would give you a line total of 120.
However, I have seen them working perfectly with the previous version of PSA in the classic web client. When I tested them in the newer Unified Interface version they didn’t work for me. (Which might be what you are seeing.)
Although I will also say that I haven’t tested them recently and Microsoft keep improving things. So just because quantity factors didn’t work for me a couple of months ago doesn’t mean they definitely still don’t work!! (So I encourage you to retest.)
Thanks
Neil.
LikeLike
Hi Neil,
Thanks for the response! I have not gotten it to work. I have not yet tested it using the classic web client but will do so. Depending on the results, I can log a case with Microsoft to assist. I’ll post the results.
Thanks,
Mike
LikeLike
FYI … latest versions of PSA are not supported on classic web client. Just to add a challenge!!
LikeLike