Please Login with your Salesforce ID to post, promote or comment.
Salesforce IdeaExchange
FAQs | Terms of Use8282 Ideas; Promoted 177409 Times; 17086 Comments.
- Suggest a New Product Concept
- Promote Ideas That You Want to See Developed
- Discuss With Product Managers and Other Users
- See What We Are Planning To Deliver
Allow dashboard components to show Grand Totals
Dashboard components based on Summary Reports should show a "Grand Total" row, just like the source reports do. It's a burden to users to have to drill down into the report (or open Calculator) just to get a total value.
Universal Picklists
Universal picklists that could be used and maintained across account, lead, opp, contact etc. objects.
Maintaining a dependent picklist that has several hundred values is time consuming - needless to say maintaining same list manually in 4 places is frustrating and not near robust.
Build Email Template - Send Yourself a TEST Email
When I build an email template, I have to open a new screen, pick a sample lead and send myself a test mail template to make sure the formatting is correct and it looks ok.
Salesforce should include a button on the template that says, "Send Test Message" just so you can see how the mail will turn out.
Multiple Master-Detail relationships
It doesn't seem to be possible to create a chain of master-detail relationships, like this:
House -> Key Set -> Key
Using this example, I can create a master-detail relationship between House and Key Set. But I cannot then create one between Key Set and Key, as the Key Set object doesn't appear on the drop-down menu when I try to add a master-detail field on the Key object.
This means:
- I can't use roll-up summary fields on Key Set
- If I delete a Key Set, the Key objects under it won't be deleted
Please make it possible to chain master-detail relationships.
Dependent page layouts - Dynamically show, hide, or make fields/sections required on a page based on data rules
There are times when it would be ideal to show different fields or sections on a page based on field data. For example, if a field for "software interest" is selected on a lead page, it would be nice if a section and/or fields related to capturing more information on "Software" is displayed. If the field is not selected, then this section and/or fields remain hidden.
Allowing greater customization on the page level based on data rules would make for more manageable and targeted page layouts.
Scheduled emailing of reports
I'd like SFDC to be able to email Printable View reports on a scheduled basis. For example, instead of our CEO needing to log into SFDC (and needing to pay for a license), I could simply have the system send him daily or weekly reports via email. The reports would be in the existing Printable View format. Otherwise, we have people who spend an inordinate amount of time simply running and sending reports to various managers and executives each week.
Dupe Alerts
Automatically give warning message when you are entering a duplicate account or contact
Need warning when user is about to navigate away from page without saving changes they made during Inline Editing
The Inline Editing feature in Winter'08 release is a great tool, and my users love it! One complaint, however, is that there is no warning to the user if they're about to navigate away from the page before saving their changes.
This most often comes up if they've made a number of changes to an object via inline editing, and then try to change the owner of the object BEFORE saving the changes that they've made to the inline editor. When this happens, they can't even hit the "Back" arrow in the browser -- all the changes are gone.
Please provide a pop-up / warning to a user if they are about to navigate away from an object in which they have made inline editing changes (preserving the changes, and giving the user a chance to save those before leaving the page).
Mark Reports with the Report Type that Created it
With so many Standard and Custom Report Types it can be extremely difficult to teach users how to "fish" and create reports for themselves. Have you ever tried troubleshooting a report someone has handed you when you have no idea which report type they started with? Let's make it simple and put the name of the report type somewhere in the report wizard, or at the very least on each report.
Yeah, I know, you could just send the example report to everyone and their Uncles, letting them deal with it. But really, wouldn't it be better to let them see the report type and say, "Okay, so THIS report type ain't got the fields I need."
Blank spaces in Page Layout
A number of times I have been requested to line up fields horizontally with each other. This can only be done if there are fields above the desired horizontal line up. I propose that SFDC make blank fields available to be added to page layouts so that the placement of fields is more flexible.
I think the picture explains what I want better than I could in words.
Cross Object Workflow
Do not hard code the Object (see above image) when creating Workflow Field Updates. Allow administrators to choose a field to pass based on a relationship (lookup or master detail). For example, a Workflow Rule based on Case would be allowed to have a Workflow Field Update change a Contact field for the Contact record associated with the Case.
