feat: route ERP via dataverse CLI across overview/query/data/connect#90
Open
athanipavan wants to merge 7 commits into
Open
feat: route ERP via dataverse CLI across overview/query/data/connect#90athanipavan wants to merge 7 commits into
athanipavan wants to merge 7 commits into
Conversation
added 3 commits
June 5, 2026 22:58
Treats Finance & Operations as an app on Dataverse, not a separate product. Adds ERP triggers (frontmatter, Plugin Covers note, Dataverse CLI row in capability matrix, routing pointers in PAC CLI row + tool priority). Detail lives in references/erp-target.md to keep the body close to Anthropic's Level 2 budget. Version 1.5.0 -> 1.5.1. Known: body is 5387 tokens (cap 5000). main was already 5186 over; this PR adds ~200. Opening for internal review of the integration approach — body-trim is a separate pass.
Conflicts: - plugin.json (x2): take main's expanded plugin description, keep 1.7.0 version - dv-connect SKILL.md: combine main's Step 5 failure-list update with the ERP detection/smoke-test pointers (extracted to references/erp-detection.md to stay close to budget) Budget status after merge: - dv-connect 5017/5000 (+17): the single line linking to erp-detection.md. Pre-PR baseline was 4999/5000 on main. - dv-overview 5395/5000 (+395): pre-existing 5256 overrun on main + 139 for ERP capability matrix row and tool-priority qualifier. Trimmed from +244 to +139 by inlining links and removing redundant prose.
Author
|
@microsoft-github-policy-service agree company="Microsoft" |
added 2 commits
June 23, 2026 15:04
# Conflicts: # .cursor-plugin/marketplace.json # .github/plugin/marketplace.json # .github/plugins/dataverse/.claude-plugin/plugin.json # .github/plugins/dataverse/.codex-plugin/plugin.json # .github/plugins/dataverse/.cursor-plugin/plugin.json # .github/plugins/dataverse/.github/plugin/plugin.json
These were inadvertently swept in by 'git add -A' during the earlier merge conflict resolution. The plugin's real auth.py lives under .github/plugins/dataverse/scripts/ and is unchanged in this PR.
jeffandms
reviewed
Jun 23, 2026
jeffandms
requested changes
Jun 23, 2026
jeffandms
left a comment
jeffandms
left a comment
There was a problem hiding this comment.
We must remove all references to "Uno" before completing this PR.
added 2 commits
June 24, 2026 11:34
Per reviewer feedback on PR #90: UNO is an internal-only codename and must not appear in externally published skill content. Substituted with phrasing that describes the actual configuration (F&O linked to / provisioned on top of the same Dataverse env).
Per reviewer follow-up on PR #90: pick one term and stick with it. Standardized on 'ERP' as the lead term, with '(Finance and Operations)' as the first-mention expansion in each skill / reference file. Replaced all subsequent 'F&O' and 'Finance & Operations' occurrences with 'ERP'. Single remaining 'F&O' is in a trigger-word list documenting input variants users may type, not descriptive prose.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds first-class ERP (F&O) routing to the Dataverse skills plugin without spawning
erp-*sibling skills. ERP is treated as a target variant of the existing skills:dv-overviewroutes ERP traffic,dv-queryanddv-datadocument the CLI-based ERP path, anddv-connectdetects ERP linkage on UNO environments and surfacesERP_URLin.env.The approach is CLI-only: ERP work goes through
dataverse --target erp,dataverse api invoke --target erp,dataverse erp batch ..., anddataverse mcp <fnoUrl>. No PythonErpClientis introduced;auth.pyis unchanged. The DataverseCLI repo already provides full ERP coverage (CRUD with composite keys +--cross-company, F&O custom services, batch jobs, ERP MCP auto-routing), so the plugin's job is to teach the agent how to route to it correctly.Highlights
dv-overview: ERP added to the trigger list; new Dataverse CLI row in the capability matrix; tool-priority paragraph notes the ERP tier (no Python SDK). Full detail in newreferences/erp-target.md.dv-query: SDK-First Rule clarifies ERP is a separate path; newQuerying ERP datasection with CLI examples and a Dataverse-vs-ERP differences table (PascalCase entity sets, composite keys withdataAreaId,--cross-company, no FetchXML/SQL/``).dv-data: newWriting ERP datasection covering MCP / CLI / DMF tiers with a key-differences table.dv-connect: Step 2 detects ERP viapac org whofirst, falls back todataverse org who --environment <DATAVERSE_URL> --json(--environmentpassed explicitly because DV CLI keeps its own active profile separate from PAC). Step 3 writesERP_URLto.envwhen present. Step 5 smoke-tests ERP withdataverse data query --target erp --table Currencies --top 1. Detail extracted to newreferences/erp-detection.mdto stay close to the body-token budget.Version
1.6.0 → 1.7.0 (MINOR — backward-compatible capability addition). All four version fields updated;
version_bump_check.pypasses.Validation
python .github/evals/static_checks.py: every check passes exceptEVAL-BUDGET-02:dv-overviewbody is 5395/5000 tokens. Pre-PR baseline on main is 5256; my additions account for ~139 tokens (Dataverse CLI matrix row and tool-priority qualifier) — trimmed down from an initial +244 by inlining links and folding prose intoreferences/erp-target.md.dv-connectbody is 5017/5000 tokens. Pre-PR baseline on main is 4999 (already 1 below cap); the +17 is a single line linking to the newreferences/erp-detection.mdplus surrounding prose. Reducible further only by removing the body pointer entirely, which would defeat the agent's ability to discover the reference.dv-overviewoverrun is best treated as a follow-up.dataverse.exe: every flag and subcommand the skills prescribe (data query/get/create/update/delete/upsert --target erp,--cross-company,api invoke --target erp --service-group ... --service ...,erp batch list|cancel,mcp <fnoUrl>,org who --environment ... --json) matches the CLI's own--helpoutput.dataverse data query --target erp --table Currencies --top 1against the UNO env) blocked locally by DNS to the F&O host; the CLI built the correct URL and authenticated correctly.Out of scope (deferred)
dv-admingainingdataverse erp batchrouting.api invoke).dv-overviewbody overrun under 5000 tokens.get_erp_url()toauth.pyif a real bulk-Python need emerges).Closes the abandoned attempt in #82.