Sahil Goura Salesforce Developer

Can you help? What do you want me to know more about? Okay. I'm Sahil Gorra. I'm having around 5 years of experience into IT domain I'm 2 x Salesforce certified, that is Salesforce admin associate certified.

What governance standards? So governance standards, which we enforce on Salesforce, is that we ensure that data mapping is getting done correctly. And, uh, even, uh, what more we can do? What governance standards do you enforce on Salesforce? Governance standards, uh, first would be particularly, if you're talking about governance standards, then that will be, I think, uh, defining the rules, even accessing the controls, encrypting the data, monitoring user activities, and even what I'll say, checking the data is mapped correctly using validation rules also. Uh, data, uh, so another key element would be data quality, which ensures that data is accurate, complete, consistent, and even timely data is there. Okay. And once it is mapped, if there is data skew or data inconsistency or any type, then we have to, um, the standard processes which is followed is to restore the back from the backup. And then, again, starting, uh, the process such as any if any flow is happening or any automation process or anything, the process is there. So, again, after restoring them from the backup, again, doing the

Describe the approach you would like to troubleshoot a Salesforce. Describe the approach you take to troubleshoot a Salesforce integration issue where account data is not syncing correctly with an ERP system. Okay. So, uh, if you talk about Salesforce integration issue, so if, uh, first of all, I check, I'll go to Salesforce object manager, then I'll go to cases, then field and relationships, and check if any additional case fields were created in our Salesforce case object. Then after that, I'll check I'll open that, uh, that case object. I'll see that what all data is created, if there is any redundant data or if even if data is not there or what exactly is in place. Then, uh, I'll check using workbench and, uh, particularly ERP system if you're talking about. Then it it is something that we need to ensure that, uh, what I'll say, we have, uh, I'll use we can use super rest API. We'll we'll majorly use rest here. And using workbench, we can, uh, do a put we can, first of all, get get the query so that understand that whatever data is there, it is clear or not. And then if we can remove the data and, again, put a post query so that this integration is done properly and all the data, uh, inconsistencies inconsistencies removed, and we are ensuring that this is working the data is properly integrated after it is moved properly into Salesforce to the from the 3rd party, uh, from Salesforce to third party application.

Let's check. How would you troubleshoot? How would you troubleshoot and resolve complex sharing rule issues that inadvertently restricted data access for a team. So first of all, I'll say that we can't use sharing rules, and we can't restrict access below our organization by default setting. That is public read only private public read only on and public read. Right? It is a necessary setting that is the most narrow and more at the bottom. Then now how will we troubleshoot complex sharing rules? So first of all, I'll check that, uh, I'll go to the sharing setting. I'll say I'll go to the sharing settings. I'll check what are sharing settings out there. I'll first go from all uploading, and I'll check I'll check the profiles. Then even after that, I'll check the permissions, its rules. Uh, everything is getting mapped or not. Then after that, uh, I'll go to the sharing settings. What are sharing settings? Even if it is account setting, opportunity setting, where all these are there, then I'll check what all accesses are given to a team. And I'll check for all the sharings inconsistencies. Uh, then what I can do is that I can remove all the sharing settings or sharing tools, and I can create new ones. Or if if I'm able to troubleshoot the proper 1, the best way is to either remove it all and then, again, reiterate it and, again, create those sharing rules because, otherwise, it will be a problem next time. So it's better to create a new sharing rule set of new sharing rules, uh, so it won't be affecting another set of another set of people. So this way, we can do that.

