experience-ui-bundle-salesforce-data-access

Generate schema-grounded GraphQL queries and mutations for Salesforce UI bundle data access.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill experience-ui-bundle-salesforce-data-access
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experience-ui-bundle-salesforce-data-access
Source: https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG/tree/main/.agents/skills/experience-ui-bundle-salesforce-data-access
Command: npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill experience-ui-bundle-salesforce-data-access

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It removes the guesswork from Salesforce data access in UI bundles by turning record reads, writes, caching, and refresh behavior into a safe, repeatable workflow.

Core Features & Use Cases

  • Record Querying: Build schema-verified GraphQL queries for Salesforce objects, lists, details, and aggregates.
  • Record Mutations: Create, update, and delete records with the current platform SDK and correct mutation shapes.
  • Freshness Controls: Use cache policies, refresh handles, and subscriptions to keep UI data current without reinventing caching.
  • Migration Support: Convert legacy data SDK call sites to the new namespace-based API.
  • Use Case: A UI bundle needs to show Account data, update a Contact, and refresh the list after save while respecting field-level security.

Quick Start

Ask the skill to generate a Salesforce UI bundle data access workflow for the records, schema, and refresh behavior you need.

Frequently Asked Questions about experience-ui-bundle-salesforce-data-access

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build safe GraphQL queries for Salesforce UI bundle data access?

Salesforce UI bundle data access generates schema-verified GraphQL queries for objects, lists, and aggregates. It ensures reads match the current schema exactly, preventing runtime errors by validating record structures before querying.

How do I handle Salesforce record caching and refresh behavior in a UI bundle?

Salesforce data caching in UI bundles uses deliberate cache policies, refresh handles, and subscriptions. This approach keeps UI data current without manual refresh logic, applying explicit cache control to maintain record freshness.

Can I create and update Salesforce records with field-level security in a UI bundle?

Yes, Salesforce record mutations for creating, updating, and deleting records use the current platform SDK. The workflow respects field-level security by applying FLS-aware optional fields, ensuring safe writes across the schema.

What is the best way to migrate legacy data SDK call sites to the new Salesforce API?

Migrating legacy data SDK call sites involves converting them to the new namespace-based API. This Salesforce data access workflow targets old call sites directly, replacing them with generated platform-sdk query and mutate calls.

How does pagination work when querying Salesforce record lists in a UI bundle?

Querying Salesforce record lists requires explicit pagination. The generated GraphQL queries include pagination parameters directly, ensuring the UI bundle fetches records in controlled batches rather than loading entire datasets.

Why do I need generated GraphQL types for Salesforce data access?

Generated GraphQL types provide schema-grounded structures for Salesforce record queries and mutations. They enforce type safety during data access, ensuring the UI bundle reads and writes match the exact platform-sdk expectations.