Skip to content

Salesforce Data Architecture Part 1

VIDEO TRANSCRIPT | Recorded: 2025-12-16 | Verify against current system state

Abstract

Introduction to Salesforce data architecture, covering object relationships, data model design decisions, and foundational structures

This article was auto-generated from the video transcript. Review and enhance the content based on the full video.

Key Procedures

  • Access I2C Bitbucket repository: Login credentials in 1Password (IT Support account) → Click Bitbucket → Integrate to Cloud workspace → AANP repository
  • Code deployment flow: Feature/bug branch → Dev → QA (I2C testing) → Staging (AANP testing) → Production
  • UAT and pre-UAT sandboxes are abandoned - only use Dev, QA, Staging, and Production
  • To view/manage sandboxes: Log into Production Salesforce → Setup → Search "Sandboxes"
  • Sandbox types available: Developer (100 licenses), Developer Pro (5 licenses, more storage), Partial Copy, Full (1 license - used for staging)
  • Full sandboxes can only be refreshed every 30 days - plan accordingly
  • Developer sandboxes can be spun up quickly for testing, then deleted when done
  • When creating sandbox: Choose "Create From" to base it on existing environment (but licensing limits apply)
  • Cannot clone full sandbox to full - only 1 full license available
  • SF Docs site (docs.aanp.org) contains official business requirements - I2C references this for specifications
  • Click Up is used for I2C project management and task tracking
  • Profiles vs Permission Sets: I2C created many profiles but most are unused - focus on Membership Support profile
  • Hidden fields exist in Salesforce (not visible even to custom admin) - must log in as regular admin to see them

Notable Statements

  • 0:17 "We'll start very broad because I know some of you are aware of the name I2C and"
  • 9:59 "specific needs. This information never got pushed back"
  • 16:56 "You can set those up and run as many as you need to to test things to try it out."
  • 23:25 "repository. So that's what I would do. And remember we had something called Dev"
  • 28:42 "So you can you can kill it in five days, seven days, whenever you want it."
  • 34:35 "We don't create a permission set again because that's again duplicating the"
  • 37:43 "if you have to work on that and kind of like rebuild that,"
  • 44:19 "My recommendation moving forward is to always do this."

Systems & Configurations

Systems Mentioned

  • Salesforce

Specific Configurations

Item Value/Setting Timestamp Notes
Review video Add settings Add timestamp Add notes

Credentials/Access Mentioned

  • Review video for credential references
  • Document access requirements

Errors & Troubleshooting

  • Issue: Review video for troubleshooting content
  • Cause: Document root causes
  • Resolution: Document solutions
  • Timestamp: Add timestamp link

Transcript Gaps & Quality Notes

  • Auto-generated from transcript
  • Duration: 59 minutes
  • Presenter: Jeff Sikes
  • Review for accuracy and completeness