---
id: "c29ebb76-b011-4b3e-be84-a1822e34db6b"
name: "Demoable mappings are org-specific (SOQL check)"
micro_summary: "Which (record type -> queue) mappings are filmable depends on org data, not the flow: a missing queue shows no-reassignment on camera. jtbsandbox has 5 RTs, EMR_Support absent; UAT differs (no Clinical Reporting queue, has EMR_Support). recordTypeIds drift on refresh — SOQL per org, never hardcode."
status: "resolved"
see_also: []
scope: "Which (record type -> queue) mappings can actually be filmed depends on the target org's data (present record types + queues that own Cases), not on the flow. How to (re)check per org."
---
## Why this matters

A correct flow still shows "no reassignment" on camera if the target queue or record type is missing in that org. So the demoable set is a property of the ORG, not the flow. Always re-run the reality check before filming a new org.

## SOQL reality check (per org)

```
-- record types present on Case
SELECT DeveloperName FROM RecordType WHERE SobjectType='Case'
-- queues that exist AND own Cases
SELECT Queue.DeveloperName FROM QueueSobject WHERE SobjectType='Case'
-- record type Ids for direct-URL creation (these DRIFT on sandbox refresh)
SELECT DeveloperName, Id FROM RecordType WHERE SobjectType='Case'
```

## jtbsandbox snapshot (2026-07-10)

Present + filmable: Client Services, Phlebotomy, Billing, Clinical Reporting, EMR Integration Request (form too heavy — see sibling discard). **EMR_Support ABSENT** (record type + Case queue) — matches Jack's Slack note that EMR_Support exists in UAT/Prod only.

## UAT will differ

Per Jack's Slack: UAT LACKS the Clinical Reporting queue (would show no-reassignment on camera) and HAS EMR_Support. Re-query, never carry jtbsandbox Ids/mappings over.