Glide Apps icon

Glide Apps

Interact with Glide Apps API
Join our community

Actions17

Overview

This node operation replaces the entire schema or data of a specified table in Glide Apps. It allows users to update the table's structure (columns) and its rows in one atomic action. This is useful when you want to completely redefine a table's layout or refresh its content with new data.

Common scenarios include:

  • Migrating or restructuring data by changing column definitions.
  • Bulk updating all rows in a table after a major data import or transformation.
  • Synchronizing an external data source with a Glide table by replacing its contents entirely.

For example, you might replace a customer invoice table schema to add new columns for discounts and taxes, then upload all updated invoice rows conforming to the new schema.

Properties

Name Meaning
API Type Choose which Glide API to use for this operation:
- Big Tables API (OpenAPI)
- Glide Npm Api (@glideapps/Tables)
If Match ETag of the current table version. If provided, the request will fail if the table has been updated since this version. Used for optimistic concurrency control to avoid overwriting changes made elsewhere.
Table ID The unique identifier of the table to replace, e.g., 2a1bad8b-cf7c-44437-b8c1-e3782df6.
On Schema Error Action to take if the provided data does not match the existing table schema:
- abort: Stop and return an error.
- dropColumns: Ignore problematic columns in the data.
- updateSchema: Adjust schema automatically to fit data.
Schema JSON object defining the new table schema as a collection of column definitions. Each column includes an ID, display name, and type (e.g., string, dateTime, number).
Rows JSON array of row objects matching the schema. Each row maps column IDs to their values. This replaces all existing rows in the table.

Output

The node outputs JSON data representing the result of the replace operation. Typically, this includes confirmation of the updated table schema and the rows now stored in the table. The exact structure depends on the API response but generally reflects the new state of the table after replacement.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Glide Apps API.
  • Uses the Glide Big Tables API (OpenAPI) or the Glide NPM API client depending on the selected API Type.
  • Network access to https://api.glideapps.com is required.
  • Proper permissions to modify the target table are necessary.

Troubleshooting

  • ETag Mismatch: If using the "If Match" property, you may get errors if the table was updated since you last fetched it. To fix, retrieve the latest ETag and retry.
  • Schema Validation Errors: If the data rows do not conform to the schema and onSchemaError is set to abort, the operation will fail. Consider using updateSchema to allow automatic schema adjustments or dropColumns to ignore invalid columns.
  • Invalid Table ID: Ensure the Table ID is correct and accessible by your API credentials.
  • Malformed JSON: The schema and rows properties require valid JSON. Invalid JSON will cause parsing errors.
  • API Limits or Permissions: Check that your API key has sufficient permissions and that you are not exceeding rate limits.

Links and References

Discussion