infor

default

Use this method to send data object from your application directly to Data Lake.


In the request you must provide the compressed data object (file) itself
and at least the required data object properties: Object Name (dl_document_name) and Sender Logical ID (dl_from_logical_id).


Instance count (dl_instance_count), decompressed size (decompressed_size)
and source publication date (dl_source_publication_date) properties are not mandatory, but it is recommended to fill them.


Data object file has to be compressed using ZLIB compressed data format with the deflate compression method.


POST/dataobjects method is governed by a quota allowing up to 200 API calls per minute.


For more information on the API and data object properties refer to the Data Fabric User Guide.


Send data object directly to Data Lake

Check if Batch Ingestion API is accessible

Default

Ingestion V1

Infor API | Ingestion V1

Generated server url

The name of the object, as defined in Data Catalog, to which the data object belongs.

dl_document_name

The logical ID of the application that provided the data.

dl_from_logical_id

Date and time representing the time at which a data object was published by a source application. Value should be sent as DateTime (String) - UTC ISO 8601 yyyy-MM-dd'T'HH:mm:ss.SSS'Z'

dl_source_publication_date

The number of instances within the raw data object.

dl_instance_count

The size of decompressed data object in bytes.

decompressed_size

The accounting entity of the data, in case the data belongs to an accounting entity.

dl_header_accounting_entity

The location of the data if applicable, in case the data belongs to a physical location.

dl_header_location

The source of the data, where the data come from, for example the file name or a table name.

dl_header_source

The Document ID of the (business) object, in case the data object contains a single business object or record.

dl_header_document_id

The revision ID of the data, in case the data object contains a single business object or record and it has a revision ID.

dl_revision_id

The variation ID is used at the receiving end to discover messages that are received out of sequence.

dl_variation_id

The ID of the batch, if the data object belongs to a batch of multiple data objects.

dl_batch_id

The sequence number of the data object in the batch, if the data object belongs to a batch of multiple data objects.

dl_batch_sequence

The total number of data objects in the batch, if the data object belongs to a batch of multiple data objects.

dl_batch_size

The revision ID of the batch, if the data object belongs to a batch of multiple data objects, and a new revision of the batch was sent.

dl_batch_revision

The indicator whether the batch was canceled before it was completed, if the data object belongs to a batch.

dl_batch_abort_indicator

Boolean property that indicates whether the data object data is archived by the source system.

Sections