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.
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!
Congrats! You’ve landed a new job taking care of your organization’s Salesforce.
Unfortunately, it’s an old Salesforce instance, and it needs a little love. We know how intimidating that can be, especially when you’re looking at data that may well be almost a decade old. After all, one benefit of Salesforce is that you can use it for years without needing to dump the system and start with something fresh.
Our team recently connected with a new Salesforce administrator who shared with us some of her concerns about inheriting her organization’s old system. In this case, her organization had been using Salesforce since 2008 and it had become quite cluttered with unnecessary data and apps.