This time around, we’ve turned our attention to easier access to all Salesforce Records.
In the interest of simplified access, we’ve employed a minimal, dynamic combination of Components- first a dropdown to select an Object, followed by a search field that suggests records within the Object as you type.
Tracing the Flow Of Control Between Components
In the beginning, the Autosearch LW Component(Parent) applies the getAllObjects method(a ‘wire’ method) from within the ManageRecordsController.cls class to retrieve and preview all sObjects in Salesforce.
Next, behind the scenes, the RecordSearch LW Component(Child) too uses getLookupSearchRecords to call a method within the same class.
The method takes in searchstring and sObject as parameters to search and fetch Records with names matching searchstring from an API that. The API, in turn, interfaces with the Autosearch Parent Component.
Then, the Record Item Lightning Web Component(Grandchild) previews all Records fetched through Record Search. To do this, a look-up Field with Record names is setup. Record Item accepts the first few letters entered into the lookup as the searchstring and uses ‘event bubbling’ to come up with the corresponding Record ID(a prerequisite to access Record data at the backend) of the Record matched.
For Live Demo Click here
Source Code
recordItem.html
recordItem.js
recordsearch.html
recordsearch.js
autosearch.html
autosearch.js
autosearch.js-meta.xml
Apex class
ManageRecordsController.cls
Conclusion
The immense benefits of bringing down access times for Object Records speak for themselves. Also, it goes without saying, but time-savings too multiply across agent processes and with each purposeful Record query made. The code illustration above is an example, typical of such far-reaching, yet subtle customizations possibilities in Salesforce.
For more assistance with productivity pages, access-focused improvements, and process efficiency solutions, reach out to us at sales@hicglobalsolutions.com
India 
USA
UK
Canada