In this webinar, our experts showcase a variety of demo use cases of how different components of the...
One of the great features of Microsoft Dynamics CRM 2011 is the role based form or the ability to create multiple forms for the same entity and exposing them based on a user's security role. Today, we'll discuss a neat best practice that may often be ignored during CRM implementations -- labeling CRM 2011 forms.
If you open any out of box CRM entity, you will find two forms available by default as shown below:
Now when you add a new form and do not name it, it will get added as a New Form, if you do not rename it and just save it in CRM (as shown below):
The above form may not be very meaningful for an end user using the application.
Instead you can do the following for labeling CRM 2011 forms:
It's easy, it's simple and can add good flavor to your CRM implementation.
Happy CRM'ing!
You are right that your new form needs a sensible name to allow users to choose between them. I tend to do this slightly differently though, and for new forms and views I tend to follow these steps:
open the form / view which is closest to what I want to get, to save time (a brand new form will always be a clone of the current default which may not be the best starting point unless you only have one so far)
save as - give it a name
it is now saved and has the new name
make changes (make sure you wait for the save to complete and the page to reload otherwise you are changing the original one still!)
don't forget to publish!
Alternatively build, then save:
hit "new"
edit your new form
go to Form (or View) Properties > display
put in the name you want there
save (and it is automatically published as all components are published on first save)
Mentally, I think of Save As to mean "keep this one and make another copy" so it would not occur to me to do "save as" on a new form as that would seem like I am getting a second new one, although I am not since it is not yet saved. It just feels wrong somehow.