-
Notifications
You must be signed in to change notification settings - Fork 93
soqlDatatable: Configuration
James Hou edited this page Jan 31, 2021
·
2 revisions
-
Create a Custom Metadata (CMDT) row in
Datatable_Config__mdt
.-
Type
must be text of"Actions"
or"Actions;Lookups"
(no quotes).
-
-
Create a CMDT row in
Datatable_Action_Config__mdt
.- Must Lookup to the
Datatable_Config__mdt
created in step 1. - Follow Page Layout instructions for
Type
,Order
etc.
- Must Lookup to the
-
Input the name of the
Datatable_Config__mdt
intoAction Configuration
in App Builder.- You can reuse the same
Datatable_Config__mdt
name inLookup Configuration
if you've configured thatType
to"Actions;Lookups"
.
- You can reuse the same
-
Place
MessageServiceHandler
somewhere on the App / Record Flexipage or the Utility bar (without a name/icon). See the main configuration for details.
-
Create a CMDT row in
Datatable_Action_Config__mdt
and follow the steps to reference a Screen Flow. -
All Screen Flows must implement the following input variables:
Name Type Description SelectedRows SObject[] Choose the correct Object type in a Record Collection. FirstSelectedRow SObject First Selected Row, choose the correct Object in a Record variable. UniqueBoundary String For Dialog Auto Close
orEvent Publisher
to refresh the table that opened the Screen Flow.SourceRecordId String For Record Pages, the recordId of the record that the soqlDatatable
is on.
For App Pages, this is not required.
-
Create a CMDT row in
Datatable_Action_Config__mdt
and follow the steps to reference a custom LWC. -
All custom LWC can optionally implement any of the following
@api
variables:Name Type Description selectedRows [] An array of SObjects: [{},{},{}]. uniqueBoundary String For messageService
to know its boundary.
Can also be a unique string of your choice in case you want to usemessageService
on a different boundary from within the modal body LWC.sourceRecordId String Available on Record Pages, the recordId
of the recordsoqlDatatable
is placed on.