Okay. How do you manage and assign correct permissions for a new hire in the sales department in Salesforce? So if I we've talked about it. So then the approach we follow is we go to the user. We go to sales for settings, and then we go to, 1st of all, setup, then we go to the quick find box, enter users. We will select the user. Then after selecting the user, in the permission site, set assignment related list, we'll, uh, click on edit assignment. After editing, clicking on that to assign a permission set will take the permission sets and add permissions, and this is something to add a permission. But if you're talking about now for a new hire so let's say the person is hired for a sales department. We'll check and on what level he's at. Either he's a sales executive, he's a sales representative, he's a sales manager. Depending on his first of all profile, uh, then his, uh, role hierarchy. Then on what level he is, we'll, first of all, give him a profile and then a role. And after that, he'll be present into the role hierarchy. Depending on that, he will have all the permission required permissions that could be create, read, update, delete. So mostly delete permission is not given. Usually create and read permission that delete. Even sometimes updater is also not given depending on the requirements as well as in this need. And after that, once we have provided them the role the profile and the role, then also if it requires something else, then rather than giving all the those permissions to his profile, what we'll do is we'll create a permission set. And after that creating a permission set, we'll make sure that he is having all the accesses, he is able to access anything. Because many times what happen if someone sends us a link and that user is not having access to that data in Salesforce, that link will be broken will show broken because that data will not be shown. But in this scenario, if we have given him the permissions, then he will be able to see that object or that data. Even a report or a dashboard could be there, which is required by him, but he's not having that permission. So by giving him to that permission set, I'll do that, and this will this is the way I'll, uh, manage and assign the correct permissions for a new hire.

New Salesforce release. Okay. So I'll say when a new Salesforce release is announced, what steps do you follow to evaluate and implement new features? So first, I'll check the release, whatever we have in the release. And I'll I, first of all, familiarize myself with all the release notes. And even as as, uh, I use a sandbox to check my orgs orgs compatibility with Salesforce major release before even it is released in a live production environment. Now Salesforce has major 3 releases in an year to improve improve the quality of life updates, new features, and security enhancements. And now we test these features rigorously. Okay? And now the specific requirements we need to consider to before the major release is something, let's say, we need to plan ahead. And before any release, Salesforce publishes all the release dates on Salesforce trust. After that, we review all the release notes, release notes, all the new changes, listing changes, critical updates. And we also should learn that how should we use the release notes and identify which production features our company uses. So let's say our company, majorly in my current company, 2K Technologies, we use Salesforce Einstein. And for inbox and outbound inbound and outbound integration with Outlook. So whatever emails or events we create on Outlook, it gets reflected into Salesforce. And whatever event we create in Salesforce, it gets reflected into, uh, this Outlook. So this we use using instant activity capture. That is the thing. So depending on that, whatever features we use, I'll check on those features. Then we'll use a release metrics to identify what new features and changes can impact our port and if any action is required. Now I'll check back in the release readiness trail with the community, which is posted before a month. Okay. After that, we'll test test and test. Major releases are first present in sandboxes approximately around 4 to 6 weeks before it's live. So we have time to review our new features, and we can take them for a test drive, I'll say. Okay. And, uh, understanding the sandbox preview process, how it's working, is it working fine or not, we can either ensure that it is aligning with that testing. Or if it is working fine, otherwise, we can rule back the changes. And we can't we should not do those changes if there's an issue. We should not do, uh, do those change in the production environment. Otherwise, if everything's working fine, we can directly, uh, after proper rigorous regression testing, we can send it to our Salesforce production environment. If whatever features are required and if something is mandatory and it will be better. So let's say Salesforce introduced this validation rules. Instead of creating a validation rule or creating a trigger, we can now create a validation rule in within flows itself. So that's a new thing, and that's a better for a betterment. So this is something which, uh, after rigorous testing on sandbox, we can use and implement in our Salesforce work.

No. Setup. If I need to set up a workflow for lead follow-up task, what Salesforce tool would I use? Okay. So here, since we know that workflow and process builders have become obsolete, now we major companies who are using these things are having an option to convert it to into a flow. So we can directly convert into it into a flow, but the better approach we we can follow is we can create that flow from scratch so that whatever integration or whatever issues we had beforehand, it should not be a problem, and they will not be, again, redundant and will make the case redundant. And the flow should, uh, flow should be properly, uh, working. So the, uh, the major thing the tool which we primarily use will be flow. And for lead follow-up task, Flow will using Flow Builders, we can create automated workflows, processes even using a visual interface. Even Salesforce flow enables the creation of simple and complex automation. Okay. And, uh, lead follow-up task. So, basically, uh, lead follow-up task will create a proper flows from start element, then we'll add a decision element. After adding that decision element, we'll, uh, see, uh, if it is a yes or a no. Then after that, adding that, uh, we'll set up a proper lead process and even using we can also use a lead assignment rule also and then approval process also could be used. And after that, we can achieve this.

