#Salesforce Developer475 人がディスカッション中

QueryException "No such column 'Name' on entity 'EmailTemplate'" + "Variable does not exist: tmpVar1" — only at API v67, works fine at v44** 

Hi all, 

I'm hitting a strange `System.QueryException` in one sandbox but not others, and I'd like a sanity check on whether this is a known platform behavior or something in my code. 

**The error:** 

``` 

System.QueryException: No such column 'Name' on entity 'EmailTemplate'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names. 

System.QueryException: Variable does not exist: tmpVar1 

``` 

**The query (inside a class method):** 

```apex 

private static Map<String, Id> getEmailTemplates() { 

    Map<String, Id> emailTemplateByName = new Map<String, Id>(); 

    for (EmailTemplate emailTemplate : [ 

        SELECT Id, Name 

        FROM EmailTemplate 

        WHERE IsActive = TRUE 

        AND (Name = :IN_EMAIL_TEMPLATE 

             OR Name = :BG_EMAIL_TEMPLATE 

             OR Name = :SK_EMAIL_TEMPLATE 

             OR Name = :PK_EMAIL_TEMPLATE 

             OR Name = :SS_EMAIL_TEMPLATE 

             OR Name = :EI_EMAIL_TEMPLATE 

             OR Name = :HT_EMAIL_TEMPLATE 

            ) 

    ]) { 

        emailTemplateByName.put(

); 

    } 

    return emailTemplateByName; 

} 

``` 

**What I'm seeing:** 

- This class is compiled at API v44.0 in our Dev and Production orgs, and the query runs fine there. 

- The same class in our UAT sandbox is compiled at API v67.0 (v44 isn't even selectable there anymore — the version picker only goes back to 63), and this exact query throws the error above every time. 

- `Name` is obviously a valid standard field on `EmailTemplate`, so the "no such column" message seems misleading — combined with the `tmpVar1` error right after it, it feels like something is going wrong internally when the query tries to evaluate a long chain of `Name = :bindVar OR Name = :bindVar ... conditions on the same field, rather than an actual field-access problem. 

**My questions:** 

1. Has anyone else run into this specific combination of errors with long OR-chains of bind variables on the same field, and does it ring a bell as a known API-version-related SOQL behavior? 

2. I'm planning to rewrite this as `Name IN :templateNames` (a `Set<String>`) instead of the OR-chain — is that a safe, reliable workaround, or is there a better-known fix? 

3. Is this worth filing as a Known Issue with Salesforce Support, or is this expected/documented behavior I'm just not aware of? 

Any pointers appreciated — thanks! 

As we race toward Dreamforce Trailblazer Bootcamp on September 12-14, lace up every Tuesday, Wednesday, and Thursday for ✨ Trailblazer Track Meets, ✨ where we’re sharing details about each of our bootcamp tracks and the instructors teaching them! 👟

We’re off to a running start with the Agentforce Service Specialist track, where instructor Alok Agarwal will guide students through building, customizing, and deploying AI-powered service agents from scratch. Don’t get left in the dust! 💨

On your marks, get set… register: https://sfdc.co/DF26TrailblazerBootcamp

@* Trailhead Official * @* Trailhead Academy * @Trailblazer Community Cove @* Salesforce Developers * @* Salesforce Administrators * #Salesforce #Certifications #Trailhead #TrailblazerCommunity #Agentforce #Salesforce Developer #Salesforce Admin

🤖 Build real expertise for the Agentic AI era. 

Trailhead Journeys are now available across 10 Salesforce products empowering you to move from fundamentals to advanced expertise with a progressive, step-by-step curriculum. 

Newly added journeys:

• ⚡ Headless 360 platform
• 📈 Agentforce Marketing
• 👥 Agentforce Service 
• 🛒 Agentforce Commerce
• 🔌 Omnistudio

Skip the search. Start the journey 👉 trailhead.com/trailhead-journeys