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.
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.
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.
Our DaizyLogik team of developers and consultants have a long history of working with local government agencies to support them in upgrading their systems and evolving their technology to adjust to changing demands.
We were thrilled to support the City of Everett, Washington, as they sought to extend the Business and Occupation Tax system, a service oriented, extensible and modular system that our director of technology, Vladimir Martinov, originally led the design and development of for the City of Bellevue, Washington.
Built on the Microsoft .NET framework and powered by SQL Server, the system supports critical business processes for local city agencies and integrates with external systems via web services.
Over the years, this system has become a regional success and has been adopted by other city agencies. Seattle area cities have licensed this system from the City of Bellevue but have needed modifications to ensure the system fits their own business processes and city tax code.