Programmers reference for Microsoft Dynamics 365 Business Central Writer
In TQL, you specify the writer type by providing its fully qualified name. To use this writer, specify Global.MicrosoftDynamics365BusinessCentralWriter
when creating a target. This identifies the specific writer implementation to use and allows you to configure its connection and behavior through the available properties.
Microsoft Dynamics 365 Business Central Writer properties
Property | Type | Default value | Notes |
---|---|---|---|
Connection properties | |||
Client ID | String | Specifies the OAuth application's client ID. | |
Client Secret | Password | Specifies the OAuth application's client secret. | |
Company | String | Company name in Microsoft Dynamics 365 Business Central. | |
Connection Pool Size | Integer | 20 | Specifies the maximum number of active connections. |
Connection Profile Name | String | Select the MicrosoftDynamics365 connection profile from the list. | |
Organization URL | String | URL of your Business Central web service endpoint. For example: | |
Refresh Token | Password | Refresh token that can be used to generate and refresh access tokens. | |
Tenant ID | String | Tenant identifier for Business Central instance. | |
Use Connection Profile | Boolean | False | Set to true to use a connection profile instead of individual properties. |
Scheming and data handling | |||
Batch Policy | String | eventCount:999, Interval:90 | The batch policy includes the event count and interval. Events are buffered locally on the Striim server and sent as a batch to the target every time either of the specified values is exceeded. When the app is stopped, any remaining data in the buffer is discarded. To disable batching, set to With the default setting, data will be written every 90 seconds or sooner if the buffer accumulates 999 events. |
Mode | String | MERGE | With the default value of MERGE, inserts and deletes in the source are handled as inserts and deletes in the target (as detailed in the notes for Merge API). Set to APPENDONLY to handle all operations as inserts. With this setting:
|
Data selection | |||
Tables | String | The name(s) of the table objects(s) to write to, in the format When the input stream of the target is the output of a DatabaseReader, IncrementalBatchReader, or SQL CDC source (that is, when replicating data from one database to another), it can write to multiple objects. In this case, specify the names of both the source and target objects. You may use wildcards for the object names. If the reader uses three-part names, you must use them here as well. Note that SQL Server source table names must be specified in three parts when the source is Database Reader or Incremental Batch Reader ( Examples:
NotePartial wildcards not allowed. For example source.Business%,B% is not an allowed combination Both Object name and field names are case sensitive. | |
Additional properties | |||
Application Error Count Threshold | Integer | 0 | Application-specific Discarded Event count threshold. The application will HALT if the number of Ignorable errors crosses the threshold value. |
Ignorable Exception | String | A comma-separated list of exceptions which are ignored while calculating the Application error count threshold. | |
Connection Timeout | String | 300 | Specifies the maximum duration an API call should wait for a response before triggering a timeout exception. |
Datatype support
Striim type | Dynamics 365 data type |
---|---|
String | Single Line of Text |
String | Multiple Lines of Text |
String | Option Set |
String | MultiSelect Option Set |
boolean | Two Options |
String | Status |
String | Status Reason |
Long | Whole Number |
Double | Floating Point Number |
Double | Decimal Number |
Double | Currency |
org.joda.time.DateTime | Date and Time |
String | Lookup |
String | Owner |
String | Unique Identifier |
java.lang.Object | Image |
String | Customer |
String | Owner |