TrackForcePro - Training Guide

🏗️ Understanding the 3-Surface Model

TrackForcePro isn't just a popup — it's a toolkit across three distinct surfaces. Understanding which surface to use first prevents confusion and makes users 3x faster.

1️⃣ Launcher Popup

Quick-access menu on the extension icon. Check current org, jump to a tool, resume last workspace. 30-second interactions.

2️⃣ Workspace Tab

Full-screen editor for serious work: SOQL, GraphQL, REST, Records, Org Tools. Multi-step workflows, tables, builders.

3️⃣ In-Page Overlays

Floating panels on Salesforce pages when context matters. Show All Data, Sidebar, LWC Explorer, right-click actions, Command Palette.

Teaching Principle: Before every action, ask: "Do I need a quick jump (Launcher), deep work (Workspace), or page context (Overlay)?"

Decision Tree

I need to jump into a tool quickly: Launcher → Workspace
I'm writing or debugging something complex: Workspace directly (Ctrl+click extension icon, or use Launcher to resume)
I'm on a Salesforce page and need context: Show All Data (double-click field or right-click), Sidebar (Ctrl+Shift+S), LWC Explorer, context menu
I'm searching metadata or jumping between features: Command Palette (Ctrl+K)

🎯 The 3-Mode Architecture

All features are organized into three modes. Each mode groups related tasks and appears as a colored pill in the workspace header.

Mode 1: Explore (Blue) Explore

For querying, exploring data, and managing users & security:

SOQL Builder — Visual query editor with inline result editing and 5 export formats
GraphQL Builder — Three-pane query editor with real-time validation
Records — Record scanner with All Fields table, inline edit, breadcrumb navigation
REST Explorer — Send any REST API request with collections and history
Schema — Search objects, fields, flows, permission sets by API name
User Manager — Search users, update profiles, manage sessions
Security Manager — Browse Profiles and Permission Sets with drill-down

Mode 2: Debug (Amber) Debug

For monitoring real-time events and troubleshooting:

Platform Events — Real-time CometD streaming with event filtering
Debug Logs — Fetch, filter, and search Apex debug logs

Mode 3: Analyze (Green) Analyze

For auditing, health checks, and administration:

Audit Trail — Fetch Setup Audit Trail with category filter and CSV export
Org Health — Real-time org limits and performance metrics
Org Tools — 7 panels: Login As, Custom Labels, Deployments, Scheduled Jobs, Debug Logs, Org Limits, Admin Utils
Org & Favicon — Custom favicons per org with 8 shapes and 8 colors

Pro Tip: The mode bar is visible in the workspace header. Switching modes changes only the view tabs below — all other settings persist. This is intentional to prevent context-switching friction.

🗺️ Role-Based Learning Paths

Different roles need different first wins. Start training with your role's path.

👨‍💼 Admin Learning Path

Phase	Focus	Features to Master
Beginner (Day 1)	Getting comfortable with the Launcher and Workspace	Launcher popup, resume workspace, switch modes, view current org
Intermediate (Days 2-3)	Metadata discovery and record inspection	Schema search, Records tab, All Fields table, record history, Show All Data on pages
Advanced (Week 2+)	Org management and automation troubleshooting	Org Tools (labels, deployments, scheduled jobs), Debug Logs, Audit Trail, User Manager

👨‍💻 Developer Learning Path

Phase	Focus	Features to Master
Beginner (Day 1)	SOQL querying and REST API exploration	SOQL Builder with visual editor, REST Explorer, inline result editing
Intermediate (Days 2-3)	Component inspection and event debugging	LWC Explorer, Platform Events, Debug Logs, GraphQL queries
Advanced (Week 2+)	Advanced queries and automation troubleshooting	SOQL sub-queries and aggregations, GraphQL relationships, Records bulk scan, LWC network tracing

🎯 Support/Ops Learning Path

Phase	Focus	Features to Master
Beginner (Day 1)	Record troubleshooting on Salesforce pages	Show All Data, context menu, Field History, Sharing tab
Intermediate (Days 2-3)	Data inspection and user access verification	Records tab, All Fields table, User Manager, Security Manager, pinned records
Advanced (Week 2+)	Bulk record scanning and complex triage workflows	Bulk scan (200 IDs), breadcrumb navigation, SOQL for data comparison, Search UI API queries

📚 Trainer/Consultant Learning Path

Phase	Focus	Features to Master
Beginner (Day 1)	The three-surface model and three-mode architecture	Launcher, Workspace switching, Settings, Command Palette
Intermediate (Days 2-3)	Teaching others the product model	All three surfaces, hands-on labs, quiz platform, leaderboard
Advanced (Week 2+)	Customizing training for different roles	Settings for appearance, sidebar shortcuts, keyboard shortcut customization, per-org settings

💼 Common Daily Workflows

Master these five workflows and you'll be confident with TrackForcePro in most situations.

Workflow 1: Find a Record Problem Fast

1

Navigate to record on Salesforce — Open any record detail page

2

Launch Show All Data — Right-click > Show All Data, use the floating button, or use your configured keyboard shortcut (Settings > General > Keyboard Shortcuts)

