Skip to main content

Object/Action name present in Org with Queryable/Retrieveable/Searchable and many more Status in Query

We always want to know what are the objects present in salesforce so we can utilize any existing if needed or to understand the structure more. Here are few ways which help you to do that.

Basic Code to get all object without any query:

Schema.DescribeSObjectResult objResult = o.getDescribe();
            String obj = objResult.getName(); 
            System.Debug(objResult.getName());

Basic code to get Object record count, don't run for all object you might get exception of 101 SOQL. Try to run this in a loop of first 100 then 100-200 and more based on need.

{

            Schema.DescribeSObjectResult objResult = o.getDescribe();
            String obj = objResult.getName();
            Integer count = 0;
            q = 'SELECT Count() FROM ' + obj;
            try{
                count = Database.countQuery(q);
            }catch(Exception e){
                continue;
            }
            mapdata.put(objResult.getName(),count);
            System.Debug(objResult.getName() + '-->' + count);
    }

Now I'll sharing the Query which can be used to get even more detail about object such as whether object is Queryable or Retrieveable via metadata or Searchable or not.

SELECT  QualifiedApiName FROM EntityDefinition order by QualifiedApiName 

EntityDefinition: It is very necessary to understand the capability of this object. To use this object and query efficiently one should use This Link  to understand the available options and the object structure.

Query to get all Fields of any object:

select QualifiedApiName, Label, Description, DataType, RelationshipName 
From FieldDefinition 
where EntityDefinition.DeveloperName='Account'

 To get all relations fields please add the below query to where clause of above:

and RelationshipName != null


Comments

Popular posts from this blog

Platform Developer I Certification Maintenance (Winter '23)

 Maintain Your Platform Developer I Certification for Winter ’23 1. Field update actions have changed in API Version 54.0. Which record-triggered flows do field update actions now execute? Answer: Before-Save after After-Save 2. Which Apex class is used to determine the hostnames for the domains that Salesforce hosts for your org? Answer: System.DomainCreator 3. Which modules can be used for notifications in a Lightning web component instead of native APIs? Answer: LightningAlert, LightningConfirm, and LightningPrompt 4. What determines an org’s “shape” in Salesforce? Answer: Features, settings, edition, limits, and licenses 5. Which lightning-modal-* component is required to create a modal? Answer: Body 6. How do you call an invocable action from Apex code? Answer: Reference Invocable.Action Get Hands-On With Apex Assertions 1. Create Two Apex class: Copy and Paste below codes (A.) TestFactory @isTest public class TestFactory {    public static Account getAccount(String accountName, B

Custom Table In LWC

I'm assuming you've Basic understanding of Lightning Web Component, I'll be explaining you the syntax that will be generic. HTML: < template > <!-- Header Part -->      < lightning-card   title = "Custom Data table in Lightning Web Components" >          < div   class = "slds-grid slds-gutters" >              < div   class = "slds-col" >                  < span ></ span >              </ div >              < div   class = "slds-col" >                  < span > <!--A Button For extra feature-->                      < lightning-button   label = "Show Selected Contacts"   onclick = {showContacts}   style = "margin-left: 40%"   variant = "brand" > </ lightning-button >                  </ span >              </ div >          </ div >< br />

LWC js-meta.xml Configuration File Tags

Each Lightning web component folder must include a configuration file named <componentName>.js-meta.xml. The configuration file defines the metadata values for the component, including the design configuration for the Lightning App Builder and Community Builder. Some Standard Key metadata values: apiVersion : A double value that binds the component to a Salesforce API version. isExposed : If isExposed is false, the component is not exposed to Lightning App Builder or Community Builder. To allow the component to be used in Lightning App Builder or Community Builder, set isExposed to true and define at least one <target>, which is a type of Lightning page. Some Standard Optional metadata values: description : A short description of the component, usually a single sentence. masterLabel : The title of the component. Appears in list views, like the list of Lightning Components in Setup, and in the Lightning App Builder and in Community Builder. targets : Specifies wher

Translate