Select a data integration (import/export) strategy in x++

  it is always wise to be aware of available integration tools.

The following integration patterns are available for finance and operations apps:

  • OData
  • Batch data API
  • Custom service
  • Consume external web services
  • Excel integration

OData : 


 It is a standard protocol for creating and consuming data.
The purpose of OData is to provide a protocol that is based on Representational State Transfer (REST) for create, read, update, and delete (CRUD) operations. 

Batch data API :

Use the batch data API in scenarios that require one or both Data management package REST API and Recurring integrations. 
Both APIs support data import scenarios and data export scenarios.

Custom service :

A developer can create custom services for finance and operations apps. When a developer writes a custom service under a service group, the service group is always deployed on two endpoints:

Consume external web services

A developer consumes web services by adding new class libraries to finance and operations apps.

Excel integration

The Microsoft Office integration capabilities provide users with a productive environment that helps them get the job done by using Office products. 

Microsoft Excel can change and quickly analyze data.

The Excel Data Connector app interacts with Excel workbooks and OData services that are created for publicly exposed data entities.


Synchronous vs. asynchronous integration patterns

Processing can be either synchronous or asynchronous. Often, the type of processing that you must use determines the integration pattern that you choose.

A synchronous pattern is a blocking request and response pattern, where the caller is blocked until the recipient has finished running the Excel integration and gives a response. An asynchronous pattern is a non-blocking pattern, where the caller submits the request and then continues without waiting for a response.

Consider using OData for synchronous and Batch data API for asynchronous integration scenarios.


Comments

Post a Comment

Popular posts from this blog

how to post trade agreement journals automatically using x++ code

  In Microsoft Dynamics AX, you can post trade agreement journals automatically using X++ code. Here are the steps to do so: Create a new job in X++. Write a code to fetch data from the trade agreement table. Create a journal header and journal lines based on the fetched data. Call the post() method of the journal header to post the journal. Repeat steps 2 to 4 for each trade agreement. Here's a sample code in X++: static void postTradeAgreementJournals(Args _args) { TradeAgreementTable tradeAgreementTable; GeneralJournalHeader generalJournalHeader; GeneralJournalLine generalJournalLine; // Fetch data from the Trade Agreement table select tradeAgreementTable where tradeAgreementTable.JournalPosting == NoYes::No; // Loop through each trade agreement while (tradeAgreementTable) { // Create a journal header generalJournalHeader = new GeneralJournalHeader(); generalJournalHeader.initValue(); generalJournalHeader.tra...
Read more

How to Create a wizard in x++ d365

Image
 step1: Create a form and apply form pattern as wizard step2 : create a class and extend the class with SysWizard. code :            class BAS_WIzardScreen extends SysWizard {     #MACROLIB.AviFiles     FormName formname()     {         return formstr(BAS_WIzardForm);  // name of the wizard form     }     public void run()     {         info(strFmt("Thankyou"));     }     public void setupNavigation()     {     }     public boolean validate()     {         return true;     }     public static str description()     {         return "BASOFA WIZARD";  // title of the wizard     }     public static void main(Args _args)     {         BAS_WIzardScreen wizard = new BAS_WIz...
Read more

x++ code to submit and approve and reject the invent movement workflow in d365 F&O

 class Class1 {     public  void submitworkflow()     {         InventJournalTable journalTable;     WorkflowWorkItemTable   WorkflowWorkItemTable;    WorkflowVersionTable        workflowVersionTable;                journalTable = InventJournalTable::find('00446');               // submit to workflow         if (journalTable.WorkflowApprovalStatus == InventJournalWorkflowApprovalStatus::NotSubmitted)         {             Workflow::activateFromWorkflowType(workFlowTypeStr(InventJournalMovementTemplate), journalTable.RecId,                                     'Workflow submitted by button', false, Curuserid());         }    ...
Read more