Prerequisites: First read
../lark-shared/SKILL.md。 Must do before execution: Before executing anybasecommand, you must first read the reference documentation for the corresponding command, then call the command. Naming convention: Base business commands only use thelark-cli base +...form; if you need to first resolve a Wiki link, you can first calllark-cli wiki ...。 Routing rules: If the user wants to "import a local file into a Base / bitable", the first step is notbase, butlark-cli drive +import --type bitable; after the import is complete, return tolark-cli base +...to perform in-table operations.
1. When to use this Skill
1.1 Trigger conditions
This skill should be used in the following scenarios:
- The user explicitly wants to operate Feishu Base.
- The user wants to create, modify, query, or delete tables, or manage fields, records, and views.
- The user wants to create formula fields, lookup fields, derived metrics, or cross-table calculations.
- The user wants to perform ad hoc statistics, aggregate analysis, comparison and sorting, or find maximum/minimum values.
- The user wants to manage workflows, dashboards, forms, or role permissions.
- The user provides a
/base/{token}link. - The user provides a
/wiki/{token}link, and it is ultimately resolved tobitable。 - The user wants to change the old Base aggregate-style syntax to the current atomic command syntax, for example changing the old
+table / +field / +record / +view / +history / +workspaceto the current command.
This skill should not be used in the following scenarios:
- The user is only doing authentication, initial configuration, switching
--as user/bot, or handling scopes. In this case, first read../lark-shared/SKILL.md。 - The user is only discussing "data analysis / field design" in a general way, but not in a Base scenario. Do not mistakenly trigger it just because "statistics / formulas / lookup" are mentioned.
1.2 Prerequisite constraints
- First read
../lark-shared/SKILL.md。 - Base business commands only use the
lark-cli base +...form of shortcut commands; if the input is a Wiki link, you can first calllark-cli wiki spaces get_nodeto resolve the real token. - After locating the command, first read the reference corresponding to that command, then execute the command.
- If the user wants to import a local Excel / CSV into a Base / bitable, the first step is not
base, butlark-cli drive +import --type bitable; after the import is complete, return tolark-cli base +...to perform in-table operations. - Do not switch to
lark-cli api /open-apis/bitable/v1/...。
2. Modules and command navigation
This chapter is organized in the manner of "first choose a module, then choose a command". First determine which major module the user's goal belongs to, then enter the corresponding submodule, and execute the command after reading the reference as required.
2.1 Module map
| Major module | What problem it handles | Included submodules / capabilities |
|---|---|---|
| Base module | Manage the Base itself, or enter the Base scenario from a link | base-create / base-get / base-copy, Base / Wiki link resolution |
| Table and data module | Manage the internal structure of the Base and daily data operations | table / field / record / view |
| Formula / Lookup module | Handle derived fields, conditional logic, cross-table calculations, and fixed lookup references | formula / lookup Field creation and updates |
| Data Analysis module | Perform one-off filtering, grouping, and aggregation analysis | data-query |
| Workflow module | Manage automated processes | workflow-list / get / create / update / enable / disable |
| Dashboard module | Manage dashboards and chart components | dashboard-* / dashboard-block-* |
| Form module | Manage forms and form questions | form-* / form-questions-* |
| Permissions and Roles module | Manage advanced permissions and custom roles | advperm-* / role-* |
2.2 Base module
Used to manage the Base itself, or to proceed with subsequent Base operations from a link provided by the user.
Module index:references/lark-base-workspace.md
When receiving a request to create a new Base, first check
lark-base-templates-catalog.md. If the catalog contains a matching template, copy it with+base-copy→ customize. If not, fall back to creating from scratch with+base-create. If you do not check the catalog first, you waste time in cases that could have been handled with an existing template.
| Command | Purpose / When to use | Required reference | Routing reminder |
|---|---|---|---|
| Check template catalog | First step in creating a new Base | lark-base-templates-catalog.md |
+base-create / +base-copy Always check before . If a matching template exists, copy it; if not, create |
+base-create |
Create a new Base (when the catalog has no matching template) | lark-base-base-create.md、lark-base-templates-catalog.md、lark-base-workspace.md |
Write operation; read the reference before executing;--folder-token、--time-zone are all optional |
+base-get |
Get Base information | lark-base-base-get.md、lark-base-workspace.md |
Suitable for confirming Base information itself; does not replace reading table/field structure |
+base-copy |
Copy an existing Base (main path when adopting a catalog template) | lark-base-base-copy.md、lark-base-templates-catalog.md、lark-base-workspace.md |
Write operation; read the reference before executing; after a successful copy, proactively return the new Base identifier information |
2.3 Table and Data module
This is the most commonly used large module, containing table / field / record / view four types of submodules.
Supplementary example:references/examples.md, suitable for reading when you need to chain together the complete table / record / view operation flow.
2.3.1 Table submodule
Submodule index:references/lark-base-table.md
| Command | Purpose / When to use | Required reference | Routing reminder |
|---|---|---|---|
+table-list / +table-get |
List data tables, or get details of a single table | lark-base-table-list.md、lark-base-table-get.md |
+table-list can only be executed serially;+table-get is suitable for confirming the target before deletion/modification |
+table-create / +table-update / +table-delete |
Create, update, or delete data tables | lark-base-table-create.md、lark-base-table-update.md、lark-base-table-delete.md |
Creation is suitable for one-off table creation; confirm the target table before updating; when deleting, if the user has already specified the target, you can execute directly and include --yes |
2.3.2 Field submodule
Ordinary field management goes here; if the field type is formula or lookup, go to the "Formula / Lookup module" below.
Submodule index:references/lark-base-field.md
| Command | Purpose / When to use | Required reference | Routing reminder |
|---|---|---|---|
+field-list / +field-get |
List field structure, or get details of a single field | lark-base-field-list.md、lark-base-field-get.md |
Before writing records, writing fields, or performing analysis, often read +field-list;+field-list Can only be executed serially;+field-get Suitable for confirming the target before deletion/update |
+field-create / +field-update / +field-delete |
Create, update, or delete ordinary fields | lark-base-field-create.md、lark-base-field-update.md、lark-base-field-delete.md、lark-base-shortcut-field-properties.md |
Before writing a field, check the field property specification first; if the type is formula / lookup, first go read the corresponding guide; when deleting, if the user has already specified the target clearly, it can be executed directly and include --yes |
+field-search-options |
Query field selectable options | lark-base-field-search-options.md |
Suitable for option-type fields such as single-select/multi-select |
2.3.3 Record submodule
Submodule index:references/lark-base-record.md、references/lark-base-history.md
| Command | Purpose / When to use | Required reference | Routing reminder |
|---|---|---|---|
+record-search / +record-list / +record-get |
Search records by keyword, read record details / paginated export, or get details of a single record | lark-base-record-search.md、lark-base-record-list.md、lark-base-record-get.md |
Default priority +record-list; use only when the user provides an explicit search keyword +record-search; data retrieval is not used for aggregation analysis;--limit maximum 200; continue paging only when the user explicitly needs it;+record-list can only be executed serially |
+record-upsert / +record-batch-create / +record-batch-update |
Create, update, or batch write records | lark-base-record-upsert.md、lark-base-record-batch-create.md、lark-base-record-batch-update.md、lark-base-shortcut-record-value.md |
Before writing, first +field-list; only write stored fields; for batch, it is recommended not to exceed 500 records at a time; do not use this for attachments |
+record-upload-attachment |
Upload attachments to existing records | lark-base-record-upload-attachment.md |
Dedicated path for attachment uploads, do not use +record-upsert / +record-batch-* to forge attachment values |
lark-cli docs +media-download |
Download Base attachment files locally | ../lark-doc/references/lark-doc-media-download.md |
For Base attachments, file_token from +record-get the attachment field array returned;do not use lark-cli drive +download(returns 403 for Base attachments) |
+record-delete / +record-history-list |
Delete records, or query the change history of a record | lark-base-record-delete.md、lark-base-record-history-list.md |
When deleting, if the user has already specified the target clearly, it can be executed directly and include --yes; history queries are by table-id + record-id, full-table scans are not supported;+record-history-list can only be executed serially |
2.3.4 View submodule
Submodule index:references/lark-base-view.md
| Command | Purpose / When to use | Required reference | Routing reminder |
|---|---|---|---|
+view-list / +view-get |
List views, or get view details | lark-base-view-list.md、lark-base-view-get.md |
+view-list can only be executed serially;+view-get suitable for viewing existing view configurations |
+view-create / +view-delete / +view-rename |
Create, delete, or rename views | lark-base-view-create.md、lark-base-view-delete.md、lark-base-view-rename.md |
Before creating, first confirm the table and view type; before deleting, first confirm the target; if the user has already specified the new name clearly, it can be renamed directly |
+view-get-filter / +view-set-filter |
Read or configure filter conditions | lark-base-view-get-filter.md、lark-base-view-set-filter.md、lark-base-record-list.md |
Often combined with +record-list , used for reading by view filter |
+view-get-sort / +view-set-sort |
Read or configure sorting | lark-base-view-get-sort.md、lark-base-view-set-sort.md |
Field names must come from the real structure |
+view-get-group / +view-set-group |
Read or configure grouping | lark-base-view-get-group.md、lark-base-view-set-group.md |
Field names must come from the real structure |
+view-get-visible-fields / +view-set-visible-fields |
Read or configure view visible fields | lark-base-view-get-visible-fields.md、lark-base-view-set-visible-fields.md |
Used to control field order and visibility in the view; field names must come from the real structure |
+view-get-card / +view-set-card |
Read or configure card view | lark-base-view-get-card.md、lark-base-view-set-card.md |
Suitable for card display scenarios |
+view-get-timebar / +view-set-timebar |
Read or configure timeline view | lark-base-view-get-timebar.md、lark-base-view-set-timebar.md |
Suitable for timeline display scenarios |
2.4 Formula / Lookup module
As long as the user's request involves derived metrics, conditional logic, text processing, date differences, cross-table calculations, or retrieving values after cross-table filtering, you must first determine whether to enter this module.
By default, prioritize formula: suitable for routine calculations, conditional logic, text processing, date differences, cross-table aggregation, and derived results that need to be displayed in the table over the long term.
Only when the user explicitly requests lookup, or when the scenario naturally matches from / select / where / aggregate for this kind of fixed-lookup modeling, then use lookup。
| Command | Purpose / When to use | Required reference | Routing reminder |
|---|---|---|---|
+field-create(type=formula) |
Create formula field | formula-field-guide.md、lark-base-field-create.md、lark-base-shortcut-field-properties.md |
Do not create directly before reading the guide |
+field-update(type=formula) |
Update formula field | formula-field-guide.md、lark-base-field-update.md、lark-base-shortcut-field-properties.md |
First get the current table structure |
+field-create(type=lookup) |
Create lookup field | lookup-field-guide.md、lark-base-field-create.md、lark-base-shortcut-field-properties.md |
Do not create directly before reading the guide |
+field-update(type=lookup) |
Update lookup field | lookup-field-guide.md、lark-base-field-update.md、lark-base-shortcut-field-properties.md |
For cross-table operations, also get the target table structure |
2.5 Data Analysis Module
Used for one-time analysis and temporary aggregate queries. When what the user wants is "the result calculated this time" rather than persisting the result as a field, prioritize entering this module.
Before entering this module, confirm several things:
+data-queryOnly performs aggregate queries (grouping, filtering, sorting, aggregate calculations), and is not used to list raw records or itemized details.- The caller must be an admin of the target multidimensional table and have FA (Full Access) to the target multidimensional table; otherwise a permission error will be returned.
+data-queryOnly whitelisted field types are supported;formula、lookup, attachments, system fields, links, and other such fields cannot be used fordimensions / measures / filters / sort。
| Command | Purpose / When to use | Required reference | Routing reminder |
|---|---|---|---|
+data-query |
Perform grouped statistics, SUM / AVG / COUNT / MAX / MIN, and aggregate analysis after conditional filtering | lark-base-data-query.md |
Field names must exactly match real field names; do not use +record-list / +record-search to pull the full dataset and then calculate manually;+data-query does not return raw records; before use, first confirm whether permissions and field types are supported |
2.6 Workflow Module
This is a highly constrained module. Before executing any workflow command, you must first read the corresponding command documentation and schema.
Module index:references/lark-base-workflow.md
| Command | Purpose / When to use | Required reference | Routing reminder |
|---|---|---|---|
+workflow-list / +workflow-get |
List workflows, or get the complete workflow structure | lark-base-workflow-list.md、lark-base-workflow-get.md、lark-base-workflow-schema.md |
+workflow-list only returns a summary and can only be executed serially; when the complete structure is needed, use +workflow-get |
+workflow-create / +workflow-update |
Create or update workflow | lark-base-workflow-create.md、lark-base-workflow-update.md、lark-base-workflow-schema.md |
First read the schema; do not guess typefrom natural language; first confirm the real table names and field names |
+workflow-enable / +workflow-disable |
Enable or disable workflow | lark-base-workflow-enable.md、lark-base-workflow-disable.md、lark-base-workflow-schema.md |
Before enabling or disabling, first confirm the target workflow;workflow_id and table_id need to be distinguished by prefix |
2.7 Dashboard Module
When the user mentions keywords such as "dashboard, data dashboard, charts, visualization, block, component, add component, create chart", enter this module, and first read lark-base-dashboard.md。
| Command | Purpose / When to use | Required reference | Routing reminder |
|---|---|---|---|
+dashboard-list / +dashboard-get |
List dashboards, or get dashboard details | lark-base-dashboard-list.md、lark-base-dashboard-get.md、lark-base-dashboard.md |
After entering the dashboard semantics, read the guide first;+dashboard-list can only be executed serially |
+dashboard-create / +dashboard-update / +dashboard-delete |
Create, update, or delete dashboards | lark-base-dashboard-create.md、lark-base-dashboard-update.md、lark-base-dashboard-delete.md、lark-base-dashboard.md |
Before creating, clarify the dashboard goals and display scenarios first; before updating, read the current configuration first; before deleting, confirm the target first |
+dashboard-block-list / +dashboard-block-get |
List chart components, or get details of a single block | lark-base-dashboard-block-list.md、lark-base-dashboard-block-get.md、lark-base-dashboard.md、dashboard-block-data-config.md |
+dashboard-block-list can only be executed serially; when viewing configuration details, read the block config documentation |
+dashboard-block-create / +dashboard-block-update / +dashboard-block-delete |
Create, update, or delete chart components | lark-base-dashboard-block-create.md、lark-base-dashboard-block-update.md、lark-base-dashboard-block-delete.md、lark-base-dashboard.md、dashboard-block-data-config.md |
When involving data_config, chart types, or filters, read the block config documentation; before deleting, confirm the target first |
2.8 Form module
Used to manage forms themselves and form questions.
Module index:references/lark-base-form.md、references/lark-base-form-questions.md
Form question-related operations depend on form-id; for the specific retrieval method, see the references for form-list and form-create .
| Command | Purpose / When to use | Required reference | Routing reminder |
|---|---|---|---|
+form-list / +form-get |
List forms, or get a single form | lark-base-form-list.md、lark-base-form-get.md |
+form-list can be used to get form-id;+form-get is suitable for viewing existing form configurations |
+form-create / +form-update / +form-delete |
Create, update, or delete forms | lark-base-form-create.md、lark-base-form-update.md、lark-base-form-delete.md |
After creation, you can continue to form question-related operations; before updating or deleting, confirm the target form first |
+form-questions-list |
List form questions | lark-base-form-questions-list.md |
Suitable for viewing the existing question structure |
+form-questions-create / +form-questions-update / +form-questions-delete |
Create, update, or delete questions | lark-base-form-questions-create.md、lark-base-form-questions-update.md、lark-base-form-questions-delete.md |
Confirm form-idfirst; before updating or deleting, confirm the question target first |
2.9 Permissions and roles module
Used to enable advanced permissions and manage Base custom roles.
When involving +advperm-enable / +advperm-disable / +role-* , the operating user must be a Base admin, otherwise a permission error will be returned.
| Command | Purpose / When to use | Required reference | Routing reminder |
|---|---|---|---|
+advperm-enable / +advperm-disable |
Enable or disable advanced permissions | lark-base-advperm-enable.md、lark-base-advperm-disable.md |
Must be enabled before managing roles; disabling is a high-risk operation and will invalidate existing custom roles |
+role-list / +role-get |
List roles, or get role details | lark-base-role-list.md、lark-base-role-get.md、role-config.md |
+role-list can only be executed serially;+role-get is suitable for viewing the complete permission configuration |
+role-create / +role-update / +role-delete |
Create, update, or delete roles | lark-base-role-create.md、lark-base-role-update.md、lark-base-role-delete.md、role-config.md |
+role-create only supports custom_role;+role-update uses Delta Merge,role_name and role_type must still pass the current value even if unchanged;+role-delete is irreversible |
3. General knowledge of Bitable
The English name of Feishu Bitable is Base, formerly known as Bitable; therefore, when bitable appears in old documents, returned fields, parameter names, or error messages, it is mostly historical compatibility and does not mean another command system should be used instead.
3.1 Field classification and writability
| Field type | Meaning | Can it be directly used as a write target for +record-upsert / +record-batch-create / +record-batch-update Write target |
Description |
|---|---|---|---|
| Stored field | Actually stores data input by users | Yes | Common examples include text, number, date, single select, multiple select, person, and link |
| Attachment field | Store file attachments | Should not be written directly as an ordinary field | Upload attachments via +record-upload-attachment; download attachments via lark-cli docs +media-download |
| System fields | Automatically maintained by the platform | Not allowed | Common examples include creation time, update time, creator, modifier, auto number |
formula fields |
Computed through expressions | Not allowed | Read-only fields |
lookup fields |
Look up references through cross-table rules | Not allowed | Read-only fields |
3.2 Task routing mental model
| User request | Preferred solution | Do not mistakenly use |
|---|---|---|
| One-off analysis / temporary statistics | +data-query |
Do not use +record-list / +record-search to pull the full dataset and calculate manually |
| Need to display the result in the table long-term | formula fields |
Do not only provide a one-off manual analysis result |
| The user explicitly requests lookup, or it is naturally a fixed lookup configuration | lookup fields |
Do not default to lookup first; first determine whether formula is more appropriate |
| Read raw record details / keyword search / export | +record-search / +record-list / +record-get |
Do not use +data-query as a data retrieval command |
| Upload attachments to a record | +record-upload-attachment |
Do not use +record-upsert / +record-batch-* to forge attachment values |
| Download attachment files in a record | lark-cli docs +media-download --token <file_token> --output <path> |
file_token from the attachment field returned by +record-get ; for usage see ../lark-doc/references/lark-doc-media-download.md |
| Filtered read based on a view | +view-set-filter + +record-list |
Do not skip view filters and guess conditions directly |
| Import local Excel / CSV as a Base | lark-cli drive +import --type bitable |
Do not mistakenly use +base-create、+table-create or +record-upsert |
3.3 Table names, field names, and expression references
- Table names and field names must exactly match what is actually returned; the source should be
+table-list / +table-get / +field-list。 - Do not guess names from natural language, and do not rewrite table names or field names from what the user says.
formula / lookup / data-query / workflowNames appearing in must also match exactly; expression references, where conditions, DSL field names, and workflow configurations all follow the same rule.- In cross-table scenarios, you must additionally read the target table structure; do not only look at the current table.
3.4 Tokens and links
This is a high-priority section. Whenever links or tokens appear in user input, or an error involves baseToken / wiki_token / obj_token, you should first return here to check.
| Input type | Correct handling method | Description |
|---|---|---|
Direct Base link /base/{token} |
Directly extract the token as --base-token |
Do not directly use the full URL as --base-token |
Wiki link /wiki/{token} |
First wiki.spaces.get_node, then get node.obj_token |
Do not directly treat wiki_token as --base-token |
In the URL ?table={id} |
First determine the object type by prefix | tbl beginning with indicates a data table table-id, and can be used as --table-id;blk beginning with indicates a dashboard dashboard-ID;wkf beginning with indicates workflow-ID;ldx The beginning indicates an embedded document; do not treat it all as --table-id |
In the URL, ?view={id} |
extract as --view-id |
suitable for directly locating the view |
lark-cli wiki spaces get_node returned obj_type |
subsequent route | instructions |
|---|---|---|
bitable |
prioritize going through lark-cli base +... |
if the shortcut does not cover it, then use lark-cli base <resource> <method>; do not switch to lark-cli api /open-apis/bitable/v1/... |
docx |
switch to the document / Drive related skill | do not continue using this skill's Base commands |
sheet |
switch to the Sheets related skill | do not continue using this skill's Base commands |
slides |
switch to the Drive related skill | do not continue using this skill's Base commands |
mindnote |
switch to the Drive related skill | do not continue using this skill's Base commands |
3.5 Execution Identity and Personnel Fields
- Personnel field / user field: note the
user_id_typeand execution identity (user / bot) differences. - bot identity: the bot cannot see users' private resources; behavior is executed under the application identity.
- user identity: depends on user authorization and scope; more suitable for operating on user resources.
4. Execution Rules
4.1 Standard Execution Order
- First determine which module the task belongs to, and choose the correct command family.
- If the user provides a link, parse the token first; do not mistake the wiki token, the full URL, or other object IDs for
base_token。 - Get the structure first, then write commands, to avoid guessing table names, field names, or expression references.
- After locating the command, read the corresponding reference first, then execute the command.
- Execute the command, and determine the next step based on the returned result.
- When replying, return the key results and information about what can be done next, so the agent can chain into the next step.
4.2 Non-Violable Rules
- Get the structure first, then write commands; at minimum get the current table structure first, and for cross-table operations also get the target table structure.
- Do not guess table names, field names, or expression references; always rely on the actual return values.
- Use only atomic commands; do not fall back to the old aggregate-style
+table / +field / +record / +view / +history / +workspace。 - Before writing records, read the field structure first; first
+field-list, then construct the written value according to the field type. - Before writing fields, look at the field attribute specification first; first read
lark-base-shortcut-field-properties.md, then construct the+field-create / +field-updateJSON. - Only write writable fields; system fields, attachment fields, and
formula、lookupare by default not used as ordinary record write targets. - Aggregate analysis and data retrieval are split; for statistics use
+data-query, for keyword retrieval use+record-search, for details use+record-list / +record-get。 - Filtered queries are executed according to view capabilities; first use
+view-set-filterto configure the filter, then combine with+record-listto read. - For Base scenarios, do not switch to raw APIs, and do not switch to
lark-cli api /open-apis/bitable/v1/...。 - Uniformly use
--base-token, do not use the old--app-token。 - For workflow scenarios, read the schema first; do not guess based on natural language
type。 - For dashboard scenarios, read the guide first; when charts, dashboards, or blocks are mentioned, enter the dashboard module first.
- For formula / lookup scenarios, read the guide first; do not directly create or update before reading the guide.
4.3 Concurrency, Pagination, and Batch Limits
+table-list / +field-list / +record-list / +view-list / +record-history-list / +role-list / +dashboard-list / +dashboard-block-list / +workflow-listConcurrent calls are prohibited; only serial execution is allowed.+record-listWhen paginating,--limitMax200; first pull the first batch and checkhas_more, and only continue paging when the user explicitly needs more data.- For batch writes, it is recommended that a single batch not exceed
500records. - When continuously writing to the same table, it is recommended to write serially, with a delay of
0.5–1seconds between batches.
4.4 Confirmation and Reply Rules
- When renaming a view, if the user has clearly specified "which view to change to what name",
+view-renameexecute directly. - When deleting records / fields / tables, if the user has clearly stated that they want to delete, and the target is clear,
+record-delete / +field-delete / +table-deleteyou can execute directly, and include--yes。 - When the deletion target is still ambiguous, first use
+record-get / +field-get / +table-getor the corresponding list command to confirm. +base-create / +base-copyAfter success, the reply must proactively return the identifying information of the new Base; if the result includes an accessible link, it should also be returned.- If the Base was created by the bot identity and the current CLI has an available user identity, prioritize continuing to grant the current user as
full_access; owner transfer must be confirmed separately, and unauthorized execution is prohibited.
5. Common Errors and Recovery
| Error / Symptom | Meaning | Recovery Action |
|---|---|---|
1254064 |
Date format error | Use a millisecond timestamp, not a string / second-level |
1254068 |
Hyperlink format error | Use {text, link} object |
1254066 |
Person field error | Use [{id:"ou_xxx"}], and confirm user_id_type |
1254045 |
Field name does not exist | Check the field name (including spaces and case) |
1254015 |
Field value type mismatch | First +field-list, then construct according to the type |
param baseToken is invalid / base_token invalid |
Mistook a wiki token, workspace token, or other token for base_token |
If the input comes from /wiki/..., first use lark-cli wiki spaces get_node to get the real obj_token; when obj_type=bitable , use node.obj_token as --base-token to retry, do not switch to bitable/v1 |
not found and the user provided a wiki link |
Common when mistaking a wiki token for a base token | Prioritize falling back to check wiki parsing, rather than switching to bitable/v1 |
| formula / lookup creation failed | Guide not read or structure invalid | First read formula-field-guide.md / lookup-field-guide.md, then reconstruct the request according to the guide |
| System field / formula field write failed | Read-only field was treated as a writable field | Change to writing the storage field; leave calculation results to be automatically produced by formula / lookup / system fields |
1254104 |
Batch exceeds 500 records | Call in batches |
1254291 |
Concurrent write conflict | Serial writes + delay between batches |
6. Reference Documents
- lark-base-shortcut-field-properties.md —
+field-create/+field-updateMust-read before calling; JSON specifications for each type of field - role-config.md — Detailed explanation of role permission configuration
- lark-base-shortcut-record-value.md — record writing (
+record-upsert / +record-batch-create / +record-batch-update) Must-read before calling; JSON specifications for each type of record - lark-base-record-batch-create.md —
+record-batch-createusage and--jsonstructure - lark-base-record-batch-update.md —
+record-batch-updateusage and--jsonstructure - formula-field-guide.md — formula field syntax, function constraints, CurrentValue rules, cross-table calculation patterns
- lookup-field-guide.md — lookup field configuration rules, where/aggregate constraints, and trade-offs with formula
- lark-base-view-set-filter.md — view filter configuration
- lark-base-record-list.md — record list reading and pagination
- lark-base-record-search.md — keyword search records
- lark-base-advperm-enable.md —
+advperm-enableEnable advanced permissions - lark-base-advperm-disable.md —
+advperm-disableDisable advanced permissions - lark-base-role-list.md —
+role-listList roles - lark-base-role-get.md —
+role-getGet role details - lark-base-role-create.md —
+role-createCreate role - lark-base-role-update.md —
+role-updateUpdate role - lark-base-role-delete.md —
+role-deleteDelete role - lark-base-dashboard.md — dashboard module workflow guide
- dashboard-block-data-config.md — Block
data_configstructure, chart types, filter rules - lark-base-workflow.md — workflow command index
- lark-base-workflow-schema.md —
+workflow-create/+workflow-updateDetailed explanation of JSON body structure - lark-base-data-query.md —
+data-queryAggregate analysis, including DSL structure, supported field types, aggregate functions - examples.md — Complete operation examples
7. Command groups
Before executing, you must: After locating the command from the table below, be sure to first read the reference documentation for the corresponding command, then invoke the command.
| Command group | Description |
|---|---|
table commands |
+table-list / +table-get / +table-create / +table-update / +table-delete |
field commands |
+field-list / +field-get / +field-create / +field-update / +field-delete / +field-search-options |
record commands |
+record-search / +record-list / +record-get / +record-upsert / +record-batch-create / +record-batch-update / +record-upload-attachment / +record-delete |
view commands |
+view-list / +view-get / +view-create / +view-delete / +view-get-* / +view-set-* / +view-rename |
data-query commands |
+data-query |
history commands |
+record-history-list |
base / workspace commands |
+base-create / +base-get / +base-copy |
advperm commands |
+advperm-enable / +advperm-disable |
role commands |
+role-list / +role-get / +role-create / +role-update / +role-delete |
form commands |
+form-list / +form-get / +form-create / +form-update / +form-delete |
form questions commands |
+form-questions-list / +form-questions-create / +form-questions-update / +form-questions-delete |
workflow commands |
+workflow-list / +workflow-get / +workflow-create / +workflow-update / +workflow-enable / +workflow-disable |
dashboard / dashboard-block commands |
+dashboard-list / +dashboard-get / +dashboard-create / +dashboard-update / +dashboard-delete / +dashboard-arrange / +dashboard-block-list / +dashboard-block-get / +dashboard-block-create / +dashboard-block-update / +dashboard-block-delete |