Addressing Salesforce CRM Storage Limitations – A Document-Oriented Database Inspired Approach

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.

Updating and Automating Business Processes Through Salesforce NPSP

Washington Defender Association (WDA) engaged DaizyLogik to assist with efforts to update and automate their business processes while moving to Salesforce CRM. This effort was done in concert with WDA’s initiative to redesign their outdated website and ensured a much needed integration between the two systems. WDA is a membership organization whose clients include attorneys and their staffs, all of whom expect an easy-to-use interface, a high level of access, and an equally high level of privacy to protect sensitive data.

WDA’s outdated database in Access was isolated and cumbersome to maintain. The team wanted a more flexible cloud-based solution that would give them the opportunity to integrate with the new website and enable data to flow directly into their database.

Read how the DaizyLogik team addressed this challenge.

Business Processes Change. Your Salesforce CRM Should Change With Them.

Does your Salesforce CRM feel disconnected from your business processes? Do you feel like you have to use Salesforce because is telling you to, but you end up reverting to spreadsheets and sticky notes?

As Salesforce has been gaining momentum in the nonprofit community, many nonprofits adopt and implement the powerful CRM to manage their donor engagement and programs. Through our work with nonprofits at various stages in their journey with Salesforce, we have found that while their business processes may change and evolve to meet new demands, their CRM doesn’t always keep up.

Fortunately, there are a few telltale signs that indicate that an organization is using a CRM that no longer supports their business processes. If you see your staff seeking out alternatives to Salesforce, it may be time to schedule a business process review.

Share your Salesforce Data with Your Constituents

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!

Which flow would that be?

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!

One Report, Many Dashboard Components

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.

LightningDashboardBlog

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. LightningDashboardComponent2

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.

The Power of a Phased Approach: Implementing the Nonprofit Success Pack in an Existing Salesforce Instance

PATH hired DaizyLogik to help them improve user buy-in within the Global Engagement division and incorporate Salesforce as a true CRM for the department.

This case study offers insights into how the DaizyLogik team led the effort to implement the Nonprofit Success Pack (NPSP) on an existing Salesforce database for PATH by using a phased approach.

This body of work started with the output from the CRM planning phase, which we discussed in Part 1 of this Case Study (Understand Your Stakeholders: A Case Study in Agile Salesforce CRM Planning). This work included over 900 user stories that were groomed and prioritized, an existing Salesforce instance with approximately 700 active users, 1.5GB of data to be migrated from DonorPerfect into NPSP, and integration with external applications such as DonorSearch and SoapBox Engage.

Recognizing the scale of this project, our team started by defining a few phases of implementation, each with its own theme and set of goals.

Read the full case study here.

Are You Recruiting a Salesforce Consultant or a Roofer?

When recruiting a Salesforce CRM consultant, it’s very tempting for project managers in organizations to equate this individual with the contractors they’ve hired to do other jobs, such as installing a new roof. After all, both the Salesforce consultant and the roofer require a very specific skill set to do their jobs well, take on a certain set of risks, and probably cost more than one might originally expect.

Salesforce consultants know the feeling all too well that their bids and proposals are reviewed as if they were simply quotes for a new roof. And it sounds fair on the surface, if you believe that Salesforce consulting equals a one-off home repair project.

If you’re in the shoes of an organization evaluating a consulting proposal for your Salesforce CRM and find yourself struggling with the question of how to evaluate consultants, consider the following points.

Understand Your Stakeholders: A Case Study in Agile Salesforce CRM Planning

To improve user buy-in within the Global Engagement division and incorporate Salesforce as a true CRM for the department, PATH hired DaizyLogik to help them facilitate this process.

Over the course of six months, the DaizyLogik team joined members of PATH’s GE division for over 46 discussions to define use cases and identify process-related requirements and business rules, collecting over 900 user stories. Our team provided guidance on process improvements while effectively communicating Salesforce and Nonprofit Success Pack functionality, evaluated data migration needs, and prepared an implementation plan.

This Case Study provides insights into how DaizyLogik applied our consulting and project delivery methodology to a cross-organizational, complex Salesforce and Nonprofit Success Pack implementation. It also discusses the questions and challenges faced by core members of the PATH and DaizyLogik teams during this extensive requirements collection process. We describe our approach and share some key takeaways that we hope others will find useful.

Read the case study here.

The Drag-n-Drop Calendar: Interactive, Real-Time Event Management

EarthCorps coordinates 850 volunteer events, field projects, and workshops each year, and they must frequently update event details, dates, and teams as circumstances change. The process of updating the details for each event involved a number of time consuming steps.

This process was not particularly easy and team members complained that it took too much time. On top of that, users did not have a visual to reference while they were making changes to the calendar, which made it more difficult to keep track of things.

EarthCorps leadership wanted to make it easier for project teams to make updates to their events. They wanted to be able to take the visual image of an event on the Calendar and simply drag it to a new location within the same month, or to a new month, automatically updating the event’s information.

Read how we made this happen.