Dynamics GP Private AI Layer Blueprint Generator
This generator produces an architecture plan for a private AI assistant on Dynamics GP, built around curated SQL views for reads and supported integrations for any write. It is meant to be handed to IT, finance and security.
Fill in
Dynamics GP Private AI Layer Blueprint Generator
GP Private AI Layer Plan: Lakeside Distribution Co
System: Dynamics GP 18.4 on SQL Server 2017, hosting: On-prem server. Scale: 60 named users, 2 company databases plus the DYNAMICS system database. Target go-live: Q3 2027.
Context
Open receivables and payables questions, inventory by site, open purchase orders, month-end variance explanations, vendor document search.
Goal: ask questions in plain language and get answers sourced from GP and documents, with all processing on Lakeside Distribution Co infrastructure.
Components
| Component | Design | Notes |
|---|---|---|
| Data access path | Read-only replica of DYNAMICS and company databases; curated views over master, open, work and history tables | Union open and history tables where needed |
| Write path | eConnect or Integration Manager after human approval; none in phase 1 | No SQL writes |
| Retrieval index | Vendor documents, item notes, scanned files on shares, report text | Local vector store |
| Model serving | Open-weight model on vLLM or Ollama, GPU: One 24 GB class GPU | Separate host from the GP SQL server |
| Tool server | MCP server with named read actions, parameter validation, row limits | Company database chosen from the user's allowed list |
| Identity and permissions | Map user to GP security roles and company access; filter in tool code | Do not reuse GP SQL logins |
| Audit | Local log of question, calls, queries, answer, approver | Retain per policy |
Security controls
| Requirement | Control |
|---|---|
| Never leaves site: Bank account numbers, payroll, customer credit terms, vendor contracts. | No external APIs; inference and index inside the On-prem server boundary; blocked egress |
| Sensitive tables | Payroll and bank views excluded by default and added only with owner sign-off |
| Least privilege | Dedicated SELECT-only SQL login on curated views |
| Write-back | Draft, approve, then submit through eConnect with the approver recorded |
| Traceability | Every figure links to the view and filter that produced it |
Three-phase rollout
| Phase | Scope | Exit criteria |
|---|---|---|
| 1. Read-only questions | Finance and purchasing pilot, curated views | Controller signs off a test set reconciled to GP reports |
| 2. Drafts | Draft invoices, vendor emails and summaries for review | Low rework rate |
| 3. Approved actions | Few actions through eConnect after approval | Audit log reviewed by IT and finance |
Open questions for IT
1. Can a readable replica or restore be provided for DYNAMICS and each company database? 2. Which third-party add-ons have their own tables? 3. How are GP users and roles managed, and are broad roles common? 4. Is multi-currency in use and how should amounts be presented? 5. Which integration methods are installed and supported for write-back? 6. What are the support and migration plans for GP?
A starting plan. Verify table contents, document type logic and integration support against your GP build and add-ons.
Get an expert review of your GP AI blueprint
Optional: send the exported plan for comments on risks, views and sequencing. The generator stays free.
Optional. The tool and every export work without this. No spam.
How to use the generator
Enter your GP version, SQL Server version, user count and the number of company databases. Describe the first questions finance and purchasing want answered and list the data that must not leave the site. The plan repeats those restrictions in its controls table and proposes a rollout that proves accuracy before enabling any write.
- Count every company database
- List add-on modules with own tables
- Name sensitive tables to exclude
- Agree the test set with the controller
The design behind the plan
GP data sits in SQL Server across a system database and one database per company, with separate open, work and history tables. The plan builds curated views over those tables, runs the model on a separate host and routes any writes through eConnect or another supported method after human approval.
Common mistakes
Using only open tables, reusing GP user logins for the assistant, ignoring multi-currency columns and treating document type codes as universal. Each is covered by the open questions and controls so they are decided before build starts.
Frequently Asked Questions
Does this replace SmartList or SSRS?
No. Those remain good for fixed questions. The assistant adds ad hoc questions and document search on top of the same data.
Can the assistant post transactions?
Only in a late phase, after a person approves a draft, and through a supported integration such as eConnect. The default plan is read-only.
Does it handle multiple companies?
Yes. The tool server selects a company database from the user's allowed list, and the plan notes this as a control.
Is data uploaded anywhere?
No. The document is generated in your browser.
If you want an outside review of this plan against your GP environment, Netray can go through it with your team.
Related Tools
Dynamics GP AI Assistant Sizing and Value Calculator
Size a private AI assistant for Dynamics GP: GPUs, index and monthly value from users and questions per day.
Microsoft DynamicsDynamics GP SQL Table Reference (IV00101, SOP10100, POP10100)
Searchable reference of common Dynamics GP tables with module, purpose and work, open or history status.
Microsoft DynamicsGP Open Transactions SQL Query Generator
Build read-only SQL for open SOP orders, open RM receivables and open PM payables in a GP company database for migration extracts.
Microsoft DynamicsDynamics GP End of Support Migration Assessment
Ten-question readiness score for Dynamics GP customers who need a decision on what comes after GP.
More On-Prem AI tools
See all- On-Prem LLM Total Cost of Ownership Calculator
- GPU Sizing Calculator for LLM Inference
- On-Prem vs Cloud AI Cost Comparison Calculator
- Self-Hosted LLM Hardware Estimator
- Air-Gapped AI Readiness Assessment
- LLM API vs Self-Hosted Cost Calculator
- RAG Infrastructure Sizing Calculator
- Open-Weight Model Selector
- On-Prem AI ROI Calculator
Go Deeper
On-Prem LLM Deployment Architecture: Reference Guide
Reference architecture for on-prem LLM deployment: inference servers, GPU sizing, RAG pipelines, and security zones for regulated manufacturers.
A Data Governance Framework for Private AI
A practical data governance framework for private AI: classification, access controls, retention, and audit patterns that satisfy CMMC 2.0 and ITAR.
Keep exploring
Free tools
- Dynamics GP AI Assistant Sizing and Value CalculatorSize a private AI assistant for Dynamics GP: GPUs, index and monthly value from users and questions per day.
- Dynamics NAV Private AI Layer Blueprint GeneratorDescribe your NAV environment and get a shareable plan for a private AI assistant: components, security controls, 3-phase rollout and open questions.
- Dynamics AX 2012 Private AI Layer Blueprint GeneratorFill in your AX 2012 environment and get an architecture plan for a private AI assistant, with components, controls, a 3-phase rollout and open questions for IT.
ERP fixes and how-tos
- Adding a Private AI Layer to Dynamics GP On-PremAdd AI to Dynamics GP on-prem without cloud: curated SQL views, eConnect for writes, retrieval index, local LLM, mirrored GP security, approved write-back.
- Dynamics GP POP Tables: Purchase Order Processing Reference and Sample SQLReference for Dynamics GP Purchase Order Processing tables: POP10100, POP10110, POP30100, POP30110, receipt tables, key joins and sample SQL queries.
- Adding a Private AI Layer to Dynamics NAV On-PremAdd AI to Dynamics NAV on-prem without moving data: SQL replica, web services, retrieval index, local LLM, mirrored NAV permission sets, approved write-back.
Integrations
- How to add AI agents to Microsoft Dynamics GPHow to add AI agents to Microsoft Dynamics GP: a read-only tool layer over SQL views, eConnect for approved writes, and human sign-off, on-prem if needed.
- How to connect Claude to Microsoft Dynamics GPUse Claude with Dynamics GP through an MCP server over read-only SQL views, via the Anthropic API, Bedrock or Vertex, or keep everything on-prem with open models.