The "Create" new picklist for creating new records from the sidebar directly relates to the tabs that are visible at the top of your screen. Therefore, if you hide the "Leads" tab from a user's profile they will not see the "Lead" in the "Create New" picklist on the left hand side.
The "Create" new picklist for creating new records from the sidebar directly relates to the tabs that are visible at the top of your screen. Therefore, if you hide the "Leads" tab from a user's profile they will not see the "Lead" in the "Create New" picklist on the left hand side.
Thanks for that Tej. That's useful to know. In fact the situations is this: we have a custom object that has records added to it automatically as part of the app functionality and we have written a visualforce page to list these records but we don't want to allow users to manually add records to this custom object. The visualforce page contains a tabstyle attribute which relates the page to the custom object tab and I guess that's why this object is appearing in the Add New component.
Maybe if we create a visualforce tab, instead of using the custom object tab this might resolve our issue.... I'll try it!
The "Create" new picklist for creating new records from the sidebar directly relates to the tabs that are visible at the top of your screen. Therefore, if you hide the "Leads" tab from a user's profile they will not see the "Lead" in the "Create New" picklist on the left hand side.
All Answers
The "Create" new picklist for creating new records from the sidebar directly relates to the tabs that are visible at the top of your screen. Therefore, if you hide the "Leads" tab from a user's profile they will not see the "Lead" in the "Create New" picklist on the left hand side.
Thanks for that Tej. That's useful to know. In fact the situations is this: we have a custom object that has records added to it automatically as part of the app functionality and we have written a visualforce page to list these records but we don't want to allow users to manually add records to this custom object. The visualforce page contains a tabstyle attribute which relates the page to the custom object tab and I guess that's why this object is appearing in the Add New component.
Maybe if we create a visualforce tab, instead of using the custom object tab this might resolve our issue.... I'll try it!
Yep, that has worked. This custom object is no longer listed in the Add New component...
Thanks Tej!