[SalesForce] How to use the same Visualforce page to override view, new, and edit buttons on custom object

I have a custom Visualforce page for a custom object. I have overriden the new, edit, and view buttons to point to this page. I would like to dynamically change the look of the page based on what mode the user is in.

For example, show an <apex:inputField /> when they are editing, but an <apex:outputField /> when viewing:

<apex:outputField value="{!MyCustomObject__c.Field1}" rendered="{!pageMode == 'view'}" />
<apex:inputField value="{!MyCustomObject__c.Field1}" rendered="{!pageMode == 'edit'}" />

I would also use this property to set the mode attribute of my <apex:pageBlock />

Is there a good way to do this using a button override? I do not want to create custom buttons and use URL parameters if I can avoid it.

Best Answer

This will lead to a lot of conditionally rendered tags. You might consider having separate page for "view" and separate for "new/edit" but use same controller extension if you really want.

But if you're determined... You can look at the URL that was used to navigate to your page and combine it with presence of Id in the standard controller.

I've called my page override and used Opportunity as the test object.

New: /apex/override?retURL=%2F006%2Fo&save_new=1&sfdc.override=1
View: /apex/override?id=0067000000AH3ME&sfdc.override=1
Edit: /apex/override?id=0067000000AH3ME&retURL=%2F006%3Ffcf%3D00B70000005pFQv%26rolodexIndex%3D-1%26page%3D1&sfdc.override=1

Something like this should work, at least until SF decides to rename/remove the retUrl param (unlikely I'd say... Especially than on viewing there's rarely something to cancel or "on success return to... where?").

public MyExtension(ApexPages.StandardController ctrl){
    Id i = ctrl.getId();
    Map<String,String> parameters = ApexPages.currentPage().parameters();
    if(i == null){
        System.debug('new');
    } else if(parameters.contains('retUrl')){
        System.debug('edit');
    } else {
        System.debug('view');
    }
}

Related Solutions

[SalesForce] onchange with Outputfield and inline editing

You can use jQuery to select the input that would eventually get submitted with the form and attach a change event handler to it. Every time that input changes the event handler would execute and you could display your lightbox from there. Depending on the location of your elements you may need to change the jQuery selector and/or placement of the wrapperClass styleClass in the code.

The following shows how it would work with an apex:pageBlockSectionItem (used that to preserve the formatting of a pageBlockSection), but you could use a different apex component, div, etc., as needed.

<apex:page standardController="Account">
  <script src="//ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>

  <script type="text/javascript">
      var $j = jQuery.noConflict();
      $j(document).ready(function() {
          $j('.wrapperClass :hidden').change(function(e) {
              alert('Hidden input was changed');
          });
      });  
  </script>

  <apex:form >
      <apex:pageBlock >
          <apex:inlineEditSupport >
              <apex:pageBlockSection title="Account Fields">
                  <apex:pageBlockSectionItem dataStyleClass="wrapperClass">
                      <apex:outputLabel value="Account Name"/>
                      <apex:outputField value="{!Account.Name}"/>
                  </apex:pageBlockSectionItem>
              </apex:pageBlockSection>
          </apex:inlineEditSupport>
      </apex:pageBlock>
  </apex:form>
</apex:page>

[SalesForce] How to override the Record Type selector and still use the standard “new” page

To avoid the spurious save, you can add RecordType and nooverride parameters to the '/006/e' URL. See my blog post here for a related but slightly different use case that includes some code. This assumes all you are passing from your custom page to the normal page is the selected record type.

You simply add this to your PageReference: pageReference.getParameters().put('nooverride', '1');

Best Answer

Related Solutions

[SalesForce] onchange with Outputfield and inline editing

[SalesForce] How to override the Record Type selector and still use the standard “new” page

Related Topic