# Subaccounts: Visma.net Financials Subaccounts Get all SubAccounts - ScreenId=GL203000 Request page size must be lower or equal to the allowed max page size which is returned as part of the metadata information. If requested page size is greater than allowed max page size, request will be limited to max page size Change log: 2020-May:Added force pagination. Data for SubAccount Response Message has StatusCode OK if GET operation succeed - Catalog: `VismaNet` - Schema: `Subaccount` - Primary Keys: `subAccountNumber` - Label: Subaccounts - Retrieve: True - Insert: True - Update: True - Delete: False ## Parameters of Table Function The following parameters can be used to control the behaviour of the table function `Subaccounts`. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values. Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three. Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third. | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `active` | `` | ☐ | | If the SubAccount is active | | `lastModifiedDateTime` | `` | ☐ | | This value, generated by the system, indicates the last time the record was modified. Use it to retrieve all records that have been modified since that time, up to the present. Accepted format: * ```yyyy-MM-dd``` * ```yyyy-MM-dd HH:mm:ss``` * ```yyyy-MM-dd HH:mm:ss.FFF``` * ```yyyy-MM-ddTHH:mm:ss``` * ```yyyy-MM-ddTHH:mm:ss.FFF``` _Note:_ __LastModifiedDateTime__ and __LastModifiedDateTimeCondition__ are __mutually inclusive__. | | `lastModifiedDateTimeCondition` | `` | ☐ | | This value represents the condition to be applied when retrieving records. Accepted values (without the single quotes): * '>' for greater than * '<' for less than * '>=' for greater than or equal * '<=' for less than or equal _Note:_ __LastModifiedDateTime__ and __LastModifiedDateTimeCondition__ are __mutually inclusive__. | ## Columns of Table Function The columns of the table function `Subaccounts` are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `active` | `char` | Active | ☐ | Active > The status of the identifier. | | `COMPANY_CODE` | `varchar2(30)` | Company Code | ☑ | Partition code, segmenting the data. | | `COMPANY_NAME` | `varchar2(240)` | Company Name | ☑ | Name of the partition. | | `description` | `varchar2` | Description | ☐ | Description > The description of the identifier. | | `errorInfo` | `varchar2` | Error Message | ☐ | | | `lastModifiedDateTime` | `datetime` | Last Modified | ☐ | System generated information. | | `metadata_maxPageSize` | `int64` | Metadata Max Pagesize | ☐ | | | `metadata_totalCount` | `int64` | Total Count | ☐ | | | `subaccountId` | `int32` | | ☐ | SubID > The identifier of the subaccount. | | `subaccountNumber` | `varchar2` | | ☐ | Mandatory field: Subaccount* > The subaccount number. Format 9-XX. | | `timeStamp` | `blob` | Timestamp | ☐ | The timestamp of the subaccount, used for concurrency control. |