Another Salesforce blog!!!

Salesforce, Apex

Scratch Org Definition File

Here’s what the scratch org definition JSON file looks like: view source { “orgName”: “nisarkhan”, “adminEmail”: “myemailaddress….”, “country”: “US”, “edition”: “Enterprise”, “description”: “Work Item #12345: add picklist to widget”, “hasSampleData”: “false”, “features”: [“MultiCurrency”, “AuthorApex”], “orgPreferences”: { “enabled”: [“S1DesktopEnabled”, “ChatterEnabled”], “disabled”: [“IsNameSuffixEnabled”] } } Favorite

Salesforce DX “If you’re an ISV Partner”

If you’re an ISV building a first-generation managed package, all of your metadata is already in a single package (unless you’re using extension packages). When you deploy updates to your packaging org, you’re typically going to send everything at once. The CLI makes it easy to do this because sfdx force:source:convert operates on only one package directory […]

Salesforce DX “If you’re a Customer”

If you’re a customer with a complex, convoluted, monolithic codebase (aka the “Happy Soup”) it can be helpful to try to start breaking things up into many small, independent unmanaged packages wherever possible. Better yet, take a look at Developer Controlled Packages (DCPs) which are part of the Packaging 2 Beta in Spring ’18. Either […]

What is a Salesforce DX “Project”?

In general, a Salesforce DX Project is a new local file structure that collects your org’s metadata (code and config), org templates, sample data, and tests. The project root is often the repository root of a version control system (VCS) as well. Specifically, an SFDX Project exists when you have a local directory that contains […]

available security features in salesforce!

Salesforce provides security controls to manage the accessibility of functionalities i your application and also the visibility of the individual records it creates. Functional security Data security Functional security: Security that applies to application objects and some code entry points (providing APIs) and also Visualforce pages that deliver the features of the application is referred […]


When it comes to performing calculations on your data, the Salesforce platform provides a number of options, API, Apex Triggers, Visualforce and Rollup summaries. The Rollup summary provides a code-free solution with the ability to apply some condition filtering. Rollup summary fields can be referenced and combined with other features such as formula fields and […]

custom field features – default field values

Adding default values to your fields improves the usability of your appliation and can reduce the number of fields needed on the screen. Default values defined on custom fields apply in the native user interface and VF UI’s Example: Create a Year text custom field in the object and in the default value provide the […]

publication and licensing of your application

The following are other organization types that you will eventually eed in order ot manage the publication and licensing of your application. Production/CRM Org: the purpose of this organization for managing contacts, leads, opportunities, cases and other CRM objects. AppExchange Publishing Org (APO) This org is used to manage your use of AppExchange. This org is actually […]

package in one of two states

Packages can be uploaded in one of two states Release: Release packages can be installed into subscriber production orgs and can also provide an upgrade path from previous releases. The downside is that you cannot delete the previously released components, or change certain things, such as a field’s type. Changes to the components that are […]

package namespace

Important decision when creating a managed package is the namespace this is a prefix applied to all your components (custom objects, visualforce pages, lightning components etc…) The namespace prefix is an important part of the branding of the application since it is implicitly attached to any Apex code or other components that you include in your […]

Previous Posts Next posts