{"id":1680,"date":"2015-08-27T14:46:21","date_gmt":"2015-08-27T09:16:21","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=1680"},"modified":"2015-08-27T14:46:21","modified_gmt":"2015-08-27T09:16:21","slug":"price-list-selection-logic-available-starting-dynamics-crm-2015-update-1","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2015\/08\/price-list-selection-logic-available-starting-dynamics-crm-2015-update-1\/","title":{"rendered":"Price List selection logic available starting Dynamics CRM 2015 Update 1"},"content":{"rendered":"

Introduction<\/strong><\/p>\n

Traditionally Price List in any of the transactions like Opportunities, Quote, Orders or Invoices was set by reading it from Customer. If there was no price list set for the customer, it would be left blank and the user would be required to set it manually. Price List is critical and needs to be set since the line items on these transactions depend on the Price List selected. You are only able to add Products that have prices defined in the selected price list.<\/p>\n

With the new release Microsoft has shipped in automation to process of setting Price List on these.<\/p>\n

Price List Based on Territory<\/strong><\/span><\/p>\n

Another way to associate Price List that has been introduced in Update 1. In this Price List needs to be associated with Territory and User is associated with a Territory. The Price List would be set based on the logged in user\u2019s territory if there is no default Price List set for the customer.<\/p>\n

By default this feature is activated in all new CRM Online trials. You can check the settings in Settings windows.\"price<\/a>Next step is to associate Territories with Price List through Territory grid available in Price List (which is essentially connections re-purposed). You now find an OOB Connection role Territory Default Price List. Make sure to create the connection from within the Price List.\"price<\/a><\/p>\n

Associate this territory with the User.<\/p>\n

Now when a new Opportunity is created, and the customer does not have a default Price List set, it would be read from the Territory Default Price List connection.\"price<\/a><\/p>\n

Note:<\/strong> If more than one price list is associated with a territory, then the price list is not populated. This should be enhanced to allow associating multiple pricelists with a territory for with a unique pricelist for each currency.<\/em><\/p>\n

The region NA may need to serve customers in America as well as Canada and create opportunities in both these currencies. Depending on the currency of the customer, the Price List should be set from the territory.<\/em><\/p>\n

If you have only one currency price list associated with a Territory and you try to create an opportunity for a customer in another currency you receive the following error\"price<\/a><\/em><\/p>\n

Price List Based on Custom Logic<\/strong><\/span><\/p>\n

Another way to get the Price List for an Opportunity is through custom plugin. We now have a new message \u201cGetDefaultPriceLevel<\/strong>\u201d available on which Plugin can be registered.<\/p>\n

Here is a snippet of how the pricelevel can be passed through the plugin<\/p>\n

public void Execute(IServiceProvider serviceProvider)<\/p>\n

{<\/p>\n

try<\/p>\n

{<\/p>\n

IPluginExecutionContext pluginExecutionContext = (IPluginExecutionContext)serviceProvider.GetService(typeof(IPluginExecutionContext));<\/p>\n

IOrganizationServiceFactory organizationServiceFactory = (IOrganizationServiceFactory)serviceProvider.GetService(typeof(IOrganizationServiceFactory));<\/p>\n

\/\/get the collection of price list based on your business requirement<\/p>\n

EntityCollection priceListcoll = GetPriceList(organizationService);<\/p>\n

\/\/pass the price list collection to the output parameter<\/p>\n

pluginExecutionContext.OutputParameters[“BusinessEntityCollection”] = coll;<\/p>\n

}<\/p>\n

catch (FaultException<OrganizationServiceFault> ex)<\/p>\n

{<\/p>\n

throw new InvalidPluginExecutionException(“Execute: ” + ex.Message);<\/p>\n

}<\/p>\n

}<\/p>\n

Register this plugin on GetDefaultPriceLevel<\/strong>. This will override the Price List selection on Opportunity, Quote, Order and Invoice as well.\"price<\/a><\/p>\n

Note:<\/strong> Make sure to return only a single Price List in the collection in output parameter. If you return more than one, the Price List will not be set.<\/p>\n

Conclusion:<\/strong><\/p>\n

Similar to the enhancement where the Pricing logic could be overridden using the CalculatePriceRequest<\/strong> Message, we now have the ability to select the Price List based on which the Pricing can be calculated.<\/p>\n

There\u2019s much more. For any assistance in implementation, customization, migration or upgradation of Dynamics CRM, get in touch with us on\u00a0crm@inogic.com<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction Traditionally Price List in any of the transactions like Opportunities, Quote, Orders or Invoices was set by reading it from Customer. If there was no price list set for the customer, it would be left blank and the user would be required to set it manually. Price List is critical and needs to be\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[15,23,24,42,50],"tags":[600,1361],"class_list":["post-1680","post","type-post","status-publish","format-standard","hentry","category-development","category-dynamics-crm-2015-update-1","category-dynamics-crm-2016","category-plugin","category-sales-2","tag-dynamics-crm-2015-update-1","tag-price-list-selection-in-dynamics-crm"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/1680","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=1680"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/1680\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=1680"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=1680"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=1680"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}