Salesforce IdeaExchange
Stop squeezing the width on Idea Exchange images
A couple of weeks ago, wider images on Idea Exchange started getting squeezed to fit within a certain width. This practice makes many of the images unreadable on idea lists. In order to see wider images in an undistorted state, you must click through to the individual page of a particular idea, where horizontal scroll bars are included to accommodate the extra width without modifying the aspect ratio and distorting the image. Can the horizontal scroll bars be put back on the images on the main idea lists?
A crisp image attracts. A distorted image detracts. I think it's important to have images appear in their proper aspect ratio everywhere on Idea Exchange. Anyone disagree?
Separate the IdeaExchange and the BugExchange
Every time we (the users) find a bug, SF Support tells us to post an "idea" for fixing it. Bug fix requests really don't belong on the IdeaExchange. Maybe it's relevant for SF to see which bugs are "most popular" (impacting customers the most), but can we put these posts in a separate area?
When converting Leads, allow custom Object records to be converted to the Contact
When Leads are converted, allow custom object records that are related to that Lead to be converted to the Contact record (similar to the way that the standard Activity and Campaign objects are converted).
The graphic above is one way it could be done. Or it could be an option on the custom object settings. Or it could be an option on the relationship field settings.
Of course, the custom object would need to contain a Lead relationship custom field AND a Contact relationship custom field, or the "Convert custom object records" option wouldn't be available for selection.
Customizable Record Type defaults for Lead Conversion
When converting Leads, please give us the ability to define the Record Type for any new Accounts, Contacts, or Opportunities that are created. Today, records created from a Lead conversion take on the default Record Type of the User performing the Lead conversion. A more useful approach would be to allow Administrators to define a default Account, Contact, and Opportunity record Type based on the Lead Record Type.
SF Edition picklist for community discussion boards
It would be useful to know which edition of Salesforce a community member is using when reading and responding to their discussion board postings. It would help to add a picklist to the New Message screen and then display the user's selection in their posting.
Alternate error msg for validation rules that use roll-up summary fields
If a roll-up summary field is used in a validation rule, the rule will trigger on the master object or the detail object. Unfortunately, the same error message is displayed on either object. We need the ability to produce different error messages on the master object and detail object.
EXAMPLE:
Master object: Opportunity
Detail object: Required Documents
Roll-up Summary field on Opportunity
Field Name - "Docs Required"
Criteria - Count # of required documents where "Status" is not "Signed Copy Received"
Validation Rule on Opportunity:
Criteria - "Stage" = Closed/Won and "Docs Required" >0
Error - "This Opportunity can not be closed because there are one or more required documents that do not have a status of 'Signed Copy Received' "
Unfortunately, this same error message would appear in the Required Document record if the "Status" field was changed to an offending value after the Opportunity was closed. Ideally, the user should receive an error message that is relevant to the object being edited. In other words, the user would receive the error above if triggered from an Opportunity record, but if triggered from a "Required Document" record, the error should be "Required Document records on a Closed Opportunity must have a status of 'Signed Copy Received' "
Exclude report footer when using Export Details to Excel
In reporting, when using the "Export Details to Excel" function, the generated report always contains a multi-line report footer. This footer is useful when reviewing reports in Excel, but it causes issues when you use that Excel file as an import file for another application.
How about a checkbox on the Export screen that you can select to "Exclude report footer"?
Control available picklist values based on the Role or Profile of the logged-in User
A useful feature would be to have the ability to control available picklist values based on the Role or Profile of the logged-in user. For example, a manager might need more values in a picklist than a subordinate.
"Run Assignment Rules" as an option in Workflow Actions
Sometimes when a Lead or Case is updated, it needs to be re-assigned using the criteria in the Assignment Rules. It would be nice if "Run Assignment Rules" was an option in Workflow Actions.
Example: Lead is initially missing an address and is assigned to a "No Territory" Lead Queue. A month later the prospect completes a web-to-lead form with his Nevada address and the Lead address is updated in SF. The territory is now "Western US" but the Lead still sits there in the "No Territory" Lead Queue. I can write a Workflow Rule that recognizes the update, but there's no trigger that will run the Assignment Rules again. To do this today, I have to write a separate Workflow Rule for each Assignment Rule entry that I have.
Add Fwd/Back navigation buttons in Help and Training
The Salesforce Help and Training window is displayed without the browser’s address toolbar. Unfortunately, in IE7, Microsoft decided to put the "forward" and "back" browser navigation buttons in the address bar. As a result, navigation in the Salesforce Help and Training window is a bit more cumbersome (we must use either a right mouse click and context menu selection, or a custom mouse button, or an alt-left keyboard shortcut).
Please add fwd/back navigation buttons in Help and Training OR display the Help and Training window with the address bar.
POST IDEA