HomeKeeper – A Fieldset Container Lightning Component

Problem Description

DaizyLogik and Grounded Solutions Network were working on making the HomeKeeper app managed package Lightning compatible. The primary custom object in HomeKeeper has nearly 300 fields on its package page layout, a common design in Salesforce Classic for complex objects that allows users to view related fields of a record on one page via formula fields.

One limitation when using Lightning experience is that a maximum of 254 fields can be displayed on a page layout or Lightning page. For an object with more than 254 fields, not all fields can be added to a Lightning layout to be displayed all at once, which means an administrator needs to be selective as to which fields will be shown. Currently, the available workarounds are:

  • Use Salesforce Classic
  • Remove fields from the layout so fewer than 254 fields are displayed at one time
  • Find a Lightning component on the AppExchange that can display fields from an object and ‘break up’ the page in multiple parts. This particular workaround would not work in our case, because of the need to package such a component with the HomeKeeper App, which is not possible.

Adding CAPTCHA to Volunteers for Salesforce Sign Up Form

Nonprofits love when volunteers sign up and engage with the organization. When using Volunteers for Salesforce this is accomplished through the sign up form that allows sign ups to flow from the online form directly into Salesforce. It is therefore important to protect the quality of the incoming data and make sure it is humans signing up and not bots.

This article will show how to enhance the Volunteers for Salesforce Signup page with CAPTCHA using very little customization.

Please keep in mind that the Volunteers for Salesforce Sign Up page is part of the managed package Volunteers for Salesforce so in order to add the CAPTCHA some coding will be needed.

Building A Teacher Portal Using Salesforce Communities for ArtsCorps

ArtsCorpsArtsCorps works with a growing number of teaching artists and other teaching professionals who need to track and submit student attendance as well as payroll information.They had designed a functional solution, but after a number of years, the team realized that it was not a solution that could scale to accommodate the need for a growing number of teaching artists to submit attendance tracking data, timesheets, and expenses.

The ArtsCorps team reached out to DaizyLogik to propose alternative solutions that would allow teaching artists to manage and enter attendance for their classes, timesheets, and expense information through a self-serve online portal. After exploring several options, DaizyLogik recommended using Salesforce Customer Communities to build the teacher portal that would put the ability to manage class information, student attendance, and payroll information in the hands of teachers.

Read more about how this customized solution helped ArtsCorps by designing a simple, self-serve system to support their team.

A Case Study for using FormAssembly to Manage Ticket Sales

Washington Global Health Alliance (WGHA) has been using Salesforce and the Nonprofit Success Pack for a few years to track and manage their members and donors. The data collected in Salesforce allows WGHA to measure and report on their members’ interactions and collaboration, and ultimately on the impact of their work in the global health community.

WGHA organizes a number of member and public events throughout the year. They had used Eventbrite to manage ticket sales, and had tested Brown Paper Tickets, but were disappointed with the new price points of both platforms and policy changes, and wanted to find another solution. More importantly, they wanted a solution that would easily feed all event data into Salesforce and remove the need for double data entry. Once the information was in Salesforce, they wanted to track the participation and payments of event attendees, donors, and other stakeholders associated with the organization.

Since the WGHA team was not looking for a full-blown event management system, the DaizyLogik team recommended FormAssembly.

Learn more about this decision and how our team helped to empower WGHA’s team to use this new tool with confidence.

 

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.