20 Ideas to Vote for on the IdeaExchange
- In the past, we’ve had many cases where we’ve run into limitations that called for more than 3 conditional highlighting fields. With this new capability, we would have the ability to create a matrix of more than 3 fields, which would allow for more flexibility.
- It would be great if there was a way to load multiple tables of data in a single load rather than loading each individual table one at a time. The problem with this is that the data needs to have a unique key already in Salesforce, and this is why you have to load it one table at a time. However, if it were possible to relate data using import keys, it would make data migration much faster.
- This is a no-brainer. Being limited to only 20 buckets in reports seems silly. With more than 20 buckets, you can group data in more granular ways. However, if you do have to bucket with more than 20, it would be worth noting that you should look at your data structure to see if you can consolidate fields and values because more buckets may not be the solution; the solution might be a better data structure.
- Campaign tracking can get tricky when you have multiple campaigns. You can enforce campaign tracking accuracy with validation rules, but with this idea of automatic campaign assignment options, you could be able to capture it in a single step instantly.
- In some situations, when a record is deleted, it would be helpful to trigger a process builder flow or a workflow rule. For instance, one of our clients needed to update a related record once the child record was deleted. We had to build an Apex trigger to accommodate this. However, if we could solve this with a declarative solution on a delete DML, it would be more efficient and much easier to accomplish.
- We believe that this is a great idea because it bridges reports and list views together. On the other hand, this idea may be more appropriate for Lightning Experience because Salesforce is continually evolving the Lightning Experience platform, and Classic is not getting the development resources we are hoping for. However, this idea should still be considered.
- While Lightning Experience is still new and continuously flourishing, this is one idea that should be on the next release to accommodate sales needs.
- This is helpful if you have a lot of calculations and want to summarize them across objects. The work-around is particularly difficult for this, but with this new idea of adding up formula fields, it will simplify many configurations.
- This would be an awesome tool, especially for admins because they wouldn’t have to utilize various combinations of validation tools, record types, and page layouts. With an intermediate hybrid tool, such as rules within a page layout, it will help admins better tailor Salesforce to their organization.
- This is already considered for the future road map, but this idea is still applicable if you’re using process builder.
- Cross object rollups, as this idea implies, are the perfect solution for rolling up data in Salesforce. Currently, there are 2 work-around solutions available that we recommend: one of them is Rollup Helper and the other is Declarative Lookup Rollup Summaries Tool.
- This idea is considered for the future roadmap, so you should continue to vote on it. Overall, this concept would especially help admins who have to do rollups that contain a lot of data and/or different types of data. Currently, as mentioned above, you can use the 2 work-around solutions, the Rollup Helper and the Declarative Lookup Rollup Summaries Tool as alternatives.
- When sending email templates to contacts, it would be beneficial to be able to track activity history, so we have a record of it for future conversations. Ultimately, this idea is necessary in order to provide consistent, efficient communication with contacts.
- With Lightning Experience, Javascript is not supported. It’s currently under product management team review, so we recommend that you continue to vote on this idea and comment your specific use cases to help the product management team with delivering this feature.
- Inline editing is crucial for functionality. Simply put, Lightning UI needs this feature for the constantly modernizing CRM tool period.
- This idea is considered for the future roadmap as well, so keep voting. The distinct/unique record feature would be great for having only one instance of a record within a report, rather than multiple. This is a basic functionality that’s needed in many situations, for example: showing contacts that have at least one meeting or call activity, when it just shows the contacts rather than showing each combination of contact and activity. There are workarounds with using cross filters and the Power of One tool.
- It would be advantageous to know who has run a report and the number of times it has be run in order to differentiate between manual and automated runs. Also, this idea would help to better understand if a report is being used at all.
- Having only one field when sorting from related lists is very limiting. The capability of sorting by more than one field would allow for better organization and efficiency in data.
- It’s very important for contacts to know when the account owner changes, so they know who is in charge of their account and who to reach out to. An automated update would help relieve this uncertainty and would allow for more reliable communication between partners.
- This idea seems like an easy fix, and would be especially valuable to nonprofits for monitoring the effectiveness of marketing campaigns. The application has become particularly apparent to us given that half of our clients are nonprofits.
With the rapid evolution of technology, Salesforce solutions are ever-changing and improving features. Contact our team for up-to-date information.
About the Author: Redpath Team
Our team at Redpath is a unique group of talented professionals who are passionate about leveraging Salesforce to help businesses simplify, accelerate, and transform what’s possible for their future.
