Save the column layout of a view

PUT 
/api/v2/views/:viewId

Persists the column selection (order + width). The list is the visible column set; the backend keeps adding the PK, FK pair counterparts and ALWAYS_VISIBLE_COLUMN fields on the next GET. Both native (name, code...) and custom (customFields.<id>) apiNames are accepted.

With a numeric viewId the columns of THAT template are updated (the "Save" button of the template bar); the caller needs canEdit on it ÔÇö owner or EDITAR_PLANTILLASGLOBALES ÔÇö and a private template of another user answers 404. Unknown apiNames are rejected with 400 on named templates.

DEPRECATED (slug form): PUT on {featureType}-main still performs the historical implicit upsert of the user's un-named plantilla, but it is deprecated in favour of named templates (POST /api/v2/views + PUT /api/v2/views/{plantillaId}). It will start answering 400 once the SPA migrates to the template bar.

Request

Responses

204

Layout saved

400

Invalid payload, unknown apiNames on a named template, or feature without a writable plantilla

401

Missing or invalid JWT (Bearer token).

403

Missing edit permission on the entity, or no edit rights over the referenced template

404

View not registered (or private template of another user)

500

Unexpected server error. Includes legacy WAR failures that are not classified as 502 / 503 / 504.