1. To-Increase Dynamics 365 for Finance & Operations
  2. EDI studio
  3. Activities

Set up document - D365 FO
Application task

Use a D365 FO document to read data from or write data to D365 FO.


Standard procedure

1. Click Connectivity studio Integration Design.
2. Click the Documents tab.
3. Click New.
4. Define a meaningful name for the document.
Example: If the document is used for a sales integration, you can use names like 'Sales - Order' or 'Sales - Invoice'.
  In the Document field, type a value.
 

Note: Best practice: In the document name, do not use the:
- Application: Use the Application field to define the applicable application.
- Document type: Use the Document type field to define the applicable document type.
5. In the Project field, enter or select a value.
6. Define the applicable application for the document. For a D365 FO document, for example, select a 'D365 FO' application.
  In the Application field, enter or select a value.
 

Note: You can only select an application that is defined for the applicable project. You can define project applications on the Projects page.
7. In the Document types field, select 'D365 FO'.
8. Sub-task: Set properties.
  8.1 Expand the Properties section.
  8.2 To improve performance when processing a lot of records, you can use paging. For paging, the records are split over several threads which run these records in parallel batch tasks.
Define the number of records to be processed by one batch task.
  In the Query page size field, enter a number.
 

Note: You can use this calculation to define the number to be entered: Query page size = Total number of records / Number of available threads.
  8.3 On export, if you start the message run manually, you can have the standard D365 FO query page shown before the message is run. You can use this query page to define more-detailed ranges.
  Select Yes in the Prompt field.
 

Note: If the message is run in batch, the standard D365 FO query page is not shown and an error is logged.
  8.4 On import to D365 FO, time validations can be applicable.
By default, the time validation is applied. Which means, this field is set to No. As a result, each import of an instance to which time validation applies, results in a new instance.
If this field is set to Yes, no time validation is applied, and the existing instance is updated.
For example, on import of addresses, the effective period is validated.
  Select Yes in the Disable time validation field.
9. Sub-task: Set (custom) handler.
  9.1 Expand the Custom section.
  9.2 For a D365 FO document, several standard handler classes are available.
You can use a customized handler class. To do so, extend a standard handler class.
  In the Handler field, enter or select the desired handler class.
 

Note: For a list and description of the standard D365 FO handler classes, refer to the Notes section of this topic.
10. Close the page.

Notes

For a D365 FO document, several standard handler classes are available:

Handler class Description
BisDocumentAxDatabase This handler class reads data from or writes data to D365 FO.
BisDocumentAxDatabase_CompanyHeader If you use EDI, you can also use this handler class. This handler class imports data into D365 FO. On import, it switches to the company as defined in the EDI history and imports the data into that company.
BisDocumentHistoryAxDatabase This handler class runs the message from the message history. It is automatically applied if you manually run a message from the message history. So, do not select it for a document.
BisDocumentAxDB_SalesOrderPostInvoice This handler class creates sales orders and automatically reserves the sales quantities. If the quantities are reserved for a sales order, the sales order invoices are created and posted automatically. If the quantities cannot be reserved, the created sales order is deleted.
BisDocumentAxDB_InventCounting This EDI-specific handler class creates inventory counting journals.
BisDocumentAxPurchaseOrderAutoConfirm This EDI-specific handler class imports purchase order confirmations and automatically confirms the purchase orders. You can only use this handler class to import a purchase order confirmation from the BisEdiPurchaseJour staging table.
BisDocumentAxDatabase_DataEntryWorkflow This handler class is specific for the Connectivity studio integration with Data entry workflow. Only use this handler class on a target document of a data import message. This handler class starts a data entry workflow. The imported data is imported in the data entry workflow staging table. The data entry workflow tasks are based on the imported data. You can, for example, use this to start a data entry workflow to complete and review the imported data before it is imported in the relevant D365 FO tables. If you select this handler class on the D365 FO document, a Data entry workflow section is added to the document header. Here you can select the desired data entry workflow template that is used to start the data entry workflow.
BisDocumentLoyaltyCardPointAdj This handler class imports loyalty card reward point adjustments. Each adjustment is logged with a unique sequence number.
BisDocumentPickingListRegistration This handler class imports and creates picking lists. When a picking list is created, the related picking route is updated.
BisDocumentPickingListRegistrationCancelUnpicked This handler class imports and creates picking lists. When a picking list is created, the related picking route is updated.
If, at least, one line is picked, all non picked (activated) lines are set to cancelled and the picklist is finished.
BisDocumentPickingListRegistrationPostAll

This handler class imports and creates picking lists. When a picking list is created, the related picking route is updated. Also the packing slip and the invoice of the linked sales order are posted.
BisDocumentPickingListRegistrationPostAllCancelUnpicked This handler class imports and creates warehouse orders. When a warehouse order is created, the related picking routes is updated. Also, the packing slip and the invoice of the linked sales order are posted.
BisDocumentPickingListRegistrationPostPackingSlip This handler class imports and creates the picking list, updates the route, and posts the packing slip. 
   
BisDocumentAxDB_TransferOrderWave This handler class creates transfer orders. If a created transfer order is validated, it is automatically released.
BisDocumentAxDB_CustVendTransOpen This handler class exports open customer transactions or vendor transactions, depending on document record setup.
BisMdmDocumentAxDatabase This handler class exports data from D365 FO for Master data management (MDM).
BisDocumentWsHistoryAxDatabase This handler class uses the web service request data to process the web service response, if no response data is received from the web service. Only use this handler class when you process one record at once.
BisDocumentWsHistoryAxDatabaseV2 This handler class uses the web service request data to process the web service response, if no response data is received from the web service. You can use this handler class when you process several record at once.
BisDocumentAxDatabase_DataEntryWorkflow This handler class starts a data entry workflow. Only use this handler class on a target document on a data import message. The imported data is imported in the data entry workflow staging table. The data entry workflow tasks are based on the imported data.
BisEdiDocumentAxChangeCompany This handler class runs an EDI message to move data from the staging journal to D365 FO in the company/legal entity as defined in the BisEdiHistory table.

 

You can also select several other standard handler classes. These other handler classes also extend the BisDocumentAxDatabase class. However, these are related to the journal and staging document types that have specific properties related to these handler classes. Therefore, selecting these other handler classes for the D365 FO document type does not give an optimal result.

See also

Provide feedback