Okay. The difference major difference between profiles and roles is profile is something which is a mandatory for a user. User can't be created without a profile, And rules are something which are not mandatory, but it gives us data visibility. Profile gives us access to the objects like account, contacts, opportunities, and all of this stuff. Whereas, roles gives us data visibility. Uh, we we have 2 types of security settings. 1 is object level security, and second is, uh, this record level security. So in object level security, we have this, uh, what I'll say, profiles and roles and even permission sets, we can say. Uh, profiles are the gives us object level security. Those gives us visibility. Uh, the major example here is so if we have if we have 50 records and we want the user to only show 40 records, So there, we can use this role, and, uh, this role could function, uh, and from this role, that user could only see those 40 even though that org is having 50 records. That is a major difference between profile and role. And now talking about the permissions, it's whatever permissions that role was not having. So rather than giving those permission to that particular specific profile, what we can do is we can give additional permission to set to, let's say, that particular sales user who require that permission. And this way, rather than giving them to to all the user, we can give that permission set to that user. And once his work is done, we can remove that permission. Now we have record level security. In record level security, uh, here comes the OWP setting that is organization by default, which is private, public read only, and public read. Right? Then we have whole hierarchy, which is let's say we have a sales executive, and there's above sales manager and above him all. So all the records which a sales executive can see can see or even private records which, uh, uh, for which the sales executive is the owner. The they can be not only read, we will edit it by above the or hierarchy. Let's say sales manager, CEO, all the above them. And, uh, majorly, we we can't disable this rule hierarchy for standard objects. We can only disable it for custom objects, but this is something rule hierarchy. And then we have this, uh, this, what else is, sharing rules, which is criteria based and owner based sharing. And then we have manual sharing. If if you want to share a few uh, 1 or 2 or few reports, then we can use manual sharing. Then we have Apex based sharing also. So majorly, I have already explained the difference between profiles and roles. Thanks.

A plan for restructuring of Salesforce roles and profiles that requires minimizing disruption to existing workflows and data accessibility. So So if you want to restructure of Salesforce, I'm using minimum disruption. So what we'll we'll do is we'll check the whole the role hierarchy, and we'll check for all the people, profiles, and rules. And, uh, first of all, we'll deactivate all those users which are, um, uh, not required, and we'll make sure that they are deactivated, and, uh, we have a license free. And before that, we'll check all the workflows, process builders, or all the things from which they're connected. We'll tell, uh, use uh, send it to a delegated user. And then after that, we have Salesforce roles and profiles. Uh, so in that existing work, we'll check that from what of that's the best way is to check and go and check and even map out what which workflow and which flow our process builders, which profile is integrated to, then create a map. And first of all, we'll go for those, uh, profiles which are, uh, heavily integrated, heavily integrated with this workflows and automation and which can be disrupted. So first of all, we'll make a list of all all those and we'll keep them aside. We'll not change anything. Then whatever is having least connection to the workflow or even we can send it to a delegated user or even, what I'll say, uh, even those profiles which, uh, from which these logics can be delegated or even removed. We'll go through this manner. So first of all, those profiles which are have intense, important, and having the maximum workflows and automation rules, We won't disrupt them. 2nd will be where we can change or delegate it some to some user. And 3rd, profile will be that in which I are either not connected or even connected to just 1 or 2 workflows. This will be a better plan for restructuring.

