Salesforce Interview Questions with Answers Part 38

1. How to avoid other fields that are made as required in the VF page stopping to call an action in the apex using apex:actionSupport?

Use apex:actionRegion tag.

2. How to get records which are modified in last 5 days in Salesforce?

3. How to query data which was modified in specific time limit in Salesforce?

4. Custom meta data types.

5. Custom metadata type api name?

Example: Employee_Setting__mdt

6. How to relate one metadata type to another?

Use Metadata Relationship field.

7. Field Manageability in Custom Metadata type.

When it comes to protecting fields on custom metadata types, you have three options.

Upgradeable—The package developer can edit the field after release via package upgrades. Subscriber orgs can’t change the field.
Subscriber Editable—The subscriber org can edit the field after installing the package. Package upgrades don’t override the subscriber’s changes.
Locked After Release—The package developer nor the subscriber can edit the field after the package is released.

8. Lightning Design System

The Design System makes it easy for you to build applications that comply with the new Salesforce Lightning look and feel without reverse engineering the UI as custom CSS.

9. Lightning Out 

Lightning Out is a feature that extends Lightning Apps. It acts as a bridge to surface Lightning Components in any remote web container. This means you can use your Lightning Components inside of an external site (that is, Sharepoint or SAP), in a hybrid app built with the Mobile SDK, or even elsewhere in the App Cloud like on Heroku.

10. What is Expression in Salesforce lightning?

An expression is any set of literal values, variables, sub-expressions, or operators that can be resolved to a single value.

{!Hello + v.attributeName}

You can’t use JavaScript in expressions in Lightning Components markup.

11. Value Providers in Salesforce lightning.


v is something called a value provider. Value providers are a way to group, encapsulate, and access related data.

In Salesforce lightning, we have two value providers for a component they are v (View) and c (Controller). 
a. v is component attribute set which helps to access component attribute values in markup 
b. c is  component controller helps us to link with event handlers and action for the component.

12. Is Lightning Components built on the MVC pattern?

No. There are similarities, to be sure, but it would be more correct to say that Lightning Components is View-Controller-Controller-Model, or perhaps View-Controller-Controller-Database.

13. Why is “controller” doubled up in that pattern name in Lightning? 

Because when interacting with Salesforce, your components will have a server-side controller in addition to the client-side controller we’ve worked with in this unit. This dual controller design is the key difference between Lightning Components and MVC.

14. What’s the distinction between “model” and “database”? 

In traditional MVC, the model is a programmatic abstraction between the underlying data storage (usually a relational database) and the rest of the application. In Lightning Components, there’s no Apex class that directly stands in between @AuraEnabled controller methods and DML operations.

15. How to encode the special characters for correct URL String using apex in Salesforce?

No comments:

Post a Comment