welcome to XRM blog

Keep in touch with latest CRM/ERP articles

To remain competitive your organisation must be efficient across the business process spectrum. To do so you need to take sound decisions based on a balance between the cost and risk. To do so you will be heavily dependent on your content management in itself needs...

image
Blog

Close related Quotes on Opportunity Lose

By Ami Atishay on 11/17/2016

Closing related Quotes on Opportunity lose seems pretty straightforward. But is it really so? 

Thought it would be pretty simple until I landed into handling it using code for one of our clients. One of our clients had requested a functionality that can automatically Close all related Quotes when the Opportunity is marked as Lost. Easiest way to do this was through plugin. So, I instantly started writing a plugin to implement this feature. 

On Lose, the plugin would fire and would retrieve all the Quotes related to the Opportunity using FetchXml and store as an Entity Collection. For every quote, I tried to set the state of the Quote to canceled using SetStateRequest class. Refer to the code below: 

SetStateRequest setStateRequest = new SetStateRequest()

            {

                EntityMoniker = new EntityReference

                {

                    Id = quote.Id,

                    LogicalName = "quote",

                },

                State = new OptionSetValue(3), //Set state to Closed

                Status = new OptionSetValue(6) //Set status to Canceled

            };

            service.Execute(setStateRequest);

        }

Well, all above code seemed perfect but alas, this did not work. The code threw an exception when it tried to set the status of the Quote to closed. This happened because closing of Quotes involves an intermediate entity name Quote Close. This Quote Close (schema name: QuoteClose) entity records are generated when a quote is closed. 

For closing a Quote, we need to use CloseQuoteRequest class. The code is given below: 

private static void CloseQuote(IOrganizationService service, Entity quote)

{

            CloseQuoteRequest req = new CloseQuoteRequest();

            Entity quoteClose = new Entity("quoteclose");

            quoteClose.Attributes.Add("quoteid", new EntityReference("quote", quote.Id));

            quoteClose.Attributes.Add("subject", "Opportunity Lost");

            req.QuoteClose = quoteClose;

            req.RequestName = "CloseQuote";

            OptionSetValue optVal = new OptionSetValue();

            optVal.Value = 6;

            req.Status = optVal;

            CloseQuoteResponse resp = (CloseQuoteResponse)service.Execute(req);

}

But there is still a catch here. This code work perfectly for Active Quotes, but since the Quotes in the Draft mode cannot be closed directly, we will have to first activate the Quotes that are in Draft mode then only we can Close them. Quotes can be easily activated using the SetStateRequest class. So, now first we need to check if the current Quote is in Active or Draft mode and then proceed accordingly. If the Quote is in Draft mode we will have to Activate them and then Close them. Below is the code to Activate any Quote: 

private static void ActivateQuote(IOrganizationService service, Entity quote)

        {

            SetStateRequest setStateRequest = new SetStateRequest()

            {

                EntityMoniker = new EntityReference

                {

                    Id = quote.Id,

                    LogicalName = "quote",

                },

                State = new OptionSetValue(1), //Set state to Active

                Status = new OptionSetValue(2) //Set status to In Progress

            };

            service.Execute(setStateRequest);

        } 

Registering the step:

Message: Lose

Primary Entity: opportunity

Event: Post-operation

Execution Mode: Synchronous 

I hope you found this blog helpful as I struggled a lot to implement this easy sounding requirement, so just thought of sharing with you all.

Dynamics CRM
MS CRM 2016
Close Quote
Opportunity
Author
Blog Calendar
Blog Calendar List
2022 Dec  20  3
2022 Nov  209  2
2022 Sep  11  1
2022 Aug  46  4
2022 Jun  7  2
2022 May  3  2
2022 Apr  4  2
2022 Mar  1  1
2022 Feb  2  1
2022 Jan  1  1
2021 Dec  3  1
2021 Nov  2  1
2021 Oct  1  1
2021 Sep  10  1
2021 Aug  35  5
2021 Jul  34  4
2021 Jun  521  5
2021 May  25  3
2021 Apr  917  3
2021 Mar  89  5
2021 Feb  1037  7
2021 Jan  1147  9
2020 Dec  284  7
2020 Sep  61  3
2020 Aug  388  3
2020 Jul  90  1
2020 Jun  55  3
2020 Apr  38  3
2020 Mar  11  2
2020 Feb  26  5
2020 Jan  33  7
2019 Dec  17  4
2019 Nov  12  1
2019 Jan  23  2
2018 Dec  39  4
2018 Nov  68  3
2018 Oct  18  3
2018 Sep  833  11
2018 Aug  6  2
2018 Jun  11  1
2018 Jan  68  2
2017 Sep  576  5
2017 Aug  17  1
2017 Jul  17  2
2017 Jun  59  2
2017 May  21  1
2017 Apr  35  2
2017 Mar  120  4
2017 Feb  603  4
2016 Dec  192  3
2016 Nov  551  8
2016 Oct  278  10
2016 Sep  459  6
2016 Aug  39  1
2016 Jun  1829  6
2016 May  108  3
2016 Jan  71  2
2015 Dec  405  6
2015 Nov  4  1
2015 Oct  13  1
2015 Sep  1417  6
2015 Aug  14  1
2015 Jul  127  2
2015 Jun  10  1
2015 May  20  1
2015 Apr  30  3
2015 Mar  80  3
2015 Jan  5316  4
2014 Dec  17  1
2014 Nov  2252  4
2014 Oct  67  1
2014 Sep  106  2
2014 Aug  5125  1
2014 Jul  48  2
2014 Apr  2518  12
2014 Mar  282  17
2014 Feb  218  6
2014 Jan  1510  16
2013 Dec  21  2
2013 Nov  684  2
2013 Oct  256  3
2013 Sep  11  1
2013 Aug  40  3
2013 Jul  213  1
2013 Apr  56  6
2013 Mar  2145  10
2013 Feb  123  3
2013 Jan  288  2
2012 Nov  54  2
2012 Oct  490  10
Tag Cloud
Interested in our services? Still not sure about project details? get a quote