Using Ui Bundle Salesforce Data

This walks Claude through Salesforce data access inside UI bundles using the Data SDK and GraphQL. It's heavily opinionated because the Salesforce GraphQL implementation has sharp edges: HTTP 200 doesn't mean success, missing the @optional directive breaks queries when users lack field permissions, and the schema is 265K lines you need to search with a script instead of opening directly. The precondition checks are useful since you can't write queries until schema.graphql exists and custom objects are deployed. If you're building forms or pages that touch Salesforce records in a UI bundle, this keeps you from making the mistakes that cause silent failures. The REST vs GraphQL decision tree and mutation syntax rules are the most immediately practical parts.