jaz-clio 5.47.0 → 5.47.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/assets/skills/api/SKILL.md +1 -1
- package/assets/skills/api/references/endpoints.md +1 -1
- package/assets/skills/api/references/errors.md +4 -3
- package/assets/skills/cli/SKILL.md +1 -1
- package/assets/skills/conversion/SKILL.md +1 -1
- package/assets/skills/jaz-kit/SKILL.md +1 -1
- package/assets/skills/jaz-pseudo-sql/SKILL.md +1 -1
- package/assets/skills/jobs/SKILL.md +1 -1
- package/assets/skills/transaction-recipes/SKILL.md +1 -1
- package/cli.mjs +451 -451
- package/package.json +1 -1
|
@@ -882,7 +882,7 @@ Always wrap in `{ payments: [...] }` even for single payment.
|
|
|
882
882
|
**CRITICAL notes from live testing**:
|
|
883
883
|
- POST uses `name`, GET returns both `customFieldName` and `name`
|
|
884
884
|
- Valid `type` values: `"TEXT"`, `"DATE"`, `"DROPDOWN"` (UPPERCASE)
|
|
885
|
-
- `printOnDocuments` is REQUIRED — omitting it
|
|
885
|
+
- `printOnDocuments` is REQUIRED and is not defaulted server-side — omitting it returns 422 `printOnDocuments is a required field` (probed 2026-09-02; recorded as a 400 before that). `create_custom_field` sends `false` when you omit it.
|
|
886
886
|
- Do NOT send `appliesTo` field — causes "Invalid request body"
|
|
887
887
|
- Only send: `name`, `type`, `printOnDocuments` (and `options` for DROPDOWN)
|
|
888
888
|
- For DROPDOWN type, `options` array works (without `appliesTo`)
|
|
@@ -90,9 +90,10 @@ Or call `list_account_classifications` — authoritative for that organisation.
|
|
|
90
90
|
|
|
91
91
|
## Custom Field Errors
|
|
92
92
|
|
|
93
|
-
### "
|
|
94
|
-
**Cause**: Missing the required `printOnDocuments` field.
|
|
95
|
-
**Fix**: Always include `printOnDocuments: false` (or `true`) in POST body.
|
|
93
|
+
### "printOnDocuments is a required field" (422) — missing printOnDocuments
|
|
94
|
+
**Cause**: Missing the required `printOnDocuments` field. It is not defaulted server-side.
|
|
95
|
+
**Fix**: Always include `printOnDocuments: false` (or `true`) in POST body. `create_custom_field` now sends `false` when you omit it, so this only bites a direct API caller.
|
|
96
|
+
**Note**: recorded here as a 400 "Invalid request body" until 2026-09-02, when a live probe returned `422 validation_error` with the field named. Either the API tightened or the original entry generalised from a different malformed body; the 422 is what it returns today.
|
|
96
97
|
```json
|
|
97
98
|
{ "name": "PO Number", "type": "TEXT", "printOnDocuments": false }
|
|
98
99
|
```
|