Changes dataset metadata or reports the content saved by the client.
Null fields stay unchanged.
A content update needs baseContentHash from the version that you opened.
Non-null schema, rowCount, columnCount, or contentHash triggers this check.
Null or empty baseContentHash matches only a null or empty stored hash.
Metadata-only changes do not require a matching base hash.
A content update returns 409 if the stored content hash no longer matches baseContentHash.
Updates without a replacement hash, or with the same hash, can still match the same base.
A new name must be unique by exact spelling in the project. Letter case matters.
The API stores these client-reported values as sent.
It does not compare them with Storage rows.
If a schema change affects variables that linked cases use, send confirm=true to continue.
Schema updates leave step text unchanged.
Send the saved content to Storage before this request.
Schema errors use code suffix 2703; reported limit errors use suffix 2702.
Requires the TestCase:Update permission.