Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am building a CPQ type tool. So the User can configure the Products they need via some Custom VF page. Then when they have done this I want to direct them to the standard Opportunity Edit page which they are familiar with. I dont want to re-create this in VF. The standard edit page will allow them to Save. Obviously if I direct them to the standard Edit page I will lose the Product configuration as this is stored in a Custom Controller [RAM] and not yet written to the DB.


share|improve this question
You could create a 'shell' of an opportunity, so with blank / dummy fields before creating line items, attach them to the oppty and open that opportunity in edit mode, so /006/e?id=OppId on save of your CPQ Controller? – techtrekker Feb 15 '13 at 9:26

The best way to address this is to go ahead and create the opportunity for the user when they finish building out the products in your CPQ tool and then redirect them to the edit page for that opportunity. The one downside to this approach is that if a user cancels at that point the expected behavior would be for no records to be saved.

I've not done your specific scenario, but I have done this in the past to do complex value defaulting above and beyond what you can accomplish by passing variables into the standard new record page. Users haven't reported any issues with this approach.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.