Definition and Usage
Delete a specified view from a table within the Lark Base. You can target both the table and the view either by their names or by their unique IDs. Use the locating modes to select which method you prefer.
Parameter Values
Input Parameters
Parameter Name | Description | Possible Values | Required | Options / Notes |
Lark Base | The connected Lark Base object to operate on. | Object from Connect Lark Base | Yes | Ensure you have successfully connected to Lark Base before using this command. |
Table locating mode | How to identify the target table. | By name, By ID | Yes | Choose ID when names are duplicated; choose name for readability. |
Data table name | The name of the table that contains the view to delete. | Text | Yes (if Table locating mode = By name) | Must match the table’s display name exactly; case and spacing matter. |
Data table ID | The unique ID of the table that contains the view to delete. | Text | Yes (if Table locating mode = By ID) | Prefer this in automated or multi-environment workflows to avoid name conflicts. |
View locating mode | How to identify the view to delete. | By name, By ID | Yes | Choose ID to avoid ambiguity when multiple views share similar names. |
View name | The name of the view to delete. | Text | Yes (if View locating mode = By name) | Must match the view’s display name; verify spelling and whitespace. |
View ID | The unique ID of the view to delete. | Text | Yes (if View locating mode = By ID) | Use when available to ensure precise targeting. |
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 previous steps into this command. For example, use a variable that stores a table ID or view ID retrieved earlier in the workflow. If the UI marks an input with {x}, it indicates that the field supports variables. Build flows so earlier steps capture names or IDs, then map those variables into the corresponding locating fields here.
Notes
Connect to Lark Base first and ensure the connection remains valid during execution.
The table must exist, and the specified view must exist within that table; otherwise, the command will fail.
Using IDs reduces the risk of deleting the wrong view when names are duplicated or localized.
Deleting a view is permanent for that view configuration; confirm you are targeting the correct table and view before running.