30
Informatica ® Cloud (Version Spring 2017) Microsoft Dynamics AX V3 Connector Guide
Informatica® Cloud (Version Spring 2017)
Microsoft Dynamics AX V3 Connector Guide
Informatica Cloud Microsoft Dynamics AX V3 Connector Guide
Version Spring 2017April 2017
© Copyright Informatica LLC 2016, 2017
This software and documentation contain proprietary information of Informatica LLC and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC. This Software may be protected by U.S. and/or international Patents and other Patents Pending.
Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013©(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.
The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing.
Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging, Informatica Master Data Management, and Live Data Map are trademarks or registered trademarks of Informatica LLC in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners.
Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights reserved. Copyright © Sun Microsystems. All rights reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All rights reserved. Copyright © Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright © Meta Integration Technology, Inc. All rights reserved. Copyright © Intalio. All rights reserved. Copyright © Oracle. All rights reserved. Copyright © Adobe Systems Incorporated. All rights reserved. Copyright © DataArt, Inc. All rights reserved. Copyright © ComponentSource. All rights reserved. Copyright © Microsoft Corporation. All rights reserved. Copyright © Rogue Wave Software, Inc. All rights reserved. Copyright © Teradata Corporation. All rights reserved. Copyright © Yahoo! Inc. All rights reserved. Copyright © Glyph & Cog, LLC. All rights reserved. Copyright © Thinkmap, Inc. All rights reserved. Copyright © Clearpace Software Limited. All rights reserved. Copyright © Information Builders, Inc. All rights reserved. Copyright © OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rights reserved. Copyright © International Organization for Standardization 1986. All rights reserved. Copyright © ej-technologies GmbH. All rights reserved. Copyright © Jaspersoft Corporation. All rights reserved. Copyright © International Business Machines Corporation. All rights reserved. Copyright © yWorks GmbH. All rights reserved. Copyright © Lucent Technologies. All rights reserved. Copyright © University of Toronto. All rights reserved. Copyright © Daniel Veillard. All rights reserved. Copyright © Unicode, Inc. Copyright IBM Corp. All rights reserved. Copyright © MicroQuill Software Publishing, Inc. All rights reserved. Copyright © PassMark Software Pty Ltd. All rights reserved. Copyright © LogiXML, Inc. All rights reserved. Copyright © 2003-2010 Lorenzi Davide, All rights reserved. Copyright © Red Hat, Inc. All rights reserved. Copyright © The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright © EMC Corporation. All rights reserved. Copyright © Flexera Software. All rights reserved. Copyright © Jinfonet Software. All rights reserved. Copyright © Apple Inc. All rights reserved. Copyright © Telerik Inc. All rights reserved. Copyright © BEA Systems. All rights reserved. Copyright © PDFlib GmbH. All rights reserved. Copyright © Orientation in Objects GmbH. All rights reserved. Copyright © Tanuki Software, Ltd. All rights reserved. Copyright © Ricebridge. All rights reserved. Copyright © Sencha, Inc. All rights reserved. Copyright © Scalable Systems, Inc. All rights reserved. Copyright © jQWidgets. All rights reserved. Copyright © Tableau Software, Inc. All rights reserved. Copyright© MaxMind, Inc. All Rights Reserved. Copyright © TMate Software s.r.o. All rights reserved. Copyright © MapR Technologies Inc. All rights reserved. Copyright © Amazon Corporate LLC. All rights reserved. Copyright © Highsoft. All rights reserved. Copyright © Python Software Foundation. All rights reserved. Copyright © BeOpen.com. All rights reserved. Copyright © CNRI. All rights reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and/or other software which is licensed under various versions of the Apache License (the "License"). You may obtain a copy of these Licenses at http://www.apache.org/licenses/. Unless required by applicable law or agreed to in writing, software distributed under these Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the Licenses for the specific language governing permissions and limitations under the Licenses.
This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright © 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under various versions of the GNU Lesser General Public License Agreement, which may be found at http:// www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.
The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine, and Vanderbilt University, Copyright (©) 1993-2006, all rights reserved.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution of this software is subject to terms available at http://www.openssl.org and http://www.openssl.org/source/license.html.
This product includes Curl software which is Copyright 1996-2013, Daniel Stenberg, <[email protected]>. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
The product includes software copyright 2001-2005 (©) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://www.dom4j.org/ license.html.
The product includes software copyright © 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://dojotoolkit.org/license.
This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html.
This product includes software copyright © 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at http:// www.gnu.org/software/ kawa/Software-License.html.
This product includes OSSP UUID software which is Copyright © 2002 Ralf S. Engelschall, Copyright © 2002 The OSSP Project Copyright © 2002 Cable & Wireless Deutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php.
This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software are subject to terms available at http:/ /www.boost.org/LICENSE_1_0.txt.
This product includes software copyright © 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at http:// www.pcre.org/license.txt.
This product includes software copyright © 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http:// www.eclipse.org/org/documents/epl-v10.php and at http://www.eclipse.org/org/documents/edl-v10.php.
This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://www.stlport.org/doc/ license.html, http://asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://httpunit.sourceforge.net/doc/ license.html, http://jung.sourceforge.net/license.txt , http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/license.html, http://www.libssh2.org, http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3- license-agreement; http://antlr.org/license.html; http://aopalliance.sourceforge.net/; http://www.bouncycastle.org/licence.html; http://www.jgraph.com/jgraphdownload.html; http://www.jcraft.com/jsch/LICENSE.txt; http://jotm.objectweb.org/bsd_license.html; . http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231; http://www.slf4j.org/license.html; http://nanoxml.sourceforge.net/orig/copyright.html; http://www.json.org/license.html; http://forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://www.sqlite.org/copyright.html, http://www.tcl.tk/software/tcltk/license.html, http://www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html, http://www.slf4j.org/license.html; http://www.iodbc.org/dataspace/iodbc/wiki/iODBC/License; http://www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http://www.edankert.com/bounce/index.html; http://www.net-snmp.org/about/license.html; http://www.openmdx.org/#FAQ; http://www.php.net/license/3_01.txt; http://srp.stanford.edu/license.txt; http://www.schneier.com/blowfish.html; http://www.jmock.org/license.html; http://xsom.java.net; http://benalman.com/about/license/; https://github.com/CreateJS/EaselJS/blob/master/src/easeljs/display/Bitmap.js; http://www.h2database.com/html/license.html#summary; http://jsoncpp.sourceforge.net/LICENSE; http://jdbc.postgresql.org/license.html; http://protobuf.googlecode.com/svn/trunk/src/google/protobuf/descriptor.proto; https://github.com/rantav/hector/blob/master/LICENSE; http://web.mit.edu/Kerberos/krb5-current/doc/mitK5license.html; http://jibx.sourceforge.net/jibx-license.html; https://github.com/lyokato/libgeohash/blob/master/LICENSE; https://github.com/hjiang/jsonxx/blob/master/LICENSE; https://code.google.com/p/lz4/; https://github.com/jedisct1/libsodium/blob/master/LICENSE; http://one-jar.sourceforge.net/index.php?page=documents&file=license; https://github.com/EsotericSoftware/kryo/blob/master/license.txt; http://www.scala-lang.org/license.html; https://github.com/tinkerpop/blueprints/blob/master/LICENSE.txt; http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html; https://aws.amazon.com/asl/; https://github.com/twbs/bootstrap/blob/master/LICENSE; https://sourceforge.net/p/xmlunit/code/HEAD/tree/trunk/LICENSE.txt; https://github.com/documentcloud/underscore-contrib/blob/master/LICENSE, and https://github.com/apache/hbase/blob/master/LICENSE.txt.
This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and Distribution License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code License Agreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php), the new BSD License (http://opensource.org/licenses/BSD-3-Clause), the MIT License (http://www.opensource.org/licenses/mit-license.php), the Artistic License (http://www.opensource.org/licenses/artistic-license-1.0) and the Initial Developer’s Public License Version 1.0 (http://www.firebirdsql.org/en/initial-developer-s-public-license-version-1-0/).
This product includes software copyright © 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For further information please visit http://www.extreme.indiana.edu/.
This product includes software Copyright (c) 2013 Frank Balluffi and Markus Moeller. All rights reserved. Permissions and limitations regarding this software are subject to terms of the MIT license.
See patents at https://www.informatica.com/legal/patents.html.
DISCLAIMER: Informatica LLC provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica LLC does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice.
NOTICES
This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software Corporation ("DataDirect") which are subject to the following terms and conditions:
1.THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.
Publication Date: 2017-04-07
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Informatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Informatica Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Informatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Informatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Informatica Product Availability Matrixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Informatica Velocity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Informatica Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Informatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 1: Introduction to Microsoft Dynamics AX V3 Connector. . . . . . . . . . . . . . . . 8Microsoft Dynamics AX V3 Connector Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Microsoft Dynamics AX V3 Connector Task and Object Types. . . . . . . . . . . . . . . . . . . . . . . . . . 8
Administration of Microsoft Dynamics AX V3 Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Install Web Services on Internet Information Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Exchange Documents by Using the HTTP Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Configure Troubleshooting Options for Integration Ports. . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 2: Microsoft Dynamics AX V3 Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . 11Microsoft Dynamics AX V3 Connections Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Microsoft Dynamics AX V3 Connection Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 3: Microsoft Dynamics AX V3 Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Microsoft Dynamics AX V3 Operations Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Microsoft Dynamics AX V3 Source and Target Operations. . . . . . . . . . . . . . . . . . . . . . . . 13
Microsoft Dynamics AX V3 Source Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configuring a Request Using Request Message Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Parameterize Input Values in a Request Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Field Mapping in a Source Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Creating Packed Fields in a Field Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Microsoft Dynamics AX V3 Target Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Field Mapping in a Target Transformation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Rules and Guidelines for Microsoft Dynamics AX V3 Operations. . . . . . . . . . . . . . . . . . . . . . . 22
Chapter 4: Mappings and Mapping Configuration Tasks with Microsoft Dynamics AX V3 Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Mappings and Mapping Configuration Tasks with Microsoft Dynamics AX V3 Connector Overview. 23
Microsoft Dynamics AX V3 Sources in Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Microsoft Dynamics AX V3 Targets in Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Microsoft Dynamics AX V3 Midstream Transformation in Mappings. . . . . . . . . . . . . . . . . . . . . . 25
4 Table of Contents
Advanced Midstream Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 5: Data Type Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Data Type Reference Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Microsoft Dynamics AX 2012 and Transformation Data Types. . . . . . . . . . . . . . . . . . . . . . . . . 28
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Table of Contents 5
PrefaceThe Informatica Cloud Microsoft Dynamics AX V3 Connector Guide contains information about how to set up and use Microsoft Dynamics AX V3 Connector. The guide explains how business users can use Microsoft Dynamics AX V3 Connector to read data from and write data to Microsoft Dynamics AX 2012.
Informatica Resources
Informatica NetworkInformatica Network hosts Informatica Global Customer Support, the Informatica Knowledge Base, and other product resources. To access Informatica Network, visit https://network.informatica.com.
As a member, you can:
• Access all of your Informatica resources in one place.
• Search the Knowledge Base for product resources, including documentation, FAQs, and best practices.
• View product availability information.
• Review your support cases.
• Find your local Informatica User Group Network and collaborate with your peers.
Informatica Knowledge BaseUse the Informatica Knowledge Base to search Informatica Network for product resources such as documentation, how-to articles, best practices, and PAMs.
To access the Knowledge Base, visit https://kb.informatica.com. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team at [email protected].
Informatica DocumentationTo get the latest documentation for your product, browse the Informatica Knowledge Base at https://kb.informatica.com/_layouts/ProductDocumentation/Page/ProductDocumentSearch.aspx.
If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through email at [email protected].
6
Informatica Product Availability MatrixesProduct Availability Matrixes (PAMs) indicate the versions of operating systems, databases, and other types of data sources and targets that a product release supports. If you are an Informatica Network member, you can access PAMs at https://network.informatica.com/community/informatica-network/product-availability-matrices.
Informatica VelocityInformatica Velocity is a collection of tips and best practices developed by Informatica Professional Services. Developed from the real-world experience of hundreds of data management projects, Informatica Velocity represents the collective knowledge of our consultants who have worked with organizations from around the world to plan, develop, deploy, and maintain successful data management solutions.
If you are an Informatica Network member, you can access Informatica Velocity resources at http://velocity.informatica.com.
If you have questions, comments, or ideas about Informatica Velocity, contact Informatica Professional Services at [email protected].
Informatica MarketplaceThe Informatica Marketplace is a forum where you can find solutions that augment, extend, or enhance your Informatica implementations. By leveraging any of the hundreds of solutions from Informatica developers and partners, you can improve your productivity and speed up time to implementation on your projects. You can access Informatica Marketplace at https://marketplace.informatica.com.
Informatica Global Customer SupportYou can contact a Global Support Center by telephone or through Online Support on Informatica Network.
To find your local Informatica Global Customer Support telephone number, visit the Informatica website at the following link: http://www.informatica.com/us/services-and-training/support-services/global-support-centers.
If you are an Informatica Network member, you can use Online Support at http://network.informatica.com.
Preface 7
C H A P T E R 1
Introduction to Microsoft Dynamics AX V3 Connector
This chapter includes the following topics:
• Microsoft Dynamics AX V3 Connector Overview, 8
• Microsoft Dynamics AX V3 Connector Task and Object Types, 8
• Administration of Microsoft Dynamics AX V3 Connector, 9
Microsoft Dynamics AX V3 Connector OverviewYou can use Microsoft Dynamics AX V3 Connector to connect to Microsoft Dynamics AX 2012 from Informatica Cloud.
Use Microsoft Dynamics AX V3 Connector to securely read data from or write data to Microsoft Dynamics AX 2012. You can use Microsoft Dynamics AX V3 objects as sources and targets in mappings and Mapping Configuration tasks.
ExampleYou want to migrate customer details from Microsoft Dynamics AX 2012 to an SQL Server database. You can use Microsoft Dynamics AX V3 Connector to read customer data from Microsoft Dynamics AX 2012 and write to an SQL Server database.
Microsoft Dynamics AX V3 Connector Task and Object Types
When you create a Microsoft Dynamics AX V3 connection to perform a task, you can select objects supported by Microsoft Dynamics AX V3 Connector for the task.
8
The following table provides the list of tasks and object types supported by Microsoft Dynamics AX V3 Connector:
Task Type Source Target Lookup
Data Synchronization No No No
Mapping Configuration Yes Yes No
Administration of Microsoft Dynamics AX V3 Connector
As a user, you can use Microsoft Dynamics AX V3 Connector after the organization administrator performs the following tasks:
• Install the web services on Internet Information Services
• Exchange documents by using HTTP adapter
• Configure troubleshooting options for integration ports
Install Web Services on Internet Information ServicesInstall the Microsoft Dynamics AX 2012 web services on Internet Information Services.
An Application Object Server is a Microsoft Windows service that controls communications among Microsoft Dynamics AX 2012 clients, databases, and applications. The Application Object Server hosted services are available to users and applications across an intranet. If you want to use services over the internet, you must host services on Internet Information Services. If you do not want to use services over the internet, you can skip this procedure.
To install the web services on Internet Information Service, see https://technet.microsoft.com/en-in/library/gg731848.aspx.
Exchange Documents by Using the HTTP AdapterTo read data from or write data to Microsoft Dynamics AX 2012, you must use an inbound integration port together with the HTTP adapter. The HTTP adapter enables synchronous communication through a website. You can create an inbound integration port and use the connector to read data from or write data to Microsoft Dynamics AX 2012. For example, create an inbound integration port and use C# code to create a command-line program that reads a specific sales order.
To create and configure the integration port, to create an HTTP client application, and to read a sales order, see https://technet.microsoft.com/en-us/library/hh496418.aspx.
Configure Troubleshooting Options for Integration PortsYou can configure troubleshooting settings in services and application integration framework. Use either the inbound ports form or the outbound ports form.
To configure the logging mode, error messaging, and security for integration ports, see https://technet.microsoft.com/en-us/library/hh202045.aspx.
Administration of Microsoft Dynamics AX V3 Connector 9
To manage integration ports, see https://technet.microsoft.com/en-us/library/aa496471.aspx.
10 Chapter 1: Introduction to Microsoft Dynamics AX V3 Connector
C H A P T E R 2
Microsoft Dynamics AX V3 Connections
This chapter includes the following topics:
• Microsoft Dynamics AX V3 Connections Overview, 11
• Microsoft Dynamics AX V3 Connection Properties, 11
Microsoft Dynamics AX V3 Connections OverviewCreate a Microsoft Dynamics AX V3 connection to connect to Microsoft Dynamics AX 2012 so that the agent can read data from and write data to Microsoft Dynamics AX 2012. You can use Microsoft Dynamics AX V3 connections to specify sources and targets in mappings and Mapping Configuration tasks.
You can create a Microsoft Dynamics AX V3 connection on the Connections page. Use the connection when you create a mapping or Mapping Configuration task.
Microsoft Dynamics AX V3 Connection PropertiesWhen you set up a Microsoft Dynamics AX V3 connection, you must configure the connection properties.
The following table describes the Microsoft Dynamics AX V3 connection properties:
Connection Property
Description
Connection Name Enter a unique name for the connection.
Description Optional. Provide a relevant description for the connection.
Type Select Microsoft Dynamics AX V3 from the list.
Runtime Environment The name of the runtime environment where you want to run the tasks.
Authentication Authenticates users who want to access Microsoft Dynamics AX 2012. Microsoft Dynamics AX V3 Connector supports Basic and NTLM authentication.
11
Connection Property
Description
WSDL URI Enter the required WSDL file path.Note: To find the WSDL URI, go to System Administration > Inbound Ports in the Microsoft Dynamics AX 2012 instance. For example, the format of WSDL URI is http://<Hostname>:<Port>/<App_Pool_Name>/<Port name>/xppservice.svc.
Username The user name to login to the Microsoft Dynamics AX 2012 web page.
Password The password associated with the NT login user.
Company Name Optional. Enter your company name. You can enter multiple company names separated by semi-colons. For example, ceu;ceed.
Language Optional. Localizes the data you read from or write to Microsoft Dynamics AX 2012. Specify the language code.
12 Chapter 2: Microsoft Dynamics AX V3 Connections
C H A P T E R 3
Microsoft Dynamics AX V3 Operations
This chapter includes the following topics:
• Microsoft Dynamics AX V3 Operations Overview, 13
• Microsoft Dynamics AX V3 Source Operations, 14
• Microsoft Dynamics AX V3 Target Operations, 19
• Rules and Guidelines for Microsoft Dynamics AX V3 Operations, 22
Microsoft Dynamics AX V3 Operations OverviewMicrosoft Dynamics AX V3 exposes the web service API that the Secure Agent uses to perform integration tasks through the SOAP protocol.
When you create a mapping, you can associate a Microsoft Dynamics AX V3 connection and an operation. Based on the Microsoft Dynamics AX 2012 WSDL you specify in the connection, the Secure Agent connects to the corresponding web service in Microsoft Dynamics AX 2012 to access, transform, or deliver data. The request and response are SOAP messages. The SOAP request and response messages contain hierarchical data, where the data follows an XML schema. If you want to write data to a relational target, the Secure Agent converts the hierarchical data fetched from Microsoft Dynamics AX 2012 to relational data.
Microsoft Dynamics AX V3 Source and Target OperationsThe following table describes the source operations that you can perform with Microsoft Dynamics AX V3 Connector:
Operation Name Description
read Uses one or more IDs to read records from the database and returns the records.
readAll Retrieves all the records from Microsoft Dynamics AX 2012 as an object or an XML document.
find Queries the database for matching records and returns records as an object or an XML document.
findKeys Uses criteria to query the database for matching records and returns a list of corresponding IDs for those records.
13
Operation Name Description
getKeys Retrieves the IDs for documents based on the specified filter.
getChangedKeys Retrieves the IDs for documents based on the specified filter and a date that is provided.
The following table describes the target operations that you can perform with Microsoft Dynamics AX V3 Connector:
Operation Name
Description
create Uses an object or an XML document to create records in the database and returns a list of IDs for the new records.
delete Uses one or more IDs to delete the specified records from the database.
update Uses an object or an XML document to update records in the database.When you perform an update operation, Microsoft Dynamics AX V3 Connector replaces all fields in the database tables with the fields from the submitted document.Note: Microsoft Dynamics AX V3 Connector does not support partial update.
Microsoft Dynamics AX V3 Source OperationsCreate a source transformation in the Mapping Designer to read data from Microsoft Dynamics AX 2012.
When you select a Microsoft Dynamics AX V3 connection for a source transformation in a mapping to read data from Microsoft Dynamics AX 2012, you can select an operation based on the imported WSDL.
After you specify the configured connection, specify All Operations on the Source tab of the source transformation. The Secure Agent displays all the supported operations. You can select the operation that you want to perform. When you select Read Operations, a subset of the available read operations for the WSDL appears.
Select the operation you require, configure the request message in XML from the sample template provided, and configure the advanced properties for the operation. If you want to write to a relational target, define a relational structure for the customer data by mapping the incoming fields that is in hierarchical format to the output fields in relational format. When you run the mapping, the Secure Agent retrieves data for the specified operation from Microsoft Dynamics AX 2012.
Configuring a Request Using Request Message EditorWhen you create a source transformation, configure an XML request message for the operation that you want to perform in Microsoft Dynamics AX V3.
Use the Request Message Editor to create a request message. The request message is in XML format. You can use the default request message for the operation and then customize the request message to specify the data that you want to enter into the data flow.
To customize your request, copy the request message from the sample template to the Request Message Editor pane where you can edit the XML message and add the attributes for the request.
14 Chapter 3: Microsoft Dynamics AX V3 Operations
For example, you want to perform an operation find using Microsoft Dynamics AX V3 Connector to retrieve data of customers who belong to a particular group. Specify the attribute CustGroup values in the request message to fetch customers who belong to that group. For example, CustGroup Retail Customers.
The following XML sample shows the request input elements that you want in the response:
<!--1 or more repetitions:--><proc:find_INPUT xmlns:proc="http://xml.schemas/infa/procedure/"> <!--Optional:--> <find> <!--1 or more repetitions:--> <CustomerServiceFindRequest> <!--Optional:--> <QueryCriteria> <!--1 or more repetitions:--> <CriteriaElement> <!--1 or more repetitions:--> <DataSourceName> CustTable </DataSourceName> <!--1 or more repetitions:--> <FieldName> CustGroup </FieldName> <!--1 or more repetitions:--> <Operator> Equal </Operator> <!--1 or more repetitions:--> <Value1> 30 </Value1> <!--Optional:--> </CriteriaElement> </QueryCriteria> </CustomerServiceFindRequest> </find></proc:find_INPUT>
Microsoft Dynamics AX V3 Source Operations 15
The following image shows the validated request message in a find operation in the Mapping Designer:
Ensure that you use well-formed XML formatting in the request message. You can verify if the XML request is valid to ensure that the XML matches the structure expected by the operation.
Parameterize Input Values in a Request MessageYou can use in-out parameters to represent input values in a request XML.
Configure the in-out parameters in the Mapping Designer. From the Mapping Designer page, you open the parameters panel and configure an in-out parameter.
16 Chapter 3: Microsoft Dynamics AX V3 Operations
The following image shows a configured CustGroup in-out parameter value:
After you configure a parameter, use the parameter name in the following format, $$Name, in a request message. The XML uses the fields from the parameterized object.
For example, you want to use parameterized CustGroup value in an XML request for a find operation.
The following sample request shows the parameterized values that you can specify in an XML request:
<!--1 or more repetitions:--><proc:find_INPUT xmlns:proc="http://xml.schemas/infa/procedure/"> <!--Optional:--> <find> <!--1 or more repetitions:--> <CustomerServiceFindRequest> <!--Optional:--> <QueryCriteria> <!--1 or more repetitions:--> <CriteriaElement> <!--1 or more repetitions:--> <DataSourceName> CustTable </DataSourceName> <!--1 or more repetitions:--> <FieldName> CustGroup </FieldName> <!--1 or more repetitions:--> <Operator> Equal </Operator> <!--1 or more repetitions:--> <Value1> $$CustGroup </Value1> <!--Optional:--> </CriteriaElement> </QueryCriteria> </CustomerServiceFindRequest> </find></proc:find_INPUT>
Microsoft Dynamics AX V3 Source Operations 17
The following image shows how to use a configured in-out parameter in a Mapping Configuration task:
Field Mapping in a Source TransformationThe response message format follows the service response definition in Microsoft Dynamics AX V3. You can map response fields from a hierarchical to a relational structure of output groups and fields.
After you configure an operation for a source and specify the request message, create the relational format from the hierarchical data to include groups and fields that you want in the output.
To do this, select the elements in the response structure that you want to include as output fields. The Secure Agent converts the XML response in the hierarchical structure to relational groups at run time.
The output groups along with the primary and foreign keys are automatically generated. You can hover the mouse over an output field to view the XPath expression, which indicates which field the output field is mapped to in the response structure of the hierarchy tree.
The following image shows an example hierarchical response structure generated from the request XML for the find operation of customer service:
For example, in the Response Structure pane, you select AccountNum and CustGroup, and then you select Address, which is located under a different parent in the hierarchy. In the Output Fields area, the structure is relational with system-generated primary and foreign keys.
You can map fields from only one output group to a particular branch of the response structure hierarchy. For example, if County is a sibling of nodes that are mapped to the DirParty group, you must map County to the DirParty group.
You can edit the data type, precision, and scale for the groups and fields after mapping the fields.
Creating Packed Fields in a Field MappingYou can reduce the number of output groups for a complex request message by marking fields that you want to pack when you configure the field mapping.
You can pack multiple instances of a single element or a hierarchy of elements into one field. A packed icon displays next to elements marked to be packed, indicating that you can pack the entire element into one output field when you check that element.
18 Chapter 3: Microsoft Dynamics AX V3 Operations
Fields can come from the source that are already marked for packing. You can unpack fields by clicking the pack icon. You cannot select fields that are descendants of packed fields.
The following image shows the packed CustTable element:
When you run the mapping, the agent packs the element and its descendants into a single XML string.
Microsoft Dynamics AX V3 Target OperationsCreate a Target transformation in the Mapping Designer to write data to Microsoft Dynamics AX 2012. When you select a Microsoft Dynamics AX V3 connection for a Target transformation in a mapping, you can select an operation based on the imported WSDL. When you want to write data that is in relational format to Microsoft Dynamics AX 2012, the Secure Agent converts the relational data to a hierarchical format before writing to Microsoft Dynamics AX 2012.
When you configure a Microsoft Dynamics AX 2012 target, you can select Write Operations on the Target tab to display the subset of write operations supported by the WSDL you specified in the Microsoft Dynamics AX V3 connection properties. If you select All Operations, all the supported operations for the WSDL display. The Secure Agent creates target fields based on the request message structure of the operation you select on the Target tab.
When you write data to Microsoft Dynamics AX 2012, the Secure Agent includes all the incoming fields from the source, by default. You can exclude the incoming fields, if required. You can add multiple input groups into the Microsoft Dynamics AX V3 target and define the primary and foreign key relationships between the multiple input groups before you run the mapping.
You can add the input files in a Source transformation, and use the Joiner transformation to join data from multiple files to create one target file. Use the data from the target file to create the final source file.
The following image shows the mapping configured to create one target .csv file that includes all the referential information:
Microsoft Dynamics AX V3 Target Operations 19
The following image shows the fields from the customer object in Microsoft Dynamics AX V3:
The following image shows the fields from the person reference object in Microsoft Dynamics AX V3:
The following image shows the fields from the address reference object in Microsoft Dynamics AX V3:
Use Joiner transformations to join the data from the files.
The following image shows a configured Join condition to join the customer and person reference data:
20 Chapter 3: Microsoft Dynamics AX V3 Operations
The following image shows the included fields for the customer and person reference data:
The following image shows a join condition to join the customer_person and address reference data:
The following image shows the included fields for the customer_person and address reference data:
When you run the mapping, the Secure Agent writes data to a configured target .csv file. Later, use this file as a source from which you write data to Microsoft Dynamics AX 2012.
Field Mapping in a Target TransformationYou can map fields that are in a relational structure to the hierarchical structure used by a Microsoft Dynamics AX V3 target.
On the Field Mapping tab for the Target transformation, the fields in the Target Fields appear in hierarchical format. The target fields are determined by the request message structure of the operation you select for the Target transformation.
Microsoft Dynamics AX V3 Target Operations 21
Each source object displays as a group in the Input Fields area. You can select fields in the Input Fields area to map the fields to the request. If the input fields include multiple input groups, map the groups to the corresponding nodes in the request. Be sure to map all of the fields that you require in the request.
The following image shows an example of mapped input fields from the source file with the Microsoft Dynamics AX V3 target in an operation create:
Rules and Guidelines for Microsoft Dynamics AX V3 Operations
Consider the following rules and guidelines for Microsoft Dynamics AX V3 source and target operations:
• Use only the following DateTime format: yyyy-mm-ddThh:mm:ssZ. For example, 2016-12-31T00:00:00Z, where Z represents the GMT/UTC timezone.
• When you fetch a large number of records from Microsoft Dynamics AX V3, perform the following steps:
- Set the JVM options for type DTM to increase the -Xms and -Xmx values in the system configuration details of the Secure Agent, and then restart the Secure Agent.
- Increase the cache size for the web service response in the advanced properties of the Microsoft Dynamics AX V3 source transformation to a size equal to or more than the memory required for a SOAP response.
• When you read or write data that contains i18n or Unicode characters, perform the following steps:
- For Windows, create an environmental variable INFA_CODEPAGENAME, and then set it to UTF-8. After you set the environmental variable, restart the Secure Agent.
- For Linux 64, set the environmental variable LC_ALL to en_US.utf8. To set the environmental variable, run the following command from Linux 64: setenv LC_ALL en_US.utf8. After you set the environmental variable, restart the Secure Agent.
• When you perform an update operation, you must specify the value of action field of the parent record as replace in the source document.
22 Chapter 3: Microsoft Dynamics AX V3 Operations
C H A P T E R 4
Mappings and Mapping Configuration Tasks with Microsoft Dynamics AX V3 Connector
This chapter includes the following topics:
• Mappings and Mapping Configuration Tasks with Microsoft Dynamics AX V3 Connector Overview, 23
• Microsoft Dynamics AX V3 Sources in Mappings, 23
• Microsoft Dynamics AX V3 Targets in Mappings, 24
• Microsoft Dynamics AX V3 Midstream Transformation in Mappings, 25
Mappings and Mapping Configuration Tasks with Microsoft Dynamics AX V3 Connector Overview
Use the Informatica Cloud Mapping Designer to create a mapping. When you create a mapping, you configure a source or target to represent a Microsoft Dynamics AX V3 object.
Validate and run the mapping to read data from Microsoft Dynamics AX 2012 sources and write data to a Microsoft Dynamics AX 2012 target.
Describe the flow of data from source and target along with the required transformations before the agent writes data to the target. Use the Mapping Configuration Task wizard to create a Mapping Configuration task and select the mapping that you want to use. The Mapping Configuration task processes data based on the data flow logic you define in the mapping.
Microsoft Dynamics AX V3 Sources in MappingsIn a mapping, you can configure a source transformation to represent a Microsoft Dynamics AX V3 source.
23
The following table describes the Microsoft Dynamics AX V3 source properties that you can configure in a Source transformation:
Property Description
Connection Name of the source connection.
Operation Source operation. Select the source operation.
Filter Not supported.
Request Message An XML request message for the operation that you want to perform in Microsoft Dynamics AX V3. Specify the data that you want to enter into the data flow.
Tracing Level Amount of detail that appears in the log for the source transformation. Use one of the following tracing levels:- Terse- Normal- Verbose Initialization- Verbose DataDefault is Normal.
Cache Size for Web Service Response (KB)
Memory available for the web service response. If the web service response contains many rows or columns, you can increase the cache size. Default is 1024 KB.
The following table describes the advanced properties that you can configure in a Source transformation:
Advanced Property
Description
Batch Size Number of records that the agent reads in a batch from the source when you read large amounts of data. Default value is 50.Note: You can select batch size when you perform read or find operation.
Company Name Specify the company name. You can enter multiple company names separated by semicolons. For example, ceu;ceed.
Language Localizes the data you read from Microsoft Dynamics AX 2012. Specify the language code.
Microsoft Dynamics AX V3 Targets in MappingsIn a mapping, you can configure a target transformation to represent a Microsoft Dynamics AX V3 target.
The following table describes the Microsoft Dynamics AX V3 target properties that you can configure in a Target transformation:
Property Description
Connection Name of the target connection.
Operation Target operation. Select the target operation.
24 Chapter 4: Mappings and Mapping Configuration Tasks with Microsoft Dynamics AX V3 Connector
Property Description
Cache Size for Web Service Request (KB)
Memory available for the web service request. If the web service request contains many rows or columns, you can increase the cache size. Default is 1024.
Transaction Commit Control
Control to commit or roll back transactions based on the set of rows that pass through the transformation. Use the transaction commit control if you have a large amount of data and you want to control how it is processed.
The following table describes the advanced properties that you can configure in a Target transformation:
Advanced Property Description
Batch Size Number of records that the agent writes in a batch to the target when you write large amounts of data. Default value is 50.
Company Name Specify the company name. You can enter multiple company names separated by semicolons. For example, ceu;ceed.
Language Localizes the data you write to Microsoft Dynamics AX 2012. Specify the language code.
Microsoft Dynamics AX V3 Midstream Transformation in Mappings
Before you configure a midstream transformation, you must create a business service on the Configure tab. You must select a Microsoft Dynamics AX V3 connection and an operation when you create a business service.
When you configure the midstream transformation, select the business service and the operation on the Web Service tab.
You can map the input fields from source file to elements in request structure on the Request Mapping tab.
You can view the response structure in the field mapping. When you map the elements from the response structure to the output fields, the Secure Agent creates the output groups, along with the primary and foreign keys for the field names.
Advanced Midstream PropertiesThe following table describes the advanced properties that you can configure for a midstream transformation:
Property Description
Cache Size for Web Service Request (KB)
Memory available for the web service request. If the request is more than 100 KB, you can increase the cache size. Default is 100 KB.
Cache Size for Web Service Response (KB)
Memory available for the web service response. If the web service response contains many rows or columns, you might want to increase the cache size. Default is 100 KB.
Microsoft Dynamics AX V3 Midstream Transformation in Mappings 25
Property Description
Allow Input Flush Not Applicable.
Transaction Commit Control Not Applicable.
The following table describes the advanced properties that you can configure on the Web Service tab:
Property Description
Business Service Name of the business service. Select the business service.
Operation Select read, readAll, find, findKeys, getKeys, getChangedKeys, or create.Note: You cannot perform delete or update operation.
Batch Size Not supported.
Company Name Specify the company name. You can enter multiple company names separated by semicolons. For example, ceu;ceed.
Language Localizes the data you write to Microsoft Dynamics AX 2012. Specify the language code.
26 Chapter 4: Mappings and Mapping Configuration Tasks with Microsoft Dynamics AX V3 Connector
C H A P T E R 5
Data Type ReferenceThis chapter includes the following topics:
• Data Type Reference Overview, 27
• Microsoft Dynamics AX 2012 and Transformation Data Types, 28
Data Type Reference OverviewInformatica Cloud uses the following data types in Microsoft Dynamics AX V3 mappings and Mapping Configuration tasks:
• Microsoft Dynamics AX 2012 native data types appear in the source and target transformations when you choose to edit metadata for the fields.
• Transformation data types. Set of data types that appear in the transformations. These are internal data types based on ANSI SQL-92 generic data types, which the Secure Agent uses to move data across platforms. They appear in all transformations in a mapping.
When the Secure Agent reads source data, it converts the native data types to the comparable transformation data types before transforming the data. When the Secure Agent writes to a target, it converts the transformation data types to the comparable native data types.
27
Microsoft Dynamics AX 2012 and Transformation Data Types
The following table lists the Microsoft Dynamics AX 2012 data types that Informatica Cloud supports and the corresponding transformation data types:
Microsoft Dynamics AX 2012 Data Type
Transformation Data Type
Description
Int Integer Integer values.Minimum value: -2,147,483,648Maximum value: 2,147,483,647Microsoft Dynamics AX 2012 might limit the range of values for some fields.
String String String values. Default is 255. You can increase the value up to 104857600 characters. Microsoft Dynamics AX 2012 might limit the range of values for some fields.
Decimal Decimal A decimal attribute. You can specify the level of precision up to 10 decimal places.Minimum value: -1,000,000,000Maximum value: 1,000,000,000Microsoft Dynamics AX 2012 might limit the range of values for some fields.
Long BigInt Big integer attribute.Minimum value: -922,337,203,685,477Maximum value: 922,337,203,685,477Microsoft Dynamics AX 2012 might limit the range of values for some fields.
Time Date/Time Date and time values. The Secure Agent considers only the time value.Minimum value: 1900/1/1 00:00:00Maximum value: 9999/12/30 23:59:59
DateTime Date/Time Date and time values. The Secure Agent considers only the date value.Minimum value: 1900/1/1 00:00:00Maximum value: 9999/12/30 23:59:59
Date Date/Time Date and time values.Minimum value: 1900/1/1 00:00:00Maximum value: 9999/12/30 23:59:59
When you use Microsoft Dynamics AX V3 Connector, you can not read or write data of complex data type. You cannot use hierarchical data type that is self-referencing. You cannot use complex data type that is self-referencing inside another complex data type.
In the following example, the complex type AxdType_Container has a self-reference.
<xs:complexType name="AxdType_Container"><xs:sequence><xs:element name="container" type="tns:AxdType_Container"/></xs:choice></xs:sequence></xs:complexType>
28 Chapter 5: Data Type Reference
In the following example, complex type AxdExtType_KeyData has a reference of the complex type AxdType_Container that has a self-reference.
<xs:complexType name="AxdExtType_KeyData"><xs:annotation><xs:documentation xml:lang="EN-US">Key fields:Packed container of key fields.</xs:documentation></xs:annotation><xs:sequence><xs:choice minOccurs="0" maxOccurs="unbounded"><xs:element name="element" type="tns:AxdType_ContainerElement"/><xs:element name="container" type="tns:AxdType_Container"/></xs:choice></xs:sequence></xs:complexType><xs:complexType name="AxdType_Container"><xs:sequence><xs:choice minOccurs="0" maxOccurs="unbounded"><xs:element name="element" type="tns:AxdType_ContainerElement"/><xs:element name="container" type="tns:AxdType_Container"/></xs:choice></xs:sequence></xs:complexType>
Microsoft Dynamics AX 2012 and Transformation Data Types 29
Index
Aadministration
configure troubleshooting options for integration ports 9exchange documents 9HTTP adapter 9install web services on IIS 9
application object server 9
Cconnection properties
company name 11language 11WSDL URI 11
connections Microsoft Dynamics AX V3 11
connector administration 9operations 13supported tasks 8
Ddata type reference
overview 27
Ffield mapping
creating packed fields 18
Iintegration ports 9
Mmapping configuration tasks
overview 23mappings
overview 23request message 23
mappings (continued)source properties 23target properties 24
Microsoft Dynamics AX data types 28Microsoft Dynamics AX V3
connection properties 11connections 11
Microsoft Dynamics AX V3 connections overview 11properties 11
Microsoft Dynamics AX V3 Connector administration 9example 8operations 13overview 8
source operation overview 14
source operations 13target operations 13
Ooperations
rules and guidelines 22
Rrequest message
parameterize input values 16request message editor
configure a request 14
Ssource operations 13source transformation
field mapping 18
Ttarget operations 13target transformation
field mapping 21transformation data types 28
30
