Integrating With Dynamics AX

Past, Present, Future

4

Session Abstract

Want to know more about AX integration? In this session you will learn about the Web Service Adapter: usage, configuration, and how to approach the extension of the Jumpstart beyond the basic template Scribe provides. You will also hear from Scribe’s Product Management team as they discuss our plans for AX integrations.

© 2015 Scribe Software Corporation. All rights reserved. 5

Insight 7.9.0 New Features Agenda

• Past:

• Using Insight to Work with Dynamics AX 2009 (AX 5)

• Present:

• Using Insight to Work with Dynamics AX 2012 (AX 6)

• Jumpstart: Out-of-the-Box

• Jumpstart: Extending

• Future:

• Looking Forward: Dynamics AX 2012 Integration

• Looking Forward: Dynamics AX 7 Integration

PAST: Connecting to Dynamics AX 2009 (AX 5)Scribe Adapter Design

• Traditional Scribe API Adapter

• AX Access through .NET Business Connector

◦ Application Integration Framework (AIF) available, still new

• User experience much like interacting with other applications with Insight

PRESENT: Connecting to Dynamics AX 2012 (AX 6)Dynamics AX Changes

• Application Overhaul

◦ Database

• Relational data structure changes

◦ Integration Best Practices

• Last version to support .NET Business Connector

• First version to recommend AIF as integration best-practice

PRESENT: Connecting to Dynamics AX 2012 (AX 6)Recommended Dynamics AX Integration Method

• Integration based on industry standards

• AIF Document Services – Service Operations

◦ Can be published as SOAP-based web service endpoints

◦ Endpoints exchange information using XML

PRESENT: Connecting to Dynamics AX 2012 (AX 6)Scribe Adapter Design Goals

• Enable connectivity to AX Document Service Operations

• Enable connection to similar standards-based interfaces

◦ XML communication to a published SOAP web service definition

• Leverage AX logic when publishing

PRESENT: Connecting to Dynamics AX 2012 (AX 6)Scribe Adapter Design Decisions

• To interface with an open architecture, create an open adapter

◦ Flatten hierarchical data structures

• Avoid redesign of platform built for relational data structures

◦ Drive Adapter features with AX implementation details

• Other web services are likely to implement them as well

◦ Limit publisher to a defined use case, keep UI simple

• Typical Scribe UI impractical across all entities

PRESENT: Connecting to Dynamics AX 2012 (AX 6)Scribe User Experience Compared to Other Adapters

• Flattened Hierarchy

◦ DTS = construction of XML payload execution of method

◦ Provide access to array parameters

• Present array parameters as entities – accessible as steps

12

PRESENT: Connecting to Dynamics AX 2012 (AX 6)Scribe User Experience Compared to Other Adapters

• Flattened Hierarchy

◦ Build in method execution timing

• Method execution and related arrays as a repeating group

• Implement repeating group automatically

• Completion of a repeating group triggers method

14

PRESENT: Connecting to Dynamics AX 2012 (AX 6)Scribe User Experience Compared to Other Adapters

• Adapter Features

◦ Handling fixed and variable arrays

16

17

18

19

20

PRESENT: Connecting to Dynamics AX 2012 (AX 6)Scribe User Experience Compared to Other Adapters

• Adapter Features

◦ Handling class inheritance

22

PRESENT: Connecting to Dynamics AX 2012 (AX 6)Scribe User Experience Compared to Other Adapters

• Publisher

◦ No direct database access

◦ No methods for creating customizations

◦ Provide a mechanism for deploying custom code

24

PRESENT: Connecting to Dynamics AX 2012 (AX 6)Scribe User Experience Compared to Other Adapters

• Publisher

◦ Provides a user interface to

• Configure customizations

• Support a publisher experience similar to other Scribe publishers

26

PRESENT: Connecting to Dynamics AX 2012 (AX 6)Benefits and Challenges

• Benefits

◦ Access to highly customizable systems

◦ Uniform Scribe interface

• Challenges

◦ More application knowledge required

◦ More infrastructure configuration required

The Dynamics AX and Dynamics CRM JumpstartOut-of-the-Box

• Basic functionality

• All implementations will go beyond this functionality

◦ Modified field mappings

◦ Modified entity/publication logic

◦ Custom entities (source, target, publication)

The Dynamics AX and Dynamics CRM JumpstartExtending

• Specific skill sets required

◦ Business logic expertise

◦ Application Integration Framework expertise

• Document Services

• X++ coding

The Dynamics AX and Dynamics CRM JumpstartExtending

• Service Considerations (Source/Target)

◦ Data requirements

• Data and operational fields

◦ Structure requirements

• Building and interacting with arrays

◦ Technical requirements

• Inheritance

The Dynamics AX and Dynamics CRM JumpstartExtending

• Publishing Considerations

◦ Understanding Scribe’s publication logic

• XML message requirements

◦ Obtaining XML body metadata

◦ Populating XML body data

◦ Adding XML envelope required by Scribe

◦ Posting XML message to the ScribeIn queue

32

XML Metadata

33

Construct and Post XML Message

FUTURE: Dynamics AX 2012 (AX 6)

• Handle More Use Cases

◦ Improve

• Error handling

• Publishing

• Queue management

FUTURE: Dynamics AX 7

• Integration methodology is switching from AIF to OData

• Cloud release planned for Q4 2015

• On premise release 3-6 months later

Scribe Connectivity

• Scribe Online OData connectivity first

• Insight connectivity after the on premise release

36

Q+A

37

THANK YOU