Accenture Interview Questions for Salesforce Developer | 4+ YOE | June 2024

[@jagadeeswaribolli6768]

If contact is removed, for that scenario the piece of logic is missing in trigger code, we should iterate through Trigger.old as it's after delete.

[@SolitudeStar2226]

For user specific form.... To keep maintain email address in metadata is fine. But, can't we create a public group where user are assigned who does not have access on form. And then we can handle in apex by soql of public group with name by checking logged in user id available in group or not? I'm just thinking, please let me know if I'm wrong

[@prachikamble3118]

Very informative, thank you🙏

[@salesforcein5minutes]

@@prachikamble3118 glad it was useful 😃

[@namanshetty2781]

Custom setting can have CRUD operation in apex but not for custom metadata. I think this is right

[@salesforcein5minutes]

Actually the answer is both are possible customdr setting directly and meta data using Metadata.Operations, but thats the ans i gave in my interview

[@ningutej1]

In custome setting CRED in custome metatdata CRE

[@rajsekar3042]

It's very informative but I have one qn...For one of the lwc question to get only specific data from external system, since you are using future method in apex, how can you return the response and send to lwc again? Because future can't return anything right?

[@salesforcein5minutes]

Use platfrom. Events in such cases

[@awesomekj5812]

Sorry your diagram in first question got me off guard ...the way you diagrammed it , it felt like form exists outside the Salesforce. If it is LWC form , shouldn't it exists within that salesforce cloud ? Also for your 2nd question ....couldn't you hide the submit button using elseif in LWC rather than doing that in Apex ?

[@salesforcein5minutes]

1) i just wanted to show the diagram, how it will look when we submit the form hence i drew it outside Salesforce database, so it was just representation and nothing else 2) for question 2 if your current user is not the one specifed in metadata, then why do you want to run the code itself, in your case you will bring whole data and then write if else instead my thinking was bring only data which is nesscary

[@Adventourer__]

For first question, we can also use lightning-record-form to directly save data to an object correct?

[@salesforcein5minutes]

@@Adventourer__ we can but they were looking for how can i pass data at the backend

[@Adventourer__]

@@salesforcein5minutes Okay, got it. Your explanations are very good. Keep up the good work!

[@salesforcein5minutes]

@@Adventourer__ thanks ☺

[@ashishgupta5209]

I have a question when the interviewer asked us the trigger or some code where we gona write the code is it on the developer console or in the notepad I am a fresher

[@salesforcein5minutes]

@@ashishgupta5209 always on notepad because you might make syntax mistakrs which you can always cover by saying, as i am writing in notepad there can be some sytax errors and those are accepted as well

[@abisheakramasamy5871]

Its for freshers??

[@salesforcein5minutes]

For experienced

[@prasadmuthyala9625]

1. Enable Debug Logging First, ensure that debug logging is enabled for the user executing the flow. 2. Assign the Debug Level to a Trace Flag Go to Setup. In the Quick Find box, type "Debug Logs" and select Debug Logs. Click New. Select the User to monitor. Set the Debug Level (more on this in the next steps).-->Here we can create new Debug Level(Set the Apex Code and Workflow levels to FINEST. ) Choose the debug level you just created. Set the start and expiration date/time for the logging. 4. Execute the Flow Run the flow that you want to debug. The system will generate logs for all actions taken during the flow's execution, including any exceptions. 5. View the Debug Logs Go to Setup. In the Quick Find box, type "Debug Logs" and select Debug Logs. Find the log entry created during the flow execution. Click View to see the log details. Debugging Flow Exceptions In the debug log, look for entries related to FLOW and FLOW_ELEMENT_ERROR. These entries provide information about the flow's execution and any errors encountered.