5

I have a client that has had a highly customized org for a good deal of time and want to move back to much more standard pages, so they can have an internal SF admin, and no need to have someone familiar with Apex and VF. They really want a different layout for when you are adding a new contact, then when you are viewing or editing the contact. Basically, they want the add new contact screen to have a very limited amount of fields, then once the contact is created the view and edit page present the user with many more fields they can optionally update.

I have an idea on how to do this by creating a Record Type for each and using workflows to update the record type after the contact is created, but this seems pretty ugly and clunky to me.

Does anyone have a workaround for allowing different page layouts on add contact and view/edit contact using standard pages?

Improve this question
1
  • If you want to use just page layouts then using record types and workflow rules is the best way to do it.
    – Daniel Hoechst
    Jul 30, 2013 at 20:45

1 Answer 1

Reset to default
9

The answer to this question is in the question. Without record types, you have no way to change the page layout on the fly. Any editable field that is on the layout will be presented to the user, and there's no way to specify that a user doesn't have "create" access to a field but does have "update" access to the same field. Any other solution would involve code for maintenance, which is exactly what you're trying to avoid. The only other solution which is equally clunky would be to have a Visualforce page for the new record creation only, and have that page be controlled by custom settings that define the layout of the fields; this specifically means that the administrator would have to go to two different places to modify the behavior of the two pages.

Improve this answer
1
  • Thanks a lot fox. I figured there was no good way to do this without some sort of Apex or VF, but wanted to put it out there. The VF page controlled by custom settings is a very interesting workaround, but like you said, seems pretty clunky as well. Just have to tell the client this is exactly why Salesforce has VF and Apex, to allow for customization such as this. Appreciate the help.
    – Chris Duncombe
    Jul 30, 2013 at 21:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .