Please Login with your Salesforce ID to post, promote or comment.
Salesforce IdeaExchange
FAQs | Terms of Use7409 Ideas; Promoted 154857 Times; 14441 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
Coming in Summer 08 Ideas
Subscribe
Cross-Object Formula Fields: Be able to insert related Object data into a formula field
Like: Get the Account name in a contact formula field.
Adjustable column widths
The ability to quickly click and drag to adjust the column widths in views and reports (like in Excel). Should be able to save these view preferences so that you don't have to re-adjust it every time.
Allow in-line editing for views
Please enable in-line editing for views similar to forms. This would be incredibly useful when you need to quickly edit data in a list view instead of going to each individual record.
Filter on Lookup
I would like to filter lookup view to restrict records return based on some condition.
Example: On opportunity screen, we have Accounts as lookup. When you click on lookup it displays all the types of accounts (Like OEM / Parent / Customer / Partner etc ...) I would like to filter this result set to show only "Parent" type. Condition may change based on the screen where lookup is implemented
Delete button for Views
It would be nice to have a delete button next to the Edit and Create New View buttons so you don't have to go back into the edit mode of the view to delete it.
Public Tagging
The Public Tagging feature would allow users to create tags that everyone in the org could view and associate to records. A public tag would be applied by any user in the org to a record only once. Once that public tag has been applied to the record, everyone that has read access to a record would be able to view the public tag on it, and everyone in the org could search for that public tag and see it in the tag home page. The more records a tag is associated with, the larger it's usage number.
Additional management features would include:
“Tag Creator” user permissions: Only users with a special permission would be allowed to create public tags, ensuring good quality and manageable numbers of public tags.
“Tag Administrator” user permissions: Only users with a special tag administrator permission would be able to edit or delete public tags once they have been created, so that all most users in the org could not accidentally or maliciously change or remove public tags that are in use.
Restricted removal of public tags: Only users with the proper permissions can add or remove a public tag from a record – for example, only the record owner or the person who applied a public tag to a record may remove it. This would help ensure that experts on the data can control the public tags on their records.
Auto-complete for Lookups on Recently Used Records
When editing a Lookup field on a record, you would see record names from your cache of recently viewed records for that object that match the string you started typing into the Lookup field.
For example, if you are editing a Contact Lookup field and you start typing "john", all the Contact records that you have recently viewed or edited that begin with the name John would appear in a menu for you to select from.
If the record you want is not available in the auto-complete menu, you can still use the Lookup function to do a more in-depth search to find the record you're looking for.
Many to Many Relationships w/ Linking Object
Problem: If you would like to create a “Many to Many” relationship between objects you must create a linking object in the middle. The linking object can contain more then the ID fields, but primarily contains the IDs of the objects that it is linking. This poses a HUGE problem with reports, related lists, etc, even with report types. There is no way to show or report on the Many to Many relationships. You can only report on one of the primary objects and the linking object. Without de-normalizing the data and saving fields to the linking object reports are very limited.
One Current Solution: To overcome this we have had to de-normalize the data model. We take fields from both primary objects and replicate them on the linking object creating a composite object. This has to be done with APEX, AJAX or some code external to Salesforce. It is very cumbersome to code this type of solution and challenging to ensure data integrity when one of the primary objects data changes. Also, if future reporting requirements change we have to code, not configure, a solution.
One Proposed solution: Create a field type called link or “Many to Many”. Under the covers Salesforce could create the linking object storing the IDs from the two primary objects. Then Salesforce could expose this in reports, related lists, etc. Since Salesforce created the linking object the system would have more control over the data model and create the composite view.
Thanks,
Todd Bursey
Appirio
Multiple Business Hours
Salesforce currently allows you to enter "business hours" into the system for use with case assignment rules. Because of the number of different departments and reporting done out of SFDC, we would like to see three new features:
1. The ability to have multiple sets of business hours. No two of our teams have the same SLA and/or hours of operation. It would be great if SFDC could account for that (possible through the user's role and/or profile?)
2. The ability to calculate queue turn around time based on multiple business hours and a particular SLA for a queue.
3. The addition of holidays to business hour calcs.
Approval Process: For Manually Chosen, Ability to Choose Pool of Approvers
In the Approval Process you have a few choices, use a "Direct Manager" field, or "Manually Choose", or use a queue. Direct Manager can be too restrictive since it's one person. "Mannually Choose" is too loose in that it allows the person to choose ANYONE within the organization. I say at each approval step, you can define who the appropriate approvers can be. Also the ability to choose more than one approver if a step requires say 3 people to approve it.
Add number of pages to search result
I would like to be able to see how many results and/or how many pages with results are generated with a View or with a Search.
Currently the users can only see that there are more than one page with search results (because of the <previous /> links), but there is no indication of how many results and/or how many pages there are.
This would be most helpful.
Increase # of rows returned in a Lookup
When doing a lookup on Accounts, I sometimes need to see more than 50 rows to find the specific Account that I am looking for. The number of rows returned on a lookup should be increased and then the "Next Page" links should be added to the bottom allowing one to search through all valid results.
Subscribe
POST IDEA
TOP USERS