🦞 D365 Tools

A lightning-fast CLI to browse Dataverse schema and analyze dependency impact before you break production.

---

🎬 Quick Demo

[INSERT: 10-second terminal GIF showing d365ai impact search account.tvs_city in action]

Figure: Finding all uses of a field in 2 seconds

---

✨ Features

🗂️ Schema Management

• Browse Schema — Explore entities, attributes, and relationships
• Search Entities — Find entities and fields instantly
• Export Schema — Export as JSON, Markdown, or CSV
• Delta Sync — 10-20x faster incremental updates (3-5s vs 60s)
• Multi-Environment — Manage connections to Dev, Test, Prod
• VS Code Extension — Tree view, search panel, Code Lens

🔍 Impact Analysis

• Dependency Detection — Find all uses of an entity or field
• Multi-Source Scanning:
  • Dataverse API (relationships, workflows, business rules)
  • JavaScript web resources
  • C# plugin code (Azure DevOps integration)
• Field-Level Analysis — Search specific field usage (e.g., account.tvs_city)
• Code Context — Shows line numbers and code snippets
• Visual Graphs — Interactive dependency visualization
• Impact Reports — Markdown/JSON reports for change review

---

⚡ Quick Start (5 Minutes)

Prerequisites

• ✅ Node.js 18.0+
• ✅ Dataverse environment URL (e.g., https://yourorg.crm.dynamics.com)
• ✅ Azure AD App Registration (for non-interactive login) OR use interactive device flow

Install

# Clone and install locally
git clone https://github.com/AdventureAdept/d365-tools.git
cd d365-tools
npm install
npm link

Connect

d365ai env connect

You'll be prompted for:

• Organization URL
• Client name (friendly name for this connection)
• Interactive login via device code (or provide Client ID/Secret for service principal)

Pull Schema

d365ai schema pull

Search & Analyze

# Search for entities
d365ai search entity account

# Find field dependencies (prevents breaking changes!)
d365ai impact search account.tvs_city

# Analyze full impact before renaming
d365ai impact analyze account --full

---

📸 Visual Proof

VS Code Extension

[INSERT: Screenshot of VS Code Tree View showing entity browser]

Figure: Browse Dataverse schema directly in VS Code

Dependency Graph

[INSERT: Screenshot of interactive dependency graph visualization]

Figure: Visual impact analysis before schema changes

Terminal Demo

[INSERT: GIF created with vhs showing delta sync speed]

Figure: Delta sync completes in 3 seconds (vs 60 seconds for full sync)

---

🏗️ Architecture

.
├── 📂 src
│   ├── 🔌 api/          # Dataverse & Azure DevOps connectivity
│   ├── 🛠️ commands/     # CLI entry points (d365ai)
│   ├── 🗂️ schema/       # Schema management (browse, search, export)
│   └── 🔍 impact/       # Impact analysis (dependencies, graphs)
├── 💻 vscode-extension/ # Tree view, WebView, Code Lens
├── 📚 docs/
│   ├── tutorials/       # How-to guides
│   ├── reference/       # CLI flags, API docs
│   └── explanation/     # Architecture, design decisions
└── 🧪 tests/            # Unit & Integration (Vitest)

---

🚀 Performance

Delta Sync: 10-20x Faster

Sync Type	Time	API Calls
Full Sync	60s	500+
Delta Sync	3-5s	10-20

How? Uses ETag headers and delta-token tracking to fetch only changed metadata since last sync.

---

🔒 Security

Token Storage

✅ OS Keychain/Secret Store - Tokens encrypted using:

• Windows: Credential Manager
• macOS: Keychain
• Linux: libsecret (GNOME Keyring/KWallet)

Never stored in plain text!

Authentication

• MSAL.js with device flow (interactive)
• Service Principal support (client credentials)
• Automatic token refresh (no manual re-auth)

---

🎯 Common Workflows

🔧 Rename Field Safely

Problem: Need to rename account.tvs_city to account.tvs_municipality

# 1. Find all usages first
d365ai impact search account.tvs_city --show-code

# 2. Review output (plugins, web resources, workflows)
# 3. Update code, test, then rename in Dataverse

Why: Prevents 5 hidden dependencies from breaking production.

---

🗑️ Delete Entity Safely

Problem: Is it safe to delete tvs_log entity?

# 1. Analyze full impact
d365ai impact analyze tvs_log --full

# 2. Review: Shows 3 plugins, 2 workflows, 1 view
# 3. Remove dependencies first, then delete

Why: Prevents orphaned code and broken workflows.

---

📋 Code Review - Audit Field Access

Problem: Who's accessing account.creditlimit?

# Audit field usage with code context
d365ai impact search account.creditlimit --show-code

Check: Validation, security roles, logging.

---

🔍 Find & Browse Schema

Problem: Need logical name for "city" field

# Search across all entities
d365ai search field city

# Or search in specific entity
d365ai search field city --entity account

Why: Faster than opening D365 or XrmToolBox.

---

📖 Documentation

Type	Content
📚 Tutorials	Connect to Dataverse • Analyze Impact • Before Renaming Field
📋 Reference	CLI Commands • API Reference
💡 Explanation	Architecture • Delta Sync Design

---

🛠️ Development Setup

Clone & Install

git clone https://github.com/AdventureAdept/d365-tools.git
cd d365-tools
npm install

Link Locally (for testing)

npm link
d365ai --version  # Test your local changes

Run Tests

npm test

Build

npm run build

---

🤝 Contributing

Quick Start for Contributors

1. Fork the repository
2. Create branch: git checkout -b feature/your-feature
3. Make changes and test locally with npm link
4. Run tests: npm test
5. Submit PR with description of changes

Development Tips

• Use npm link to test CLI changes in real-time
• Run npm run watch for auto-rebuild during development
• Add tests for new features (Vitest)
• Update docs in the same PR as code changes

---

📄 License

MIT License - see LICENSE for details.

---

🙏 Acknowledgments

• Built with Microsoft Dataverse Web API
• Uses MSAL.js for authentication
• VS Code Extension API

---

📞 Support

Questions?

• 📖 Read the docs
• 🐛 Open an issue
• 💬 Discussions

---

Made with ❤️ for Dynamics 365 developers