Please Login with your Salesforce ID to post, promote or comment.
Salesforce IdeaExchange
FAQs | Terms of Use8060 Ideas; Promoted 170158 Times; 16384 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
Drag & Drop for Calendar Events
It would be great if calendar events could be moved to another date simply by using the mouse.
INLINE EDITING IN THE CONSOLE VIEW!!!
Oh no... We just discovered that inline editing does not work in the Console view. This is extremely disappointing as all of our 90 users work the console view.
After all the hype over here we can't use it.
Receive inbound emails in salesforce
Please provide full email integration. Ideally this would be one-click integration whereby all email activity - both incoming and outgoing are linked historically to a contact record without thinking about it. These two features alone would give everyone a "true" composite of a contact, both historically how they interact or respond to email marketing campaigns sent by marketing and also giving them true history of all email interactions without cumbersome syncing or integration.
Formula limitations - length of formula and compiled size
It will be good to get rid of formula limitations.
1. The length of text that the formula can have is 1300 characters.
Due to this limitation, I had to split my formula in to two or more variables - write the first part of the formula in the 1st variable, write a 2nd variable to refer to the 1st variable and continue with the rest of the formula, etc.
2. Max size of compiled formula is 5000 character.
I think when you refer another formula in your formula, there is a limitation is the size after compilation.
3. when the same formula field is referred more than once in a formula, the compilation happens to translate the formula as many times as it's called.
Example:
Formula1_Field=IF (1<2><3>))
In this case, when Formula2_Field is compiled it translates Formula1_Field twice. In my real case, CASE statement cannot be written when you are checking for multiple expressions.
Disable E-mail option for "S-Control" Dashboard Refreshes
Due to their nature, I understand that it isn't possible for dashboards with s-controls to be e-mailed out. However, it's possible to *schedule* dashboards with S-Controls and give the expectation that you'd be able to e-mail them out.
What I'd like is if you are attempting to schedule an S-Control Dashboard, it doesn't give you the option to e-mail it out. It still makes sense to have scheduled dashboard refreshes if they have non-dashboard components, but the e-mail piece should be completely disabled to not give the appearance that you are able to e-mail them out.
Email integration with Yahoo or Gmail
How about in addition to "Outlook edition" that lets you synch with Outlook emails. How about also a "Yahoo Edition", "Hotmail Edition", "Gmail Edition"?
Obviously not all the same feature sets might be there for each of these web-based email systems but something basic like selective email synching would be nice. Maybe as an add-in that works with Firefox?
I might envision a way to "tag" yahoo emails and allow for at least an easy template to download that could be used with the SFDC data loader. This might be an idea I need to pitch onto yahoo's version of "ideas.exchange" as well.. hmm..
-a
Allow "All" to be a default forecast product family setting
Currently, while I can set "None" or a specific product family as the default Product Family setting for the forecast tab to show, I cannot set "All". I would like "All" to be a setting, so that I don't have to select "All" each time I look at the Forecast Tab.
Roll-up Summary Fields for Account - Opportunity Standard Relationship
The recently announced Winter 08 feature - Roll-up Summary Fields for Standard Objects (Opp-Opp Line in Winter 08) - is another great step forward. While this will extend the Roll-Up Summary Field functionality to work with Opportunities and their Line Items, it would be tremendously useful to extend that same functionality to the remaining standard objects and existing relationships. For example...
Example 1 [COMING IN SPRING 08]
Create a Roll-up Summary field on the Account object that calculates the SUM of all related Opportunities where Stage = "Closed/Won." This is an obvious win for organizations that wish to easily identify the value of a particular customer in terms of sold business.
Example 2 [SEPARATE IDEA POSTED]
Create a Roll-up Summary field on the Account object that calculates the COUNT of all related Cases where Type or Status = X. Use your imagination but this could be an easy way for support organizations to identify how many cases a customer has submitted versus their paid support agreement.
Example 3 [SEPARATE IDEA POSTED]
Create a Roll-up Summary field on the Account or Contact object that calculates the COUNT of all related Tasks where Type = "Call" Status = "Complete." This would allow organizations that focus on a high volume of customer interaction to easily evaluate those trends.
Advanced Validation Rule Functions
Validation rules are a really powerful way to write business logic without writing code. In Spring '08 we are introducing these new functions to make them even more powerful:
VLOOKUP Function
Similar to its Excel counterpart, the VLOOKUP function lets you use data in another object as a basis for validation. For example, to validate the zip code in a contact address, you could use the VLOOKUP function in a contact validation rule to search for a match in a custom object containing a list of valid zip codes.
ISNUMBER Function
The ISNUMBER function provides a simple way to tell if data entered in a text field only contains numbers, which is required for many types of identification numbers like credit cards and account numbers.
REGEX Function
Regular expressions are a powerful tool used by programmers to find patterns within bodies of text. The REGEX function exposes the power of regular expressions in validation rules, empowering formula authors to tackle the most demanding format validation challenges. Need to validate an IP address, country-specific phone number or VAT number format? If so, the REGEX function is for you.
Increase Name Field Widths In Force.com IDE
Increase the name field with in the IDE so that more of the name can be seen at once. Right now it only shows about 12 characters when the full length is around 50.
Outer joins as "with and without" relationships in Custom Report Types
Make it possible to have a relationship between a parent and child objects when building a Custom Report Type that allows the return of parent records when they are no child records.
This would be like a database outer join, and allow reporting when there may or may not be child records - something not possible today. Today's Custom Report Types allow only the return of a parent when there are child records. For instance, if reporting on opportunities, we want opportunity data whether or not there are products attached.
This isn't about "exception reporting" covered in:
http://ideas.salesforce.com/article/show/23676/Exception_Reporting_outer_joins
