This is beautiful, man. Well done. I actually built this thing out as you suggested but then realized the managed package is a much more robust version.
Yes this is possible, you would want to display the line items in a screen flow, then select which line items. From there take the line items and add to the new quote.
Would love this clone feature but with ability to choose account or opportunity before saving. Often times we need to duplicate a quote or create a template for regular standard quotes for different customers.
That variable "QuoteId From Create Quote" appears out of nowhere at 11:18, and it looks like there's a jump in your video at that same time. This is the exact thing that's stumping me. How do you reference the ID of a record that you're creating within the same flow?
This is wonderful!! I am slightly stuck though and not sure what to do now. I followed the tutorial well, and am NOT a programmer at all so luckily got VSCode installed properly and deployed the LWC, but then in the end trying to add it to the End Screen element doesn't work because I do not see it in the Custom section of my components. I'm confused because I thought I followed everything correctly but must have missed something. Help?
I would check to confirm that the xml for the LWC is configured correctly. This is how the visibility is controlled. I would also refresh the flow builder, because the component will not show otherwise.
At 26:24 I'm not sure why you assigned the variable pbe_size to the Quote Line Items Collection instead of the Inactive PriceBook Entry Collection! The decision element is now dependent on the Quote Line Items, disregarding the Inactive PriceBook Entries.
hello bro, im stuck i want to clone accounts and their related contacts, cases and opportunities but i dont know how to manage teh decisions because the flow becomes very big cause i have to check if i should clone each one after each outcome of decision, can you help me with that?
You should write out the workflow of what should happen outside of flow to simplify some of the logic. Additionally, you can use sub flows to condense the logic of processes e.g. clone cases of an account is a sub flow that has an input of the account, and a list of cases.
Interested in the managed package? www.1sync.co/quote-clone-sign-up
Article by Sebastiano: javascript.plainenglish.io/how-to-open-a-record-page-from-salesforce-flow-using-lwc-a8a94bc0c9ba
Source code: github.com/jawills/Quote-Clone-Flow
Write up: www.1sync.co/clone-quotes-with-flow
This is beautiful, man. Well done. I actually built this thing out as you suggested but then realized the managed package is a much more robust version.
Glad you enjoyed! The managed package has features seen in part 2!
very simple on the Quote Line Item connections - thank you!
You're a genius. This saved me so much time.😀🙏
Glad you enjoyed!
Thank you very much @JustinWills for this excellent tutorial. I was able to solve a very important task I had.
Thank you!
Great work greatly appreciated.
Finally I am able to create the flow to clone quote with its line items. Thank you Justin. can we give option here which line items we want to clone.
Yes this is possible, you would want to display the line items in a screen flow, then select which line items. From there take the line items and add to the new quote.
@@JustinWills can you make a small video just for this part.That would be really helpful.
@@nisha3nov I may be able to do so
@@JustinWills Thank you Justin
@@JustinWills Justin can you please help me on this. Its one of the use case I am working on.
Would love this clone feature but with ability to choose account or opportunity before saving. Often times we need to duplicate a quote or create a template for regular standard quotes for different customers.
This can be accomplished using a screen flow and selecting the opportunity before creating the record.
That variable "QuoteId From Create Quote" appears out of nowhere at 11:18, and it looks like there's a jump in your video at that same time. This is the exact thing that's stumping me. How do you reference the ID of a record that you're creating within the same flow?
You save the create a record element which allows you to reference this.
This is wonderful!! I am slightly stuck though and not sure what to do now. I followed the tutorial well, and am NOT a programmer at all so luckily got VSCode installed properly and deployed the LWC, but then in the end trying to add it to the End Screen element doesn't work because I do not see it in the Custom section of my components. I'm confused because I thought I followed everything correctly but must have missed something. Help?
I would check to confirm that the xml for the LWC is configured correctly. This is how the visibility is controlled.
I would also refresh the flow builder, because the component will not show otherwise.
@@JustinWills From what I can tell, the XML is correct because I copied it over and I've refreshed the flow builder a few times. I'm stumped!
@@stephenross5786 If you use the links in the pinned comment, you can use the flow prebuilt.
@@stephenross5786 Had the same challenge, solved it by using Save All under File on the VSC.
At 26:24 I'm not sure why you assigned the variable pbe_size to the Quote Line Items Collection instead of the Inactive PriceBook Entry Collection! The decision element is now dependent on the Quote Line Items, disregarding the Inactive PriceBook Entries.
hello bro, im stuck i want to clone accounts and their related contacts, cases and opportunities but i dont know how to manage teh decisions because the flow becomes very big cause i have to check if i should clone each one after each outcome of decision, can you help me with that?
You should write out the workflow of what should happen outside of flow to simplify some of the logic.
Additionally, you can use sub flows to condense the logic of processes e.g. clone cases of an account is a sub flow that has an input of the account, and a list of cases.