authentication synchronous calls batched data apis

Authentication Synchronous Calls Batched Data APIs

Calling external serviceTriggers Web hooks

Data warehouse Integration

What are the Dynamics 365 Integration Components?

Data Entity (simplified projection of schema)

Azure SQL DatabaseRowStore & ColumnStore

OData(HTTPS/JSON/XML)

REST(HTTPS/JSON)

SOAP(HTTPS/XML)

X++ Class

X++ Class Table(s)Relational

QueryAggregate

Query

Single record or

batched records

Data Import/Export Framework (DIXF)

Transform Validation Mapping

Asynchronous high volume interface

File UploadData

Staging

Application Server (AOS)

1700+ entities

What are the Dynamics 365 Integration Components?

Data Entity (simplified projection of schema)

Azure SQL DatabaseRowStore & ColumnStore

OData(HTTPS/JSON/XML)

REST(HTTPS/JSON)

SOAP(HTTPS/XML)

X++ Class

X++ Class Table(s)Relational

QueryAggregate

Query

Single record or

batched records

Data Import/Export Framework (DIXF)

Transform Validation Mapping

Asynchronous high volume interface

File UploadData

Staging

Application Server (AOS)

Application Lifecycle (LCS) data management tasks e.g.

- Data migration for initial system load- Move data between AX instances (Test→ Prod)- Master data synchronization etc.

Azure App Services(BizTalk or Logic App)

Custom Apps

& integrations

1700+ entities

Entity Configure

Compare

Copy

MDM

Integration

Data Migration

Import

Export

Entity

What is the structure a data entity?

Party

(DirPartyTable)

Location

(LogisticsLocation)

Party-Location

relationship

(DirPartyLocation)

Location roles

(LogisticsLocationRole)

Party-Location role

relationship

(DirPartyLocationRole)

Customer

(CustTable)

Electronic address

(LogisticsElectron icAddre

ss)

Postal address

(LogisticsPostalAddress)

Customer Entity

• Account number

• Customer group

• Bank account

• Party number

• Name

• Primary postal address

• Primary email address

• Primary fax number

For example, in normalized tables, a lot of the data for each customer might be stored in a customer table, and then the rest might be spread across a small set of related tables. In this case, the data entity for the customer concept appears as one de-normalized view, in

which each row contains all the data from the customer table and its related tables.

REST(HTTPS/JSON)

SOAP(HTTPS/XML)

X++ Class

APP DEVELOPERS

USERS

MOBILE APPS

APPS

PARTNERS ANDAFFILIATES

API

AZURE API MANAGEMENT

DEVELOPER PORTALREGISTRATIONDOCUMENTATIONINTERACTIVE API CONSOLEDEVELOPER ANALYTICSAPP GALLERYFORUMSNEWSISSUESWIKI

API PROXYSCALINGCACHINGMONITORING

TRAFFIC MANAGEMENT

ADMIN PORTALAPI PUBLISHINGSUBSCRIPTION MANAGEMENTSECURITY

MEDIATIONCONTENT PUBLISHINGSITE CUSTOMIZATIONISSUE MANAGEMENTANALYTICSREPORTS

Decision point Recurring integrations API On Demand Package API

Scheduling Scheduling in Finance and Operations Scheduling outside Finance and Operations

Format Files and data packages Only data packages

Transformation Support for Extensible Stylesheet Language

Transformations (XSLT) if the data file is in XML

format

Transformations that are external to the system

Supported

protocols

SOAP and REST REST

Service type Custom service Open Data Protocol (OData) action

Availability February 2016 release (RTW) and later Platform update 5 and later