Shivansh Yadav

Hello. My name is. I have been working in the IT background for the past 5 years, and my relevant experience in Salesforce is also 5 years. I have done projects on Apex, Lightning Web Component, and admin. There was a project in which I created new models based on LWC. And, I worked with LWC and back triggers, these things.

Handling incorporated as to and to close. So we can use try and catch block. Also, we can use the error boundaries, using the template for rendering the components or the elements. If true, then execute that portion of the element code. And, also, we can handle the events according to error occurred during the events, and we can also use the promises and the async and await. We can also show the Toast notifications or the pop up messages to alert the user so that they can fix the wrong data, or the developer can resolve the error.

So we can create a batch class, and in which there will be 3 methods. So first is the start, then second execute, and the third is the finish. And the start method, we initially call the constructor or call the, which collects the data on the dataset of our choice. And then the execute method, we are performing the logic or the calculation, which should be covered on the objects. And in the finish method, we are finishing. We are processing all the batches. We are processing the data into batches of a number and also logging the results and sending notifications.

Testing strategy is for the complex as well. So testing strategy would be used for complex. We should create a test data factory class in which we have to initialize the test data for the base objects. We should have to prioritize and plan the test data as per the application requirement. Like, as in some of the applications, there will be an object which is common. So first of all, we have to create that data. After that, the second layer of the hierarchy, we have to create that data. And we should also have to use different types of testing techniques like functional testing, integration testing. Integration testing if integration is also happening in that application. And we have to design test cases for various scenarios for the critical or normal areas. And also, we have to add positive and negative test cases so that we can cover each and every aspect.

I check the process for debugging and filling a SQL used in Webex. So I would whenever I have a SQL query that's failing, I would check what variables have been passed into the SQL, like in the field in the VAR logic and also debug the query result and the prerequisite things while debugging.

We've created a LWC component, and we can use it to reuse it for different aspects or different business logics. Just we have to do some modification. Also, we are handling the errors and exceptions very easily in the Apex class.

That's why not the process and have to correct the issue. K. Here in the where condition we are defining that last modified should not be greater than the last week. So last week. So if we have to run all the process to run on all the contacts, then we have to remove this where logic. And due to this where condition, contacts might not be processed because let's consider there are 2 contacts, and one contact is last modified on the past 2nd week. So that does not get included in the query locator. And if we have to correct this issue, then we have to change the where condition to the last modified date. We can also consider some other field values who has done any of the bad field condition as per the business logic.

Test. Will it trigger to update? Will it trigger to update contact records when an account contract hours. When an account custom file changes. In Salesforce, here we have to create a set of IDs of all the accounts which have been getting changes. And then query on that. We have to remove the for loop inside the for loop because it is necessary and it should create a performance issue. So that is done.

So we're trying to enforce those checks within an Apex class. If we just check to ensure field level security checks within an Apex class, we can use the Schema class and its methods to then quickly check whether the current user has the necessary permissions to access a specific field or not. So we can create a class, and we can create a method in which we use the Schema method names on the respective field of that object, and also the methods of the schema to check if the field has field read access. So by this, we can check whether the field is read-only or not, or the user has the ability to read the field value.

In the real estate industry, we can use Salesforce by logging records into respective objects. For leads, we can include data into the lead, and for the sales perspective, we can use the sales application of the Salesforce environment. After sales, if any issues arise, such as maintenance of the house or plumbing issues, we can log a case into the Service Cloud. By using these clouds, we can track and maintain our data very efficiently.

To align Apex development with the business financial model, first we need to establish a solid foundation to calculate our profits and losses. We have to get a clear blueprint of the financial process so that we can easily implement it in our packs.