Please Login with your Salesforce ID to post, promote or comment.
Salesforce IdeaExchange
FAQs | Terms of Use7890 Ideas; Promoted 165896 Times; 15895 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
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.
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.
Make managed packages less restrictive / more intelligent
Making an application "managed" is a big step. Immediately several items become frozen and fixed for all time. Although many of these make sense to permit upgrades, many are unreasonably restricting and do not allow for "normal" evolution of an application over several versions.
Take one example: the text comments in a help popop on a custom object field. They can't be altered after going managed. If user feedback says that the comments aren't helpful enough - tough luck. If the use of a field changes - again tough.
This example is one where the AppExchange system could permit the developer to make the change in the package - and then all future installations of that package have the new text. Anybody that has already installed that app and customised the popup help text would keep that customisation. The change to the managed package would only affect new installs.
There are several examples of the above intelligent approach to managed package upgrades.
Another big example is to permit items to be depreciated. This includes custom objects, fields and scontrol. These would be flagged as "no longer used". Or better still, not included in new installs of the package. Like the previous example older installations would not have the depreciated item automatically removed (although they could be given to option too if they wish).
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.
Exception Reporting (outer joins)
There needs to be the ability to run exception or without reports. For example: show me all Accounts without an Opportunity. It would also be nice to include the total number of accounts in the report so % comparisons could be made. For example: of the 1000 Accounts in salesforce.com, 350 did not have Opportunities, hence 35% of all accounts are without an opportunity.
Insufficient Privileges - Tell me why
I often get messages from my users saying they can't access a certain page/object/report.
When we were 10 employees, and 2 profiles, it was easy. but once we grew, and profiles has increased, and so did everything, it may take me couple of hours to figure out what exactly is the reason for the limitation on the user.
If possible ( since the system knows exaclty which object has issued/triggered the limitation) to have that displayed on the error screen.
This will reduce the admin time wasting on looking for the solution.
Modify "Meeting Summary" email template
Meeting Summary emails is a nice idea, however the default email template contains a few "too generic" elements. Example, a picture of two businessmen and some SFDC branding items need to be optional or at least customizable.
Allow me to create public pages with access to salesforce data
If I want to develop a true Saas application, I need a welcome page, and a sign up screen, and an about screen, and I want to expose a read only view of ideas, just like salesforce.com.
Along another thread, I want to be able to put a widget on my website that shows my current job openings, as they are managed in salesforce.com.
salesforce.com's current pricing and security models do not offer the infrastructure to do this. technically, I would have to run my own web server, and hard code login information in to my page or widgets to query salesforce.com, and display it on my page.
Until then, I and other Saas app builders will be forced to use other tools like OpSource.net.
Salesforce as an Open ID provider
It would be great if Salesforce became an Open ID provider and followed the lead of AOL, Wordpress.com, etc. allowing an ID that people already have to act as an Open ID.
I'd like to suggest that Salesforce implement this, not a partner. Also, it should not be an extra fee, and should be included in every edition of Salesforce, including Developer Edition.
The benefit to Salesforce in doing this is a) media publicity and b) lots of new people will sign up for Salesforce accounts (even just DE accounts) and be exposed to the entire Force.com platform. Many of these people will probably take that new found knowledge to work and see it as an Opportunity to use Salesforce as an authentication system within their business.
Authentication on the web is becoming more and more important for people's security and convenience and I think Salesforce is in a great position to be a part of that.
Using the QUERY call to delete records!
The Delete call from within the API is ok, but when I need to delete 10,000 records or more at a time (100,000+ isn't uncommon), running a delete query would be far far far far far smarter, faster and more efficient.
try
{
$query = "DELETE FROM Opportunity WHERE Type__c='Information' AND LeadSource='Web'";
$output = $mySforceConnection->query($query);
}
catch (Exception $e)
{
print_r($e);
die;
}
All objects should be able to relate to all objects when creating a custom report type
When creating a custom report type for Activities, we can not relate it to any other object. Often an activity is related to an account or contact, and so when I create a custom report type, I should be able to choose either of these as a related object. The only way to pull activity reports with a contact right now is to use the standard report types, and there are critical limitations to only use those.
Allow any object to be related to any object when creating a custom report type.
