Developers usually get strange requests from client to make some of the text clickable so that if a user clicks on that field in record it should redirect to detailed page of that record. We know that standard Name field already does similar task. However there will be a scenario where client uses Standard name field as auto number field and a custom field to save proper name and requests for a clickable link on the custom field and requests to make it clickable.
There are multiple ways in which we can perform this task. But in this blog we will see 2 ways using formula field.
One simple way that everyone follows is using a relative URL, where you can create a custom formula field and use relative URL with record Id.
Before knowing what governor limits in salesforce is, let us understand what Multitenancy is?
‘Multitenancy’ is a fundamental technology that cloud uses to share IT resources cost-effectively and in securely.
Salesforce has many servers across globe and the org or salesforce instance that you work in will be in one of those servers. There servers will have huge database and machines and are so powerful that each server can host multiple instances of salesforce from different companies. So obviously every application will share resources that are available in the server like processor, database, network etc. Everything works smoothly without any deadlock situation. Such sharing of resources among different applications is called multitenancy.
If you speak in general, in a single building there will be many houses and different owners will own individual houses and resources such has, common space, water, garden area electricity will be shared among those people. Here building is like a server and you house is like your own application. There can be multiple applications in a server just like multiple houses in a building.
Password is important for authenticating users. Users usually forget password or try multiple wrong passwords and many more reasons where system locks their credentials and restrict further access. A system admin can reset the password in many ways. In this blog we will see different ways through which you can reset the password.
As per my knowledge there are 3 ways you can reset password of a user in salesforce.
There will be some scenarios in organization where you want to share a record based on some complex scenario, but you cannot define the complex scenario as a criterion in sharing rule. Then the question is how you can share a record, of course you can share them manually. But how many times you can share records manually, trust me its annoying to share records manually again and again.
Salesforce provides another way to share a record and that is through apex code via share object. So what is Share object? Every standard and custom object will have a share object in salesforce with predefined fields as shown below.
Standard Object’s Share object will be “sObject+Share”. For example, Account objects Share Object is AccountShare. Similarly, Opportunity objects Share object will be OpportunityShare.
Custom Object’s Share object will be “CustomObjectName + __Share”. For example, if your custom object name is MyCustomObject, then its API name will be MyCustomObject__c and share object will be MyCustomObject__Share.
There will be some scenarios where all records are privately owned, you want to share records based on some criteria with a specific user or group of users or to specific role. In such cases sharing automation should work on all records of that object. You can build a sharing rule which will handle such situation.
Consider a scenario where records should be shared based on continent field and those records should be shared with people of specific group or role. You can simple create sharing rules for each continent and share according to business requirement.
Consider a scenario where security setting is too restrictive in your org. If there is a need to share some specific record with only couple of users or group and that too for one time sharing, instead of changing OWD setting or profile level setting or creating a permission set you can share those records manually directly from records detail page.
An organization where there are many employees, each employee is designated with a specific designation or role. Many employees report to a person who is above their designation. Like in a IT industry where we have designations like, Software Engineer, Senior Software Engineer, Module Lead, Tech Lead, Manager, Director etc. Where Software Engineer and Senior Software Engineer will report to a Module Lead or Tech Lead. Similarly Module Lead and Tech Lead will report to Manager and so on.
Let us assume that in your organization you have multiple users, let us say few are assigned to Marketing Agent Profile, some assigned to Marketing officers Profile. Marketing Agent Profile is more restricted compared to Marketing officers Profile. You know that there is a user who is in Marketing Agent’s profile who is performing better, and you want to assign him some additional permissions.
Permission sets have similar options that are in profiles, then question is why permission set when we have profiles. permission set is a collection of settings and permissions that give users access to various tools and functions. The settings and permissions in permission sets are also found in profiles, but permission sets extend users’ functional access without changing their profiles. You can create a permission set, give those additional access in that permission set and assign it to users who needs those additional options.
There are ample options in profiles in salesforce. In this post I will discuss about different options with which you can secure data (only, not all options) from different users.
With OWD, you can decide who can view, edit the record and who cannot. I will try to explain you how profiles can be helpful in sharing records and its permission.
But first let’s see how you can reach profiles.
Step 1: Login into your Salesforce Org.
Step 2: In Quick Search type “Profiles”, Select Profiles option.
You will see list of all profiles that are available in System. Both Standard profiles and Custom profiles.
Here you can see a column named Custom, you can differentiate between Standard and Custom by the checkbox field. If check box is unchecked, its standard profile and if check box is checked, its custom profile.
There are limited standard profiles, predefined by salesforce. You can create custom profiles and assign permission as per business requirement. In this post we will only discuss about different options to secure data.
To secure data through profiles there are multiple options.