add-dataverse

**📋 Shared Instructions: [shared-instructions.md](${CLAUDE_PLUGIN_ROOT}/shared/shared-instructions.md)** - Cross-cutting concerns. **References:** - [dataverse-reference.md](./references/dataverse-reference.md) - Picklist fields, virtual fields, lookups, form patterns (CRITICAL) - [api-authentication-reference.md](./references/api-authentication-reference.md) - Dataverse API auth, token, publisher prefix - [table-management-reference.md](./references/table-management-reference.md) - Query, create, extend tables and columns - [data-architecture-reference.md](./references/data-architecture-reference.md) - Relationship types, dependency tiers # Add Dataverse Two paths: **existing tables** (skip to Step 5) or **new tables** (full workflow). ## Workflow 1. Plan → 2. Setup API Auth → 3. Review Existing Tables → 4. Create Tables → 5. Add Data Source → 6. Review Generated Files → 7. Build --- ### Step 1: Plan Check memory bank for project context. Ask the user: 1. Which Dataverse table(s) do they need? (e.g., `account`, `contact`, `cr123_customentity`) 2. Do the tables **already exist** in their environment, or do they need to **create new** ones? **If tables already exist:** Skip to Step 5. **If creating new tables:** - Ask about the data they need and design an appropriate schema - Use standard Dataverse tables when appropriate (`contact` for people, `account` for organizations) - Build a dependency graph -- see [data-architecture-reference.md](./references/data-archi...