How do you use Salesforce? So Salesforce reporting and analytics to inform business decisions. So, basically, Salesforce provides a great report, I'll say, and dashboard even to provide proper metrics of data time and the data types, different data charts using funnels, bar, histogram, and all and all. So it's provide it provides a great reporting structure, having all the filters and everything. Now how will I use the sales for reporting and analytics to inform? So I'll, first of all, get all the data points whatever, uh, from what duration, what will be the numbers, how, uh, so let's say they record from 1, 000, 000 to 10, 000, 000, and there's a year from 2011 to 2024. So I'll first of all check on the data points what year, then what numbers do we require, what all companies do we require, then how many people, what else position they have, profile rules, whatever. I'll after collecting all the data points, then I'll create a report, and then I'll create report based on different rules and then different data points, like, let's say, different years, year on year growth, and different, uh, let's say, if you use a sales cloud, so different selling on different categories. Depending on that, how the report is required, I'll provide them different set of reports and so that they can even I'll create a dynamic dashboard also so every user can have this thing. And even I I'll do some bucketing so that it will be grouping also, uh, so that it will be helpful for the user, and we can even see all those reports into, uh, the same that bucket. And this way, I'll use the sales for reporting and analytics, even dashboarding also to provide them a proper picture, Whatever filter filters or whatever to, uh, field they don't require, I'll remove them. Whatever data points they don't require, remove them. Whatever additional data points they require. So if they want this percentage, this calculation and all, so I'll add even a formula field so that whatever calculation they want to do, even if they want to remove it for some year, let's say, they want to remove at 2011 and they want to inculcate 2024 whole year or since it is not completed and they just want it for 2023. So I'll inculcate that. So depending on that, we'll have to make multiple iterations depending on multiple stakeholders. We have to check with multiple stakeholders, and then we can do that. After that, uh, I'll the 1 of the better, uh, much better platform is Tableau and even PowerPA, uh, which, uh, even is, uh, I think in terms of reporting and analytics, it's much better than Salesforce, particularly here, and, um, majorly, companies have started using Tableau and Power BI so that this reporting and dashboarding becomes much more easier, more dynamic, and even gives us a scope, uh, much more much better scope, I'll say, that, uh, this way, uh, that reporting and dashboarding can be done in a much better

When dealing with large scale data migration, what steps do you take to mitigate the risk related to Salesforce's government limits? So there are certain best practices where, like, say, there's some this is similar to, like, we have best practices for triggers or coding or something. Here also, we have since we are dealing with the large scale at the millions of the, um, data records we are talking about, so here are some best practices which we need to follow. So, uh, once we have defined the method which is best to import or export the data, there are some best practices. First of all, we need to identify the data we need to migrate. That is choosing the objects we need to migrate. Let's say, deciding whether migrating only the contact information from the each account or migrating the account information also. Even sec secondly, it will be creating the templates for the data. Uh, these templates will be like creating an Excel template for each object using a data export from data loader and using insert, update, bleed, delete data using data loader. Now since objects have mandatory relationships which dictate the order of data migration, identify the required fields for each object for more, and, uh, this will help us reviewing the data before populating the template. For example, we'll we can load 1 record and then check the results and can load all the records. Then after that, we'll prepare the destination or, let's say, we'll consider using creating, uh, creating custom fields to store any legacy ID information and even creating custom page to store the data contained in nonstandard fields in our organization. We can give an example, like using home phone for user, and even the next point will be validating the data using this technique, uh, like creating custom reports to validate the account records and provide an overall snapshot of migration. Then even what we can do is we can even build a report. We can spot the check of the data and review the exception records. Report sorry. Exception reports. I'll say exception reports to see which data was not migrated. And bills after checking which data was not migrated, we can either, uh, again, do it or we can again restore that. If there is any data skew or inconsistency, we can again restore the backup, and we'll make sure that whatever data was not mapped properly or what issue was last time, we will remove and rectify that error. After rectifying that error, we'll make sure that all the data records are there. And we'll even check from the log file from all the list, uh, if next time also this data, uh, is failed, this data upload is failed or migration is failed, then we'll send those data also and we'll check why it failed and then we can again migrate it.