3

Inspect fields — Search by field name, view values, check field history or sharing

4

Dive deeper if needed — Click "Field History" or "Sharing" to inspect, or open Records in Workspace for more context

Workflow 2: Search Metadata by API Name

1

Quick discovery: On any Salesforce page, press Ctrl+K to open Command Palette, type the API name (Flow, Permission Set, etc.)

2

Broader results: Go to Workspace > Explore > Schema, use the search bar for all objects and fields

3

Jump to Setup: Click the Setup link icon to open the metadata in Salesforce Setup

Workflow 3: Inspect a Broken Page Component

1

Open LWC Explorer: On the Salesforce page, click the LWC Explorer shortcut in the sidebar or use your configured keyboard shortcut (Settings > General > Keyboard Shortcuts)

2

Select the component: Click on the component tree to select it, or use the page inspector to highlight

3

Filter traces: Use the trace filter chips (All, Apex, UI API, GraphQL, Fetch/API, Errors) to isolate the issue

4

Open the code: Click "Edit Code" or "Edit Apex" to jump to the component source or Apex class

5

Explain this Page (X-Ray): Turn on the X-Ray chip to get a plain-English inventory of which components ran on the page and the Apex, UI API, GraphQL, and SOQL each one invoked. Use it to confirm whether the broken component is even the one issuing the failing call.

6

Errors → Root Cause: When a page action fails, enable the Root Cause chip — it correlates the failed action to the specific Apex/UI API/GraphQL call that broke, the component that triggered it, and the readable error body, so you can skip the guesswork and go straight to the cause.

Workflow 4: Triage a Failing Automation

1

Find the Flow: Open Workspace > Explore > Schema, search for the Flow API name

2

Check debug logs: Open Workspace > Debug > Debug Logs, filter by class/trigger name if the Flow calls Apex

3

Test the record: Use Workspace > Explore > Records to scan the record ID and inspect field values

4

Document results: Capture the result path and timeline in your incident report

5

Trace the Flows (beta): On the Salesforce page, open LWC Explorer and turn on the Flow & Automation trace chip to see which Flows ran on the interaction, with timing and any faults. This pinpoints whether the failing automation is even firing — and where it stalls.

6

Profile the page: Enable the Performance Profiler chip to aggregate the captured page traffic into the slowest Apex calls, N+1 (repeated-call) detection, and a round-trip/type breakdown — so a "failing" automation that's really just timing out becomes obvious.

Workflow 5: Translate or Update Labels Safely

1

Open Org Tools: Workspace > Analyze > Org Tools > Custom Labels panel

2

Export labels: Click "Export All" to download a CSV with all labels

3

Update locally: Edit the CSV in your spreadsheet (or use the bulk import feature)

4

Import back: Click "Import" and upload your updated CSV — changes are applied in batch

Workflow 6: Bulk Data Changes Safely

1

Open CSV Import: Workspace > Explore > Records > 📥 Import. Pick the target SObject and an operation: Insert, Update, Upsert, or Delete.

2

Map and preview: Upload your CSV, map each column to a field, then review the preview before anything is written. Writes are batched, and you get per-row results plus a downloadable error-report CSV for any rows that fail.

3

Or edit in place from a query: Run a SOQL query, select rows in the results grid, and use the bulk grid actions to mass Update, Set-null, or Delete. Bulk actions require Id in your query so each row can be targeted precisely.

4

Confirm and run: Review the affected record count, then execute. Watch the per-row results and export the error report if anything needs follow-up.

Production safety: Both CSV Import and the bulk grid actions are production-gated — writing to a production org requires an explicit confirmation step before any records change. v2.10.0 also added a production-edit confirmation directly on the SOQL results grid. Treat these prompts as your last checkpoint: read the operation and record count, and only proceed when both are exactly what you intend.

🏋️ Hands-On Labs

Use these labs to reinforce learning. Each lab teaches both product navigation and Salesforce problem-solving.

Lab A: Metadata Discovery Race

Objective: Understand when to use Command Palette (quick) vs. Schema (comprehensive)

Exercise: (1) Search a Flow API name using Command Palette (Ctrl+K). (2) Now search the same Flow in Workspace > Explore > Schema. (3) Which surface felt faster for you? Why? (4) Note the difference: Command Palette shows the top 3 results; Schema shows all results with filtering. This teaches feature selection.

Lab B: Page Context Handoff

Objective: Practice moving between overlays and workspace smoothly

Exercise: (1) Open any record page in Salesforce. (2) Open Show All Data via the floating button or right-click menu. (3) Find a field with history; click "Field History". (4) Then click "Open in Workspace" to jump to the Records tab. (5) Describe to someone else: when does Show All Data feel like the right choice vs. Records? This teaches cognitive load management.

Lab C: Safe Admin Work with Inline Edit

Objective: Verify inline edit protections and practice applying settings

Exercise: (1) Go to Workspace > Settings > Org Management. (2) Find your production org and verify "Allow Editing" is OFF. (3) Go to Workspace > Explore > Records, try to edit a field (should be blocked with a warning). (4) Now toggle "Allow Editing" ON in Settings (for dev org only). (5) Click "Save & Apply" and watch the setting propagate. (6) Try editing again in Records — it should work now. This teaches settings management and org-level protections.

Lab D: LWC Troubleshooting Deep Dive

Objective: Use LWC Explorer to separate Apex, UI API, and GraphQL traffic

Exercise: (1) Open a Salesforce page with custom LWC components. (2) Launch LWC Explorer (sidebar or Ctrl+K). (3) Select a component from the tree. (4) Compare one Apex action (descriptor starts with apex://) with one UI API trace. (5) Can you spot the difference in request/response format? (6) Try filtering by "Apex" only, then "UI API" only. (7) Now pick any captured call and use Capture → Replay to open it as an editable request in the REST, GraphQL, or SOQL builder — notice that session secrets are stripped automatically. Tweak a parameter and re-run it to reproduce the issue in isolation. (8) This teaches network analysis, component debugging, and turning a live capture into a repeatable test.

Lab E: SOQL Query Building

Objective: Build a real SOQL query with relationships and inline editing

Exercise: (1) Open Workspace > Explore > SOQL. (2) Write a query: SELECT Id, Name, Account.Name FROM Contact LIMIT 5. (3) Run it (Ctrl+Enter or green Run button). (4) Try double-clicking a result cell to inline edit (if enabled). (5) Try filtering results using the column filter icon. (6) Export the results as CSV. (7) Save the query to the Saved query library — give it a name, then clear the editor and reload it from the library by searching its name. (8) Export the library as JSON (handy for sharing a query set with a teammate or importing it in another org). This teaches the SOQL Builder end-to-end workflow and how to build a reusable query catalog.

Lab F: Find Unused Fields & Compare Access

Objective: Use the analyzers to make data-quality and security decisions with evidence, not guesswork

Exercise: (1) Open Workspace > Explore > Records > 📊 Fill Rate and pick a busy SObject (e.g. Account or Contact). (2) Let the field fill-rate analyzer run its batched COUNT() aggregates, then sort by fill rate to surface fields that are effectively unused. (3) Filter the list and export it — this is your evidence for a field-cleanup proposal. (4) Now open Records > Security Manager > ⚖️ Compare and pick two permission sets or profiles. (5) Read the diff of object CRUD and field-level security (FLS) between them — which one grants more, and where? (6) Discuss: how would you use the fill-rate report and the permission diff together before deprecating a field? This teaches evidence-based data hygiene and access review.

⭐ Best Practices & Coaching Tips

For Admins

Protect production inline edits: Always disable inline editing in Settings > Org Management for production orgs. Use dev/sandbox only for testing.
Bookmark your most-used SOQL queries: The SOQL Builder supports multi-tab editing — create tabs for common queries (inactive users, duplicate detection, etc.)
Use Command Palette for quick setup navigation: Instead of clicking through Setup, use Ctrl+K to search API names and jump directly.
Export labels in bulk: Org Tools > Custom Labels lets you export all labels at once — translate offline, import back. Much faster than manual updates.

For Developers

Use LWC Explorer to trace requests: Filter by Apex vs. UI API vs. GraphQL to understand which layer is slow. Screenshot the trace for code reviews.
Compare SOQL vs. GraphQL results: Use both builders to query the same object — GraphQL is often more efficient for related fields.
Bulk-scan records with IDs: Got a list of problematic record IDs? Use Records > Bulk Scan (up to 200 IDs) to inspect them all at once. Export the results.
Set custom keyboard shortcuts: In Settings > General, configure a shortcut for "Toggle Show All Data" (no default exists) so you can inspect pages instantly.

For Trainers

Teach surfaces first, features second: Most user confusion comes from not knowing which surface to use, not from missing features. Start with Launcher → Workspace → Overlays.
Use the Quiz platform: After each lab, have users take a related quiz question to reinforce learning. Track leaderboard progress.
Customize the sidebar for your org: Settings > Sidebar lets you configure shortcuts per role. Create role-specific sidebar layouts to reduce cognitive load.
Ask the decision-tree question: After training, ask: "When would you use Show All Data vs. Records?" or "Command Palette vs. Schema?" If they can answer clearly, they understand the model.

Universal Best Practices

One surface at a time: Don't try to use the Launcher, Workspace, and overlays simultaneously for a single task. Pick the right surface first.
Reset to defaults if confused: Settings > Advanced > Cache Management can clear local storage and reset defaults. Safe for troubleshooting.
Use dark mode in long sessions: Settings > Appearance > Dark Mode reduces eye strain during extended debugging.
Backup settings regularly: Settings > Advanced > Backup lets you export your config. Useful before major browser updates or switching machines.
Trust the safety prompts: v2.10.0 hardened security across the board — XSS and SOQL-injection fixes, cross-org state isolation so one org's data never bleeds into another, and production-edit confirmation on the SOQL results grid. The confirmations exist to protect you; read them before you click through.

Final coaching principle: The best learners ask "when should I use this?" not "how do I use this?" If you can help your users ask the right question first, feature mastery follows naturally.