Friday, September 22, 2023

Developer Notes

 

What is npm? 

npm is the default package manager for Node.js. It is used to implement developer tools and command line tools for Salesforce projects. npm command line is generally used with developer tools to perform code linting/formatting and unit testing. Installing Node.js will install the npm

npm consist of three different components : 

  • Website - is for managing public and private packages
  • Command line Interface - runs in terminal
  • Registry - database of JavaScript software

Learn more about npm here : https://docs.npmjs.com/about-npm


sfdx-project.json : is a Salesforce project config file

            - Info about the package is bundled in this file. The API version name/number, login Url and other package details are included here.




Saturday, December 21, 2019

Very important Chrome extensions for an Admin


Salesforce Logins by Synebo
To manage your salesforce credentials

Salesforce Colored Favicons
When we have different SB instances on Chrome, we can easily differentiate seeing the colored favicon
Right Click > This can read and change data > Select Option 'on all Sites'. When the extension is added, it will automatically assign a color for each Instance. Icon color can be changed by Right click > Option

Note: It takes few moments to see the Instance in Options initially

Salesforce Navigator for Lightning
This extension helps you get to any Salesforce page quickly. Just type in what you need to do!
ctrl+shift+space

Salesforce Api field names
Toggle between API field names and labels on salesforce detail pages. Search for any record in Lightning and then toggle to Classic > Recent list > Select Record > Click Api field names Icon

Salesforce Admin Check All
Setup tasks more efficient by potentially saving administrators from having to manually check each checkbox in a list individually.( Object and Filed level permissions for now)

Salesforce Hotkeys


Profiles and Roles - Simplified


Security and Data access are controlled by different set of tools like Profiles, Roles, Permission sets, Sharing Settings and Page Layouts etc

Why do we need a Profile?
Profiles (mandatory for User) determine which Objects and Fields User can access. This will determine what access they have in the system

Why Permission Sets?

When you want to provide additional access to some users with same profiles, Permission sets are created and assigned to selected users.

Role :  Grant Record access using hierarchies

Why a Role when User has a Profile ?
Roles determine your position in hierarchy for Record visibility while Profile determine what User can see
If you are above someone in Role hierarchy, you can automatically see records of all users under his hierarchy though permissions are PRIVATE

4 Levels of Restrictions to what Users can see : 
App Level : Hide the App from Users
Profile Permissions: Visible, Default( To make it a default App when User login )

Object Level : Hide Tab from User
Profile Permissions: Read, Create, Edit, Delete

Field Level :  Hide Field from User
Profile Permissions(Setup > Profiles > Object > Field ) à Read and Edit
                            (or)
Field level Security for Profiles (Setup> Object > Field > Field Level security) à ReadOnly and Visible(Read+Write)

Updating at Profile level can only restrict for that profile. If there are more than one profile to restrict, go with Field level Security to update access for multiple profiles.

Record Level : Hide Records from Users
Note: Records cannot be restricted at Profile level
Achieved by :
Gate 1: OWD ( Org wide default settings) , Gate 2: Role Hierarchy , Gate 3: Sharing Rules , Gate 4 : Manual Sharing by record owner

To specify record-level security, set your organization-wide sharing settings, define Roles, and create sharing rules

Organization-wide sharing settings specify the default level of access users have to each other's records (Gate 1 for record access)

Role Hierarchy : Once you've specified organization-wide sharing settings, the first way you can give wider access to records is with a role hierarchy. 

Sharing rules let you make automatic exceptions to organization-wide sharing settings for particular sets of users, to give them access to records they don't own or can't normally see. 

Manual Sharing : record owners can use manual sharing to give read and edit permissions to users who would not have access to the record any other way. 

Note : Sharing rules and role hierarchies, are only used to give additional users access to records—they can't be stricter than your organization-wide default settings.



Friday, November 16, 2018

Career strategy in Salesforce

If you want to build your career in Salesforce, you will need to have a career strategy. There are different roles in Salesforce which you may find intrigued. Take your time and dig into your ideas and follow your interest.

Here are some job profiles :
  • Salesforce Administrator
  • Salesforce Developer
  • Salesforce Business Analyst
  • Salesforce Consultant
  • Salesforce Architect

You will soon make a huge progress if your approach is strategic. This blog of mine will assist you if you are a beginners who want to enter into as well as the job holders in Salesforce ecosystem.

I will update this blog every week with helpful material, tips & latest news in Salesforce.
                                                        

Happy Reading !!!!!!