Each standard operation must have a fixed parameter set. The table shows the required parameters for each ABL operation that corresponds to a standard operation.

Built-in operation

Prescribed parameter list

Create

INPUT-OUTPUT { TABLE table-name | DATASET dataset-name | TABLE-HANDLE table-hdl | DATASET-HANDLE dataset-hdl}

Read

INPUT filter AS CHARACTER,

OUTPUT { TABLE table-name | DATASET dataset-name | TABLE-HANDLE table-hdl | DATASET-HANDLE dataset-hdl}

Update

INPUT-OUTPUT { TABLE table-name | DATASET dataset-name | TABLE-HANDLE table-hdl | DATASET-HANDLE dataset-hdl}

Delete

INPUT-OUTPUT { TABLE table-name | DATASET dataset-name | TABLE-HANDLE table-hdl | DATASET-HANDLE dataset-hdl}

Submit

INPUT-OUTPUT {DATASET dataset-name| DATASET-HANDLE dataset-hdl}

All standard operations for a particular Data Object resource must use the same data model. Because of this, all the CRUD operations for a given Data Object resource must use the same parameter type. Therefore, within an ABL resource, you must ensure that all the ABL operations that will correspond to the built-in operations use the same parameter type.

Unlike other operations, the Read operation defines only one input parameter. The parameter must be named “filter”. If it is named differently, it will not function properly when the JavaScript method calls the read operation.

The filter parameter is a string. As the name suggests, you can use the filter in a WHERE clause to filter the records returned by a read operation. However, you do not need to limit yourself to passing only a filter. Since it is a string parameter, you can place additional information in the string and then parse it in the ABL method or procedure corresponding to the read operation.