AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Salesforce List Views

skill-jhillock1-salesforce-claude-skills-salesforce-list-views · by jhillock1

Create and modify list views — column references, filter logic, queue-based views

↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-jhillock1-salesforce-claude-skills-salesforce-list-views

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Salesforce List Views? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Salesforce List Views

When to Use

  • Creating new list views for an object
  • Adding/removing columns from list views
  • Setting up queue-specific list views
  • Fixing column reference errors

Critical Knowledge

Column API Names Are NOT Always Obvious

List view columns use a special naming convention that differs from field API names.

Common Case columns: | Display Name | Column API Name | Notes | |-------------|----------------|-------| | Case Number | CASES.CASENUMBER | | | Subject | CASES.SUBJECT | | | Status | CASES.STATUS | | | Priority | CASES.PRIORITY | | | Owner | CORE.USERS.ALIAS | Owner alias | | Owner (Full Name) | OWNER.ALIAS | Alternative | | Created Date | CASES.CREATEDDATE | | | Date/Time Opened | CASES.CREATEDDATEDATE_ONLY | | | Case Origin | CASES.ORIGIN | | | Account Name | ACCOUNT.NAME | Via Account lookup | | Contact Name | NAME | ⚠️ NOT CASES.CONTACT |

Custom fields: Use the API name directly: Waiting_On__c, Needs_Attention__c

⚠️ Some standard fields DON'T work as list view columns. If deploy fails with a column reference, remove it and try an alternative.

List View XML Template


    Needs_Attention
    Needs Attention
    Mine
    CASES.CASE_NUMBER
    CASES.SUBJECT
    CASES.STATUS
    Waiting_On__c
    CORE.USERS.ALIAS
    CASES.CREATED_DATE
    
        Needs_Attention__c
        equals
        1
    
    
        CASES.STATUS
        notEqual
        Closed,Merged

File location: force-app/main/default/objects/Case/listViews/Needs_Attention.listView-meta.xml

Filter Scope Options

| ` | Meaning | |-----------------|---------| | Mine | Records owned by current user | | Queue | Records owned by a specific queue | | Everything | All records visible to user | | MineAndMyGroups` | User's records + their queue records |

Queue-Specific List View


    Queue_Customer_Support
    Queue: Customer Support
    Queue
    Customer_Support
    CASES.CASE_NUMBER
    CASES.SUBJECT
    CASES.STATUS
    CORE.USERS.ALIAS
    CASES.CREATED_DATE
    
        CASES.STATUS
        notEqual
        Closed,Merged

Key: `` uses the Queue's DeveloperName, not the display label.

Find queue developer names:

sf data query --query "SELECT Id, Name, DeveloperName FROM Group WHERE Type = 'Queue'" --target-org

Recipes

Create a List View

  1. Write the XML file to force-app/main/default/objects//listViews/.listView-meta.xml
  2. Deploy:

``bash sf project deploy start --source-dir force-app/main/default/objects/Case/listViews/Needs_Attention.listView-meta.xml --target-org ``

Add a Column to Existing List View

  1. Retrieve it:

``bash sf project retrieve start --metadata "ListView:Case.Needs_Attention" --target-org ``

  1. Add a `` element (order = display order)
  2. Redeploy

Validate List View Shows Correct Data

# Replicate the filter logic in SOQL
sf data query --query "SELECT CaseNumber, Subject, Status, Owner.Name FROM Case WHERE Needs_Attention__c = true AND OwnerId = '' ORDER BY CreatedDate DESC" --target-org

Compare the SOQL results with what appears in the list view UI.

Common Pitfalls

| Pitfall | Fix | |---------|-----| | Column "not found" on deploy | Check the column API names table above; some standard fields have non-obvious names | | CASES.CONTACT doesn't work | Use NAME for Contact Name | | Queue list view is empty | Check ` uses DeveloperName not label; verify queue exists | | Filter not working | Boolean fields use 1/0 not true/false | | Custom field not showing | Use API name directly: MyField_c` (no prefix) |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills