docs(transaction-api): correct JobContractPricing update guidance#45
Open
mrwuss wants to merge 1 commit into
Open
docs(transaction-api): correct JobContractPricing update guidance#45mrwuss wants to merge 1 commit into
mrwuss wants to merge 1 commit into
Conversation
The 'Known Limitations' note previously claimed Status="Existing" returns 500 and pointed readers to the Interactive API for modifications. That misled the reader -- the Transaction API does update existing JobContractPricing records when called with Status="New" and FORM key fields in Edits (rather than Keys). Adds an "Updating an Existing Contract" subsection with a verified payload shape and notes on Source -> Price pricing_method conversion. Restates the Status="Existing" 500 caveat under Known Limitations but as a "use New instead" note, not a "use Interactive API" deflection. Empirically verified by running 173 price updates against contract A120-12 on a production tenant -- all succeeded with OData verification. Closes #44 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Status=\"New\", FORM keys viaEdits,end_daterequired).Status=\"Existing\"is invalid (not a platform-wide write ban) -- use\"New\"for both create and update.pricing_methodSource -> Price conversions work in the same call (dormantsource_price/multiplierremain on the row)./api/v2/transaction/getretrieve example so readers can fetch FORM values before submitting an update.Empirically verified by running 173 successful price updates against contract
A120-12on a production tenant (HTTP 200,Summary.Succeeded=1, OData re-read confirms each new price).Closes #44
Test plan
docs/03-Transaction-API.mdand confirm the new subsection appears between Commission Costs and Known Limitations.[Updating an Existing Contract](#updating-an-existing-contract)resolves.\xf0\x9f\xa4\x96 Generated with Claude Code