Set up FXL Bulk Edit
The API names of Salesforce objects and object fields are required to configure the FXL Bulk Edit fields for the FXL Data Grid. The most accurate way to enter the API names is to obtain them from the Object Manager.
The object for FXL Bulk Edit must match the object for the FXL Data Grid you have already added and configured. You could also configure custom labels for the FXL Bulk Edit Lightning Component.
-
Drop FXL Bulk Edit to the record page with the FXL Data Grid already added and configured.
-
Select FXL Bulk Edit where it is placed on the page to display the configurable fields to the right.
-
Obtain the API name of the records' object and enter it in sObjectType to bulk edit.
-
Obtain the API names of any additional objects you want to display in FXL Bulk Edit and enter them separated by commas in Identifying fields to display in results.
-
You can also do one of the following:
-
Obtain the API names of the specific fields you want to limit bulk editing to and enter them separated by commas in Include Only These Fields.
-
Obtain the API names of the specific fields you want to exclude from bulk editing and enter them separated by commas in Exclude These Fields.
-
-
Click Save.
-
If this is the first time FXL Bulk Edit has been set up on the page, activate the configuration of the page as the Org default
-
Click Back.
-
Verify FXL Bulk Edit is displaying the object you selected.
Setup Dependent Lookup Fields
For most fields in FXL Data Grid, the default Salesforce Lookup Control functions as expected. The default lookup control does not work for dependent fields. You can use a custom search popup to get a filtered lookup for dependent fields.
-
Obtain the API names of objects for the dependent fields.
-
Obtain the API names of the dependent fields you want to filter for bulk editing.
-
Create or modify an fxl_searchSettings.js Static Resource file to include a
bulkEditfunction for the desired dependent field filtered lookup. -
Verify the Bulk Edit Control is added to the object’s lightning page.
-
Verify the fields have been added to the grid columns on the lightning page.
Example 1 - Bulk Edit Contacts Should Match the 'First Letter of Contact' Field
Scenario
On Quote Items, we have a verification that the entry in Contact field starts with the character entered in a first_letter_of_contact field.
When doing a bulk edit on the Contact field, only valid entries that match the entry in first_letter_of_contact for the controlling record should display.
| For this example, we assume the objects, fields, and verification rule already exist. |
To accomplish this lookup with verification for a bulk edit, the following code is added to the fxl_searchSettings.js Static Resource file.
bulkEdit: {
"FX5__Quote_Item__c": {
"Contact__c": {
"QueryFilter": "(LastName=NULL OR LastName LIKE '@@first_letter_of_contact__c@@%')",
"QueryFields": "Name,LastName,FirstName",
"KeywordSearchFields": "LastName",
"OrderBy": "LastName"
}
}
}
Example 2 - Bulk Edit Wells for Selected Quote
Scenario
We have an object that tracks well sections.
The Quotes object has a reference field to the well sections object.
We also have a lookup from the Quote Items to the well section object.
When we are looking at Quote Items, we want to be able to bulk edit the well section, but the bulk edit should only allow well sections for the displayed quote.
| For this example, we assume that the objects and fields already exist. |
To accomplish this, we add the following code to the fxl_searchSettings.js Static Resource file.
bulkEdit: {
"FX5__Quote_Item__c": {
"well_section__c": {
"QueryFilter": "(Quote__c='@@FX5__Quote__c@@')",
"QueryFields": "Name",
"KeywordSearchFields": "Name",
"OrderBy": "Name"
}
}
}