Big Objects

Big objects are Salesforce's take on NoSQL (although it works just like common SQL). It allows large data storage on Salesforce's servers. Ideal for Big Data and compliance scenarios.

Sample scenario - store all field changes for an object

In this scenario, the customer wants, for whatever reason, to track changes of all the fields in ...

General Conventions

Grouping fields

Workflow Triggers

Workflow Field Updates

Workflow Email Alerts

Workflow Tasks

Workflow Outbound Messages

Validation Rule Metadata Conventions

Validation rules writing conventions

1 - Data Migrations Checklist

2 - Data Migration Step-by-step - Before Loading

3 - Data Migration Step-by-step - Loading

ARCHIVED - Process Builder Bypass

ARCHIVED - Process Builder Structural Conventions

ARCHIVED - Process Builder Naming Conventions

Sample scenario - store all field changes for an object

Object Permissions - Basic Functionality

Field Permissions - Basic Functionality

Query CRED And FLS Permissions - Examples

Updating, Deleting, and Adding Permissions

Important Notes

Flow General Notes

What Automation do I create Flowchart

Flow Meta Conventions

Flow Structural Conventions - Common Core

Flow Structural Conventions - Record-Triggered

Flow Structural Conventions - Scheduled

Flow Naming Conventions

Introduction - Why are we even doing it like this

Chapter 1: The Why, When and By Whom

Chapter 2: Software List

Chapter 3: Basic Machine Setup

Chapter 4 - Base Project Setup

Chapter 5 - Using an Existing Project

Chapter 6 - Creating a New Project

Useful Command reference

Big Objects

Sample scenario - store all field changes for an object

Search Results