In Connectivity studio, usually, you can design the integration setup by configuration. Sometimes, it can be required to use a customization. This topic explains the standard connector handler classes in Connectivity studio and how to customize these classes. Only use customized classes if you really need specific functionality.
|
Connector type |
Handler class |
Description |
|
D365 FO |
BisConnectorAxDatabase |
This handler class exports data from or directly imports data into D365 FO tables. |
| Database |
BisConnectorODBC |
This handler class exports data to or imports data from an external database via ODBC or an external Azure SQL database |
|
Staging journal |
BisConnectorStagingJournal |
This handler class exports data from or imports data into a staging journal. |
|
Azure file storage |
BisConnectorWindowsFolder |
This handler class exports data to or imports data from a file. |
|
Web service |
BisConnectorStreamWebservice |
This handler class imports data from a stream or exports data to a stream. |
|
Blob Storage |
BisConnectorStreamBlobStorage |
This handler class exports data to or imports data from a file in a Blob container. |
|
Upload and download |
BisConnectorStreamManual |
This handler class imports data from an uploaded file or exports data to a file and downloads it. |
|
Method |
Description |
|
getNextInstance |
Returns the sets of data. So, for connector type Azure file storage, it returns the next file. |
|
preAction |
The actions if the connector is used as source connector. |
|
postAction |
The actions if the connector is used as target connector. |
|
close |
Closes the connector. |