Definition and Usage
Change the name of a specified view within a Lark Base table. You choose how to locate both the table and the view (by name or by unique ID), then provide the new view name. Use this command after establishing a connection to Lark Base.
Parameter Values
Input Parameters
Parameter Name | Description | Possible Values | Required | Options / Notes |
Lark Base | Select the Lark Base object generated earlier. | Previously created object | Yes | Must come from the Connect Lark Base command; ensure the connection is valid. |
Table locating mode | Choose how to specify the table. | By name, By ID | Yes | Determines which table field is used; match exactly with table metadata. |
Data table name | Name of the table containing the view to rename. | Text | Conditionally | Required when Table locating mode = By name; must match the existing table name. |
Data table ID | ID of the table containing the view to rename. | Text/ID | Conditionally | Required when Table locating mode = By ID; copy from Lark Base to avoid typos. |
View locating mode | Choose how to specify the view. | By name, By ID | Yes | Determines which view field is used; IDs are more reliable than names. |
View name | Current name of the view to be renamed. | Text | Conditionally | Required when View locating mode = By name; case-sensitive matching may apply. |
View ID | Unique ID of the view to be renamed. | Text/ID | Conditionally | Required when View locating mode = By ID; preferred for accuracy. |
New view name | The new name to assign to the view. | Text | Yes | Ensure the name follows any naming rules; avoid duplicates if your process depends on unique names. |
Advanced Settings
No advanced settings available.
Error Handling
Parameter Name | Description |
Throw error & stop | When an error occurs, the action will stop execution. |
Retry command | The action retries the command if an error occurs. |
Ignore error & continue | The action ignores the error and continues workflow execution. |
Variables Produced
This action doesn't produce any variables.
Using Variables in Conditions
You can pass dynamic values from earlier steps into fields such as table name, table ID, view name, view ID, and new view name. If the UI marks a field with {x}, it indicates that the field supports variables. Common patterns include:
Storing a table ID from a previous Get Lark Base view step and injecting it here.
Building a new view name using a variable (e.g., including a date or iteration counter).
Test variable-driven values to ensure they resolve to valid names or IDs before running at scale.
Notes
Prerequisite: You must first connect to Lark Base and have a valid Lark Base object.
Use IDs when possible to avoid ambiguity from duplicate or renamed tables/views.
Ensure the specified table contains the target view; mismatched table/view references will fail.
Confirm you have permission to modify the table/view in Lark Base.
Avoid leading/trailing spaces in names; trim inputs if built from variables.
If your workflow depends on unique view names, validate uniqueness before renaming.