docs: document special Dataverse type formats in data command --data (#63)#169
Open
zekelinAlex wants to merge 1 commit into
Conversation
Member
|
We want to replace this custom JSON with CMT format. the CLI should provide better support for composing the CMT format, which should be consistently used across all commands working with data |
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.
Closes #63
The
--dataoption onrecord create/updateandbulk create/update/upsertdidn't explain how to format special Dataverse column types, so MCP agents had to discover by trial and error that option sets go as plain integers and lookups as GUID strings. Since the MCP input schemas are generated from the sameCliOptionattributes, the gap was visible both in CLI help and in the tool descriptions.This adds the formats to the
--datadescription on all five commands: OptionSet as an integer, Lookup as a GUID string or{Id,LogicalName}object, Money as a decimal, Boolean as true/false, DateTime as an ISO-8601 UTC string.