Get Record
Operation name
Get Record
Function overview
Gets Kintone records.
Data model
The data model of this component is XML type.
Properties
For details on use of variables, refer to Variables.
Basic settings
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
---|---|---|---|---|
Name |
Required |
Not available |
Enter a name that is used on the script canvas. |
|
Required settings
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
---|---|---|---|---|
Destination |
Required |
Not available |
Select a connection resource.
|
|
Search query |
Optional |
Available |
Enter a query string as a filter condition to get records. |
Note
When you select Enable paging, don't use offset or limit as a query string. |
Field list |
Required |
- |
Specify fields. |
|
Field list/Target |
Optional |
Not available |
Select whether or not to include each field in target to read.
|
Note
One or more columns must be selected. |
Field list/Field name |
Optional |
Not available |
Field name is displayed. |
|
Field list/Field code |
Optional |
Not available |
Field code is displayed. |
|
Field list/Field type |
Optional |
Not available |
Field type is displayed. |
|
Field list/Subtable |
Optional |
Not available |
When a field is included in subtable, the field code of the subtable is displayed. |
|
Property actions
Item name |
Description |
Remarks |
---|---|---|
Update field list |
Get field information from the Kintone application and set it to Field list. |
|
Get record settings
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
---|---|---|---|---|
Enable paging |
Optional |
Not available |
Select whether or not to enable paging to get more records than the limited number of API.
|
|
Page size |
Optional |
Available |
Specify the number of records that you get from a single API request when paging is enabled. |
|
Method for getting records by using paging |
Optional |
Not available |
Specify the method for getting records when paging is enabled.
|
|
Attachment
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
---|---|---|---|---|
Download attachment |
Optional |
Not available |
Select whether or not to download attachments.
|
|
Output method for attachment |
Optional |
Not available |
Select an output method for attachments.
|
|
Download directory |
Required |
Available |
Select or enter the directory to download attachments. The Browse button launches a directory chooser that allows you to select a directory. The paths of the downloaded attachments will be Download directory/<record ID>/<field code>/<file key>/<attached file name>. |
Note
|
Data processing method
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
---|---|---|---|---|
Data processing method |
Optional |
Not available |
Select a data processing method.
|
|
Comment
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
---|---|---|---|---|
Comment |
Optional |
Not available |
You can write a short description of this connector. |
|
Schemas
Input schema
None.
Output schema
For more details on schema used by this connector, refer to Record schema.
Loading schema in Mapper
The schema is loaded automatically.
Specify the schema of the data to be loaded.
For details, refer to Edit Schema.
Mass data processing
Mass data processing is supported.
Parallel Stream Processing
PSP isn't supported.
Available component variables
Component variable name |
Description |
Remarks |
---|---|---|
count |
The number of read records is stored. |
|
message_category |
When an error occurs, the category of the message code corresponding to the error is stored. |
|
message_code |
When an error occurs, the code of the message code corresponding to the error is stored. |
|
message_level |
When an error occurs, the severity of the message code corresponding to the error is stored. |
|
error_type |
When an error occurs, the error type is stored. |
|
error_message |
When an error occurs, the error message is stored. |
|
error_trace |
When an error occurs, the trace information for the error is stored. |
|
When paging is enabled, it's necessary to use the different methods of acquiring records depending on factors such as the total record count in the filtered results.
For more details, refer to "Bulk record retrieval using the Cursor API method" (https://kintone.dev/en/tutorials/development-productivity/the-three-methods-for-bulk-record-retrieval/#the-cursor-api-method).
Method |
Suitable usage scenario |
Points for consideration |
---|---|---|
Use offset |
|
|
Use cursor API |
|
|
Use record ID |
|
|
The above contents are based on Kintone API specifications as of December 8, 2019.
The contents are subject to change depending on future improvements and additions to Kintone API.
Message codes, exception messages, and limitations
Connector |
Message code |
Exception message |
Limitations |
---|---|---|---|