JDBC Driver for Microsoft Dataverse

Build 22.0.8462

INSERT INTO SELECT Statements

To perform multiple inserts in a single request to Microsoft Dataverse, use the INSERT INTO SELECT syntax to insert a temporary table of data into Microsoft Dataverse. This works by first populating a temporary table with the data you are going to submit to Microsoft Dataverse. Once you have all of the data you want to insert, the temporary table is then passed into the table in Microsoft Dataverse.

This functionality is also available via the standard Batch Processing API available in JDBC. See Batch Processing for more information.

Populate the Temporary Table

The temporary table you are populating is dynamic and is created at run time the first time you insert to it. Temporary tables are denoted by a # appearing in their name. When using a temporary table to insert, the temporary table must be named in the format [TableName]#TEMP, where TableName is the name of the table you will be inserting to. For example:

INSERT INTO Accounts#TEMP (Name, MyCustomField__c) VALUES ('New Accounts', '9000');
INSERT INTO Accounts#TEMP (Name, MyCustomField__c) VALUES ('New Accounts 2', '9001');
INSERT INTO Accounts#TEMP (Name, MyCustomField__c) VALUES ('New Accounts 3', '9002');

This creates a temporary table called Accounts#TEMP with two columns and three rows of data. Since type cannot be determined on the temporary table itself, all values are stored in memory as strings. They are later converted to the proper type when they are submitted to the Accounts table.

Insert to the Actual Table

Once your temporary table is populated, it is now time to insert to the actual table in Microsoft Dataverse. You can do this by performing an INSERT to the actual table and selecting the input data from the temporary table. For example:

INSERT INTO Accounts (Name, MyCustomField__c) SELECT Name, MyCustomField__c FROM Accounts#TEMP
In this example, the full contents of the Accounts#TEMP table are passed into the Accounts table. This results in fewer requests being submitted to Microsoft Dataverse since multiple inserts may be submitted with each request, which is much better for performance if you have many records to insert.

Results

The results of the query are stored in the LastResultInfo#TEMP temporary table. This table is cleared and repopulated the next time data is modified by passing in a temporary table. Please be aware that the LastResultInfo#TEMP table has no predefined schema. You need to check its metadata at run time before reading data.

Temporary Table Life Span

Temporary tables only last as long as the connection remains open. When the connection to Microsoft Dataverse is closed, all temporary tables are cleared, including the LastResultInfo#TEMP table.

Copyright (c) 2023 CData Software, Inc. - All rights reserved.
Build 22.0.8462