Allow for filtering of sObjects

[christianjosephvarriale]

Description

Currently the Salesforce component will query an org and present all objects, including system level objects, sharing records, etc. From a practical perspective it doesn't make sense to search by them as an administrator wouldn't even have access to their properties.

Example

We see from the below screenshot that not only Account is shown, but also Account share ( only created and accessed through Apex code ), and other unnecessary objects making the list very large.

Proposed Solution

Adding a Drop-down which allows you to filter between Custom Objects, Standard Objects, and System Generated Objects. This would greatly improve the UX.

[jhorbulyk]

What is the technical way to determine if an sObject is a custom/standard/system generated object?

[christianjosephvarriale]

The metadata from the sObjects all have a custom: boolean field which we'd have access to in order to determine a custom object from a standard object. From there, in order to sort between standard and system generated you could have a list such as standardSObjectList which contains all the sobjects included in an org. Some objects in Salesforce such as the AccountHistory or customObject__history are also system generated. We would need to account for those endings. This could also give us the opportunity to search by the __history, or __partner, or __share records