OMomni
Models

Re-parse model SQL

Changed on
<Note> **Querier** permissions or higher on a model are required to use this endpoint. </Note>

Re-parse all SQL fields and views in a shared model or shared extension and refresh their inferred column types. Use this to clear a SQL validation error after resolving the issue - such as a missing database grant - without editing the SQL itself.

Re-parsing the shared model itself, or a branch on a Git follower model, only saves if the result leaves the model's YAML unchanged; otherwise the request fails and nothing is saved. Re-parsing an ordinary branch saves YAML changes normally, such as newly inferred dimensions.

This request runs synchronously and can take several minutes on a large model. If your client times out before it finishes, the re-parse still completes and saves on the server.

post/v1/models/{modelId}/reparse

Request

  • Base URL
    https://blobsrus.omniapp.co/api
  • URL
    https://blobsrus.omniapp.co/api/v1/models/{modelId}/reparse
  • Auth
    HTTP bearer

Path parameters

modelIdstring uuid required

Model UUID

Example:123e4567-e89b-12d3-a456-426614174000

UUID of the shared model or shared extension to re-parse.

Query parameters

branch_idstring uuid
Example:123e4567-e89b-12d3-a456-426614174001

ID of a branch model to re-parse. This can be a branch of the shared model, or for a shared extension, a branch of its shared model. If the extension uses the Develop independently branch workflow, pass the ID of the extension itself.

Unlike re-parsing an entire model, re-parsing a branch saves even if the branch model's YAML changes. The exception is when this occurs on a Git follower model.

Response

Model re-parsed and saved

successboolean

Example response

{
  "success": true
}

Changes