Most organizations start out with 1GB of storage for Salesforce CRM. This can be a challenge especially for nonprofits who would like to collect a lot of data needed to report to their funders, collect program data or consolidate multiple aspects of their business data into Salesforce. Over time the data fills up the allotted storage and puts organizations into a bind to either purge data or purchase more storage.
Over the years we have explored different solutions that can be used as preventive measures and limit the storage used. The traditional approach is to either export and archive or aggregate and purge older records. The drawback with these solutions is that you can no longer see the details of the historical data in Salesforce.
Below we describe a different preventive approach inspired from document-oriented databases that allows organizations to keep their data and not run the risk of running out of storage.
At DaizyLogik we always strive to serve our clients through a thoughtful approach in which we take the coolest solutions we develop and make then widely available to as many organizations as possible. Nonprofits work hard to make the world a better place, and they deserve to have access to these solutions in a streamlined and cost effective way. So when our consultants see patterns emerge from client requests, our team of developers transform these ideas into useful products and services. We share a few examples here.
The Salesforce Data Story
Over the years, we’ve found that many organizations want to publicly share some of the important data they collect in Salesforce on their website. The most common ways to do this come with their own set of challenges:
- Exporting a snapshot of the data from Salesforce, and hard-coding it in the website. This requires manual process and results in static website content.
- Exposing Visualforce pages through sites requires custom Salesforce development which can be expensive and difficult for web developers to style in a public website.
- Using Salesforce Communities which comes with a steep price tag.
We knew there had to be a more streamlined way to make this work. Our team wanted solutions that would not require us to reinvent the wheel every time a client asks, that does not clutter Salesforce with custom code, and that can scale to benefit multiple clients. So we built them!
If you’ve ever run into or received this error message from Salesforce you know how frustrating it can be to not know right away which flow this is referring to.
The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 301A0000000TizV. Flow error messages: <b>An unhandled fault has occurred in this flow</b>An unhandled fault has occurred while processing the flow. Please contact your system administrator for more information. Contact your administrator for help.
Here is one way to find out which flow this is referring to. Open the Developer Console and navigate to Query Editor. Type the following query, plugging in the id from the error message:
select masterlabel from flow where id = '301A..........V'
Make sure you check the “Use Tooling API” checkbox at the left bottom of the screen. Click Execute. This will return the label for the flow or process builder. Voila!
Do you have a favorite Salesforce report that provides you a wealth of data that you would like to represent visually? If your report is pulling together multiple sums and groupings, then one graphical representation will not be possible or desirable. But with a Dashboard in Salesforce Lightning, you can leverage the same report to show many aspects of your data in one place.
We used two of our favorite reports “New Donors Last Year” and “Second Year Donors”. These reports pull the list of gifts made last year by new and returning donors, grouped by donation Record Type and by donor, and count the number of donors as well as the number of donations.
We then used the two reports to create a rich Lightning Dashboard that visually displays various aspects of the data.
Each of the two reports was reused multiple times to extract and display different aspects of the data using the right visual representation in dashboard components. The New Donors Last Year is used to display the four dashboard components in the top row, while the Second Year Donors report was used to create the four components in the bottom row.
When adding a new Dashboard component in Lightning you can select the report you wish to use, the visual representation and the actual slice of data from the report.
By reusing the same report for multiple components you can avoid the proliferation of multiple versions of the same report, and you can easily call out various aspects of the data by visually representing them in a dashboard.
Fresh from the Salesforce Global Lightning Tour 2017
Our consultants attended the Salesforce Lightning Tour ’17 workshop this week and are very excited about some of the latest features in Lightning. They’re pretty awesome.
Whether you’re already using Lightning or are considering moving to Lightning, we wanted to share some of the newest highlights.