Sample Maps: Microsoft Dynamics NAV/Financials. Version 1.0

Transcription

1 Sample Maps: Microsoft Dynamics NAV/Financials 9/24/2018

2 Important Notice No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, photocopying, recording, or otherwise, without prior written consent of TIBCO Software Inc.. No patent liability is assumed with respect to the use of the information contained herein. While every precaution has been taken in the preparation of this book, TIBCO Software Inc. assumes no responsibility for errors or omissions. This publication and features described herein are subject to change without notice. TIBCO Software Inc. makes no representations or warranties, either expressed or implied, by or with respect to anything in this document, and shall not be liable for any implied warranties of merchantability or fitness for a particular purpose or for any indirect, special or consequential damages. Disclaimer The names of companies, products, people, and/or data used in window illustrations and sample output are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Trademarks TIBCO Scribe Online is a trademark of TIBCO Software Inc.. All other products or services mentioned in this document are identified by the trademarks or service marks of their respective companies or organizations. TIBCO Software Inc. disclaims any responsibility for specifying which marks are owned by which companies or organizations. Publishing Information Copyright 2018 TIBCO Software Inc. All Rights Reserved.

3 Contents Microsoft Dynamics NAV And 365 Business Central Sample Maps 1 Two Implementation Options 2 Preventing Bounce Backs 2 Domain Value Mapping 2 Method 1 3 Method 2 Variation 1 4 Method 2 Variation 2 4 Method 3 5 Related Entities 5 Multi-Key Updates 5 Working With ETags 6 TIBCO Scribe Online Agent Information 7 Requirements 7 TIBCO Scribe Online Requirements 7 Dynamics NAV/Financials Requirements 8 Dynamics CRM Requirements 8 Text File Requirements 9 Source Text Connection Settings 18 Location Tab 18 Entities Tab 19 Fields Tab 20 Target Text Connection Settings 21 Locations Tab 21 Entities Tab 22 Fields Tab 23 Preparing The Dynamics CRM Sample Maps 24 Sample Maps: Microsoft Dynamics NAV/Financials - i -

4 Extract The Files From The Zip File 24 Add An Ignore User 26 Preparing The Text File Sample Maps 27 Dynamics CRM And Dynamics NAV/Financials Maps 28 CRM Account -> NAV Customer Create Map 28 Payment Terms/Domain Value Mapping 28 Address Formats 29 Address CODE 29 Working with ETags 29 CRM Account -> NAV Customer Update Merge Map 30 Working with ETags 30 CRM Account Address -> NAV Customer Ship To Address Create Or Update Merge Map 31 Create 31 Update 31 Working With ETags 31 NAV Customer -> CRM Account Create Map 32 Payment Terms/Domain Value Mapping 32 Related Entities 33 Address Format 33 Working With ETags 33 NAV Customer -> CRM Account Update Map 34 NAV Ship To Address -> CRM Customer Address Create Or Update Map 35 Text Files And Dynamics NAV/Financials Maps 36 Customers/Addresses Text -> NAV Customers Create Map 36 Payment Terms/Domain Value Mapping 36 Address Formats 37 Address CODE 37 Working With ETags 37 Sample Maps: Microsoft Dynamics NAV/Financials - ii -

5 Customers 37 Addresses 38 Customers Text -> NAV Customer Update Merge Map 39 Working With ETags 39 Addresses Text -> NAV Customer Ship To Address Update Merge Map 40 Working with ETags 40 NAV Customer -> Customers Text Create Map 41 Payment Terms/Domain Value Mapping Map 41 Address Format 42 ETags And Key Sharing 42 Additional Notes 43 Running Maps Multiple Times 43 Sample Maps: Microsoft Dynamics NAV/Financials - iii -

6 Microsoft Dynamics NAV And 365 Business Central Sample Maps Microsoft Dynamics NAV And 365 Business Central Sample Maps Sample Maps provide a base set of Maps and configuration files you can leverage when integrating data between applications. Each set of Sample Maps requires customization to integrate your data properly. Therefore, it is important that you read and understand the entire document before attempting to use the contents of the Sample Maps. TIBCO Sample Maps are meant to be used as a starting point for your own projects, and should not be considered plug and play. Sample Maps are available as is, with no guarantee or commitment of support for the associated Maps and configuration files. This document introduces how to work with TIBCO Scribe Online and the TIBCO Scribe Online Connector for Dynamics NAV/Financials, providing general information about TIBCO Scribe Online options and features, as well as an overview of the Maps in the DynamicsNAV-SampleMaps_v1.0.zip file. The sample Maps outline best practices and strategies for dealing with common integration considerations: Preventing bounce backs Determining approaches for data transformation Working with related entities Performing multi-key updates Working with ETags Sample Maps: Microsoft Dynamics NAV/Financials - 1 -

7 Microsoft Dynamics NAV And 365 Business Central Sample Maps Two Implementation Options The DynamicsNAV-SampleMaps_v1.0.zip package contains sample Maps that use the sample Cronus International Ltd. company on a Dynamics NAV/Financials 2015, 2016, or 2017 Azure or on-premise deployment. The Maps illustrate a bidirectional integration of Customers/Accounts and their related addresses: Implement Samples between Dynamics NAV/Financials and Dynamics CRM This set of Maps uses Dynamics CRM. If you do not have Dynamics CRM and want to review these examples, you can use a Dynamics CRM Online Trial Organization. This option requires you to apply customizations either manually, or by importing one of the provided Dynamics CRM customization packages. Implement Samples between Dynamics NAV/Financials and Text Files This set of Maps uses the text files provided. This option allows you to configure the Maps and review the provided examples without any external requirements. Because this option uses text files instead of a database, more explanation is provided in this document for some integration concepts. For more information, see TIBCO Scribe Online Connector For Microsoft Dynamics NAV And 365 Business Central and TIBCO Scribe Online Connector For Microsoft Dynamics CRM in the TIBCO Scribe Online Help. Preventing Bounce Backs In a bidirectional integration, to prevent data bouncing back and forth between the two applications, you typically use a lastmodifiedby field. While Dynamics NAV/Financials does not provide this information, Dynamics CRM does. To see examples of preventing bounce back, implement the samples using Dynamics CRM. Domain Value Mapping Most integrations require domain value mapping between the source and target. There are three main methods that can be used for domain value mapping using TIBCO Scribe Online that vary in their row processing performance, steps to maintain the value mapping, and requirements for implementing for a bidirectional integration. Sample Maps: Microsoft Dynamics NAV/Financials - 2 -

8 Microsoft Dynamics NAV And 365 Business Central Sample Maps Method 1 One method is to hard code the value Map in a linked field formula in Integration Maps. At run time, this method is fast because the value mapping is done during processing, with no external lookups. Adding or modifying value mappings requires modifying any Map that uses the logic. If you are using this method for a bidirectional integration, you must set up the link formulas in both directions. This method is best suited for: One-time, large volume data loads where incremental performance gains can provide benefit over a large volume of rows when there is no need to modify value mappings. An example of this is the initial data synchronization during a migration to a new system. Ongoing migrations where the value mappings is not going to change. Sample Maps: Microsoft Dynamics NAV/Financials - 3 -

9 Microsoft Dynamics NAV And 365 Business Central Sample Maps Method 2 Variation 1 A second method is to keep the domain values between the source and target system in sync. There are various ways to make this work, but generally requires a business rule that when a value is added or modified in the target system, the source system must also be updated. This rule could be as simple as: Whenever a territory is added to the target system, a territory with the same name must be added to the source system. This usually requires the Map to be designed to do a lookup on the target system to return an ID. For example, look up a territory in the target system where the name matches a given territory s name in the source system, and return the ID of the target system territory to use in the Map later. For example, the territory ID returned by the Lookup Block could be used in a later Create Block in the Map to assign the territory to a new customer being created in the target. With this method, the performance per row is a little slower than the first method, but there is nothing to maintain in the Map itself. If you are not doing large volume, the performance difference is minimal. This method is set up for bidirectional integration by configuring the same lookup logic in both directions. This method is best suited for situations where you want changes to the domain values to be visible to the business process. Examples of this are seen in Maps that have Dynamics NAV/Financials as the source. Method 2 Variation 2 Another variation on this method is to have a business rule that says: Whenever a territory is added to the target system, its ID needs to be added to the corresponding territory in the source system. With this variation, you can likely avoid the Lookup into the target system and achieve performance similar to Method 1. Maintenance of mappings is likely done by a more technical resource than the first variation, which can be done by a business user. Setting this variation up for bidirectional processing requires either storing cross-referenced system IDs in both systems, or by configuring a Lookup in the other direction, similar to Variation 1. This method is best suited for situations where ongoing, high-volume performance is the goal and value Maps are not expected to change frequently, like recurring large list loads. Examples of this are seen in Maps that have Dynamics CRM as the source. Sample Maps: Microsoft Dynamics NAV/Financials - 4 -

10 Microsoft Dynamics NAV And 365 Business Central Sample Maps Method 3 The final method is to use external lookup tables or files. This method has similar performance to variation 1 of Method 2 due to the Lookup required to get the target system key. The main maintenance advantage is that it is easy to look at the entire set of value Maps in a single location. Maintenance is likely done by an integration administrator, but all of the information can be formatted and centrally located. This method, like Variation 1 of Method 2, is set up for bidirectional integration by configuring the same lookup logic in both directions. This method is best suited for creating portable Solutions that are easily modified on site. Examples of this are seen in Maps that have Dynamics NAV/Financials as the target. Related Entities If you are familiar with TIBCO Scribe Online, you have probably worked with related entities using Relationships. The TIBCO platform uses relationships to retrieve an entity and its related entities in a single transaction. The Dynamics NAV/Financials implementation does not support retrieving related entities in a single call. The sample Maps that have Dynamics NAV/Financials as the source provide examples of using a Fetch Block to retrieve related child records in a separate call. Multi-Key Updates Multi-key updates require: PK The key for the child entity you are updating. FK The key for the related parent. For example, the sample Maps that update the Ship to Address in Dynamics NAV/Financials require both the Customer_No for the customer and the CODE for the address. Sample Maps: Microsoft Dynamics NAV/Financials - 5 -

11 Microsoft Dynamics NAV And 365 Business Central Sample Maps Working With ETags The Dynamics NAV/Financials implementation of OData uses ETags for optimistic concurrency control. This is fully supported in the TIBCO Scribe Online Connector for Dynamics NAV/Financials using two fields, ETag and ETagConcurrencyBehavior. For more information, see TIBCO Scribe Online Connector For Microsoft Dynamics NAV And 365 Business Central. Both sets of sample Maps use the ETag field linked from the source, which supports Always Overwrite, Overwrite If No Match, and Overwrite If Match. Because the behavior is not linked, the default behavior is Always Overwrite. To use Always Overwrite, you can use any value in the ETag field, even if it is not a valid ETag. When working with ETags and Update Blocks, if the match criteria in your Update Block uses the primary key field in Dynamics NAV/Financials, you must provide a value for the ETag field. Otherwise, the following error occurs: Description: Could not validate the client concurrency token required by the service. Please provide a valid token in the client request. If you use a field other than the primary key for your match criteria, no ETag is required. By default, the current ETag is returned from Dynamics NAV/Financials and compared to itself, which results in the ETags always matching. Sample Maps: Microsoft Dynamics NAV/Financials - 6 -

12 Microsoft Dynamics NAV And 365 Business Central Sample Maps TIBCO Scribe Online Agent Information TIBCO provides the option of using either an On-Premise Agent or a Cloud Agent. Some features in the samples, such as using the CSVLOOKUPVALUE function, require an On- Premise Agent. Using text files as a source or target with a Cloud Agent has some specific requirements. For more information, see Connecting To Text File As A Source or Connecting To Text File As A Target. Requirements In addition to the Sample package, your site needs: A trial or paid subscription to TIBCO Scribe Online Integration Services (IS) TIBCO Scribe Online Connector for Dynamics NAV/Financials TIBCO Scribe Online Connector for Dynamics CRM (Optional) Access to a Dynamics NAV/Financials Organization Access to a Dynamics CRM Organization (Optional) TIBCO Scribe Online Requirements You must download the TIBCO Scribe Online Connector for Dynamics NAV/Financials from the TIBCO Scribe Online Marketplace. Optionally, you can also download the TIBCO Scribe Online Connector for Dynamics CRM. The TIBCO Scribe Online Connectors for using text files as source and target are included in your TIBCO Scribe Online Organization. For more information about downloading Connectors from the TIBCO Scribe Online Marketplace, see Marketplace Connections. Sample Maps: Microsoft Dynamics NAV/Financials - 7 -

13 Microsoft Dynamics NAV And 365 Business Central Sample Maps Dynamics NAV/Financials Requirements Your Dynamics NAV/Financials Organization must have OData web services enabled with the objects in the table below published. You also need a user to connect as that has the appropriate permissions to query, create, and update these objects. This user is the one you use in your Dynamics NAV/Financials Connection in TIBCO Scribe Online. For information on connecting to Dynamics NAV/Financials, see TIBCO Scribe Online Connector For Microsoft Dynamics NAV And 365 Business Central. Object Type Object ID Object Name Service Name Page 21 Customer Card Customer Page 4 Payment Terms PaymentTerms Page 300 Ship-to Address ShipToAddress The Service Name appears in the Entity drop-down in TIBCO Scribe Online. The sample Maps use the names as they appear in the table. If you choose a different Service Name, you must modify the Maps accordingly. Dynamics CRM Requirements If you plan to use Dynamics CRM, the following settings are required. Users Your Dynamics CRM Organization must include users that are configured with appropriate permissions and access: Query, create and update the entities in the sample Maps This user is the one you use as the integration, or ignore user, in your Dynamics CRM Connection in TIBCO Scribe Online. To prevent bounce backs, use a different user when logging into the Dynamics CRM application. For more information, see Ignore Users. Access to import custom Solutions If you plan to import the included Dynamics CRM customizations, you need a user with permissions to perform the import. Otherwise, you need a user with permissions to manually create the customizations. For more information about connecting to the TIBCO Scribe Online Connector for Dynamics CRM,see TIBCO Scribe Online Connector For Microsoft Dynamics CRM. Sample Maps: Microsoft Dynamics NAV/Financials - 8 -

14 Microsoft Dynamics NAV And 365 Business Central Sample Maps Customizations The sample Maps require specific custom fields in your Dynamics CRM Organization. The DynamicsNAV-SampleMaps_v1.0.zip file includes two versions of the custom Solution: ScribeSolutionforNAVSamples_v7.0_1_0_0_managed.zip Use with Dynamics CRM Online 2015 or On-Premise ScribeSolutionforNAVSamples_v7.1_1_0_0_managed.zip Use with Dynamics CRM Online 2015 SP1 and 2016 or On-Premise 2015 SP1 and 2016 After you import or create the custom fields, you must refresh the metadata for your Microsoft Dynamics 365 Connection in TIBCO Scribe Online. Text File Requirements If you are using the Text files, there are several points to consider. On-Premise Agents If you are using an On-Premise Agent, copy the text files from the \Samples folder in the DynamicsNAV-SampleMaps_v1.0.zip file to the \Program Files (x86)\scribe Software\Scribe Online Agent\DataExchange folder on your TIBCO Scribe Online Agent system. Configure the source and target Connections for these files using the settings shown in the sections below. All files are (pipe) delimited with no text qualifier. For more information on setting up source and target text Connections, and using source and target Connections with a Cloud Agent, see the Connecting To Text File As A Source and Connecting To Text File As A Target topics. File Names And Connection Types File Name Connection Type(s) Customers_Initial.txt Source Addresses_Initial.txt Source Customers_ETagUpdate1.txt Source/Target Addresses_ETagUpdate1.txt Source/Target Sample Maps: Microsoft Dynamics NAV/Financials - 9 -

15 Microsoft Dynamics NAV And 365 Business Central Sample Maps File Name Addresses_ETagUpdate2.txt Customers_ETagUpdate2.txt Customers_FinalUpdate.txt Connection Type(s) Target Target Target File Layouts The files contain the following text fields: Sample Maps: Microsoft Dynamics NAV/Financials

16 Microsoft Dynamics NAV And 365 Business Central Sample Maps Customers_Initial.txt Field Width ID 10 Name 100 Address1 100 Address2 100 City 100 State 2 PostalCode 15 Country 2 Phone 50 Fax 50 PaymentTerms 50 Addresses_Initial.txt Field Width ID 10 Customer_ID 10 Name 100 Address1 100 Address2 100 City 100 Sample Maps: Microsoft Dynamics NAV/Financials

17 Microsoft Dynamics NAV And 365 Business Central Sample Maps Field Width State 2 PostalCode 15 Country 2 Sample Maps: Microsoft Dynamics NAV/Financials

18 Microsoft Dynamics NAV And 365 Business Central Sample Maps Customers_ETagUpdate1.txt Field Width ID 10 Name 100 Address1 100 Address2 100 City 100 State 2 PostalCode 15 Country 2 Phone 50 Fax 50 PaymentTerms 50 Scribe_ExternalId 100 Scribe_Etag 100 Addresses_ETagUpdate1.txt Field Width ID 10 Customer_ID 10 Name 100 Address1 100 Sample Maps: Microsoft Dynamics NAV/Financials

19 Microsoft Dynamics NAV And 365 Business Central Sample Maps Field Width Address2 100 City 100 State 2 PostalCode 15 Country 2 Scribe_ExternalId 100 Scribe_Etag 100 Sample Maps: Microsoft Dynamics NAV/Financials

20 Microsoft Dynamics NAV And 365 Business Central Sample Maps Customers_ETagUpdate2.txt Field Width ID 10 Name 100 Address1 100 Address2 100 City 100 State 2 PostalCode 15 Country 2 Phone 50 Fax 50 PaymentTerms 50 Scribe_ExternalId 100 Scribe_Etag 100 Addresses_ETagUpdate2.txt Field Width ID 10 Customer_ID 10 Name 100 Address1 100 Sample Maps: Microsoft Dynamics NAV/Financials

21 Microsoft Dynamics NAV And 365 Business Central Sample Maps Field Width Address2 100 City 100 State 2 PostalCode 15 Country 2 Scribe_ExternalId 100 Scribe_Etag 100 Sample Maps: Microsoft Dynamics NAV/Financials

22 Microsoft Dynamics NAV And 365 Business Central Sample Maps Customers_FinalUpdate.txt Field Width ID 10 Name 100 Address1 100 Address2 100 City 100 State 2 PostalCode 15 Country 2 Phone 50 Fax 50 PaymentTerms 50 Scribe_ExternalId 100 Scribe_Etag 100 Sample Maps: Microsoft Dynamics NAV/Financials

23 Microsoft Dynamics NAV And 365 Business Central Sample Maps Source Text Connection Settings Settings for the source text Connections are shown in the following images. Location Tab Use the Location tab to specify the physical location of your text file and the access properties for that location. Text Source Location Tab Sample Maps: Microsoft Dynamics NAV/Financials

24 Microsoft Dynamics NAV And 365 Business Central Sample Maps Entities Tab Use the Entities tab to do the following: Manually enter the names of the entities for this Connection. These names represent the individual text files or set of related files that contain your data or receive data from another datastore. The names on the Entities tab do not need to match the text file name. Associate a text file or files with the entity selected on the Entities tab. Select post-processing options for the associated text file. Define the format of the source entity file. If the Fail Record On Metadata Mismatch option is enabled, any record that does not match the defined parameters is not processed. You must add the entities manually. Text Source Entities Tab Sample Maps: Microsoft Dynamics NAV/Financials

25 Microsoft Dynamics NAV And 365 Business Central Sample Maps Fields Tab The Fields tab displays the field names for the Entity selected in the Entities column. The first time you access the fields tab, select the Generate fields schema from your data link in the right pane to display the associated fields. From the Fields tab, you can: Make changes to the Field name, Data type, and Width of individual fields in your text file. Set the width of each field using the tables in the File Layouts section of this document. Revert all of your fields to the original source names and formats using the Refresh Schema option on the Gear menu for the selected Entity. Text Source Fields Tab Sample Maps: Microsoft Dynamics NAV/Financials

26 Microsoft Dynamics NAV And 365 Business Central Sample Maps Target Text Connection Settings Settings for the target text Connections are shown in the following images. Locations Tab Use the Location tab to specify the physical location of your text file and the access properties for that location. Text Target Locations Tab Sample Maps: Microsoft Dynamics NAV/Financials

27 Microsoft Dynamics NAV And 365 Business Central Sample Maps Entities Tab Use the Entities tab to do the following: Manually enter the names of the entities for this Connection. These names represent the individual text files or set of related files that contain your data or receive data from another datastore. The names on the Entities tab do not need to match the text file name. Associate a text file or files with the entity selected in the Entities column. Select post-processing options for the associated text file. Define the format of the target entity file. Select an Entity to specify properties displayed on the right. Text Target Entities Tab Sample Maps: Microsoft Dynamics NAV/Financials

28 Microsoft Dynamics NAV And 365 Business Central Sample Maps Fields Tab The Fields tab displays the field names for the Entity selected in the Entities column. The first time you access the fields tab, select the Generate fields schema from your data link in the right pane to display the associated fields. From the Fields tab, you can: Make changes to the Field name, Data type, and Width of individual fields in your text file. Set the width of each field using the tables in the File Layouts section of this document. Revert all of your fields to the original source names and formats. Text Target Fields Tab Sample Maps: Microsoft Dynamics NAV/Financials

29 Preparing The Dynamics CRM Sample Maps Preparing The Dynamics CRM Sample Maps This section explains how to extract the files from the.zip file and configure the Dynamics CRM sample Maps for integrating data between Dynamics NAV/Financials and Dynamics CRM. You must create the Dynamics NAV And 365 Business Central Connection and the Dynamics CRM Connection in TIBCO Scribe Online and the necessary custom fields in your Dynamics CRM Organization. For more information, see Requirements. For information on TIBCO Scribe Online tasks, such as configuring Connections, and using TIBCO Scribe Online, see the TIBCO Scribe Online Help Center. Extract The Files From The Zip File 1. Download the DynamicsNAV-SampleMaps_v1.0.zip file. 2. Unzip the file and extract the files to a folder accessible by TIBCO Scribe Online and Dynamics CRM. Do not unzip the Scribe CRM Managed Solution zip files contained in this file. The \Samples folder includes two files used in the Maps where Dynamics NAV/Financials is the source. These files are used in the domain value mappings for payment terms: Payment Terms-LookupTable.csv Use the contents of this file to create a Lookup Table in TIBCO Scribe Online when the LOOKUPTABLEVALUE2 option is selected for the Payment Terms mapping in Maps where Dynamics NAV/Financials is the source. Add the Lookup Tables using the Lookup Tables page in TIBCO Scribe Online. See Lookup Tables in the TIBCO Scribe Online Help. The name of the Lookup Table you create must be Payment Terms to match the information configured in the Sample Maps. Payment Terms.csv Use this file when the CSVLOOKUPVALUE option is selected for the Payment Terms mapping in Maps where Dynamics NAV/Financials is the source. Save this file to the..\program Files (x86)\scribe Software\Scribe Online Agent\DataExchange folder on your Agent system. Sample Maps: Microsoft Dynamics NAV/Financials

30 Preparing The Dynamics CRM Sample Maps 3. Do one of the following to include the custom fields in your Dynamics CRM Organization: Import Dynamics CRM Customizations Importing the customizations automatically includes the custom fields in your Dynamics CRM Organization. o o Log in to your Dynamics CRM Organization as a user with access to import custom Solutions. Import the appropriate version of the provided custom Solutions. For more information about the version to import, see the Customizations section. Manually Implement Dynamics CRM Customizations The Maps use a Publisher with a prefix of scribe. You can create a new publisher and set the prefix as shown below. If you are using an existing Dynamics CRM Organization and want to use an existing Publisher when creating the custom fields, update the links in the Maps from the fields with the scribe_ value to the fields with your publisher's prefix. Set The Custom Field Name Prefix Create the following custom fields: Entity Display Name Name Data Type/Length Account ETag etag Single Line of Text/100 Account ScribeExternalId scribeexternalid Single Line of Text/100 Address ETag etag Single Line of Text/100 Address ScribeExternalId scribeexternalid Single Line of Text/100 Sample Maps: Microsoft Dynamics NAV/Financials

31 Preparing The Dynamics CRM Sample Maps After you import or create the custom fields, you must refresh the metadata for your Microsoft Dynamics 365 Connection in TIBCO Scribe Online. 4. Create a TIBCO Scribe Online Integration Solution. See Adding Or Editing An Integration Solution. 5. In the Maps section of the Solution, select Import from the Menu. See Exporting And Importing Maps. 6. Browse to and import the CRM-NAV Accounts and Addresses.xml file. The imported Maps show as Incomplete. 7. Open each Map and configure the Connections. See Defining An Integration Map. The Dynamics CRM set of Maps contains examples of preventing bounce backs from occurring by using an integration user, or ignore user, which is the Run As user configured in your TIBCO Scribe Online Dynamics CRM Connection. This is the last modified by user for all records either created or updated by the integration process. When you retrieve data from Dynamics CRM to send to Dynamics NAV/Financials, records created or updated by this user are ignored. For more information on implementing the Integration User in a realworld scenario see, the Users section. Add An Ignore User For each of the following Maps, you must modify the Filter tab on the Query Block: CRM Account -> NAV Customer Create CRM Account -> NAV Customer Update Merge CRM Account Address -> NAV Customer Ship To Address Create or Update Merge 1. In TIBCO Scribe Online, open one of the Map files. 2. Open the Query Block. 3. Select the Filter tab. 4. Select the filter with the modifiedbyname field. 5. Change Value to the user s full name for the integration user, specified in the selected Dynamics CRM Connection. Sample Maps: Microsoft Dynamics NAV/Financials

32 Preparing The Text File Sample Maps 6. Repeat steps 4 through 7 in the extracting procedure, above, to import the NAV-CRM Accounts and Addresses.xml file. Preparing The Text File Sample Maps This section includes steps to extract the files from the.zip file and configure the Maps for integrating between Dynamics NAV/Financials and the sample text files. For information on TIBCO Scribe Online tasks, such as configuring source and target Connections, and using TIBCO Scribe Online, see the TIBCO Scribe Online Help Center. Extract The Files From The Zip File 1. If you haven't already done so, download the DynamicsNAV-SampleMaps_v1.0.zip file. You can download this file from the TIBCO Scribe Online Sample Mapss page. 2. Unzip the file and extract the files to a folder accessible by TIBCO Scribe Online. The \Samples folder includes two files used in the Maps where Dynamics NAV/Financials is the source. These files are required in the examples for managing the domain value mappings for payment terms: Payment Terms-LookupTable.csv Use the contents of this file to create a Lookup table in TIBCO Scribe Online. Add the Lookup Table using the Lookup Tables page in TIBCO Scribe Online. See Lookup Tables in the TIBCO Scribe Online Help. The name of the Lookup Table you create must be Payment Terms to match the information configured in the Sample Maps. Payment Terms.csv Save this file to the..\program Files (x86)\scribe Software\Scribe Online Agent\DataExchange folder on your TIBCO Scribe Online Agent system. 3. Create a TIBCO Scribe Online Integration Solution. See Adding Or Editing An Integration Solution. 4. In the Maps section of the Solution, select Import from the Menu. See Exporting And Importing Maps. 5. Browse to and import the NAV Customers -Text File.xml file. The imported Maps show as Incomplete. 6. Open each Map and configure the Connections. See Defining An Integration Map. 7. Repeat steps 4 through 6 and import the Text File-NAV Customers and Addresses.xml file. Sample Maps: Microsoft Dynamics NAV/Financials

33 Dynamics CRM And Dynamics NAV/Financials Maps Dynamics CRM And Dynamics NAV/Financials Maps CRM Account -> NAV Customer Create Creates a customer in Dynamics NAV/Financials from an Account in Dynamics CRM. Each related address in Dynamics CRM is created as a Ship To Address in Dynamics NAV/Financials. CRM Account -> NAV Customer Update Merge Updates a customer in Dynamics NAV/Financials from an Account in Dynamics CRM. CRM Account Address -> NAV Customer Ship To Address Create or Update Merge Creates or updates a customer Ship to Address in Dynamics NAV/Financials from an Account address in Dynamics CRM. NAV Customer -> CRM Account Create Creates an account in Dynamics CRM from a customer in Dynamics NAV/Financials. Each related customer Ship To Address in Dynamics NAV/Financials is created as a related account address in Dynamics CRM. NAV Customer -> CRM Account Update Updates an account in Dynamics CRM from a customer in Dynamics NAV/Financials. NAV Ship To Address -> CRM Customer Address Create or Update Creates or updates an address associated with an account in Dynamics CRM from a customer Ship to Address in Dynamics NAV/Financials. CRM Account -> NAV Customer Create Map This Map creates customers with a main address and multiple Ship to Addresses in Dynamics NAV/Financials. It is configured to retrieve all active customers created since the last run date/time created or updated by users other than the integration user. The main address, or address number 1, from the Dynamics CRM account is used as the main address for the customer in Dynamics NAV/Financials. Additional addresses, address number 2 and greater, are created as Ship to Addresses associated with the customer in Dynamics NAV/Financials. Payment Terms/Domain Value Mapping This Map populates the payment terms in Dynamics NAV/Financials from payment terms in Dynamics CRM. Although the payment terms are not required, they are included to demonstrate different approaches for domain value mapping. To include payment terms for the customer in Dynamics NAV/Financials, you must provide the Payment Terms Code. The Payment Terms from Dynamics NAV/Financials need to be set up in Dynamics CRM, ensuring the full name, such as Net 21 days, is the same in both. Sample Maps: Microsoft Dynamics NAV/Financials

34 Dynamics CRM And Dynamics NAV/Financials Maps The Map contains a Lookup Block that uses the payment terms description from Dynamics CRM to look up the corresponding Payment Terms Code in Dynamics NAV/Financials. The Payment Terms Code value returned in the Lookup Block is linked to the Payment Terms Code in the Create NAV Customer Block. Address Formats There are significant differences in how address data is formatted in Dynamics NAV/Financials and Dynamics CRM. The sample Maps provide examples of transforming data for US address formats between the two applications: The two-character ISO code is used for both the country and state. The Dynamics NAV/Financials configuration also uses the two-character ISO code for the country region field. The postal code only contains 5-character postal codes. The expected Post_Code format is: Country-State PostCode For example, US-FL While this is the expected format, Dynamics NAV/Financials allows any value to be written to the Post_Code field in the main customer address and the Ship to Addresses. Address CODE Dynamics NAV/Financials requires a unique CODE when creating a Ship to Address. The CODE is what you see in the interface when you select an address. Microsoft suggests defining a value that is representative of the address. The Maps populate this field with the first 10 alphanumeric characters of address line 1 and ignore any address record from Dynamics CRM where address line 1 is not populated. Working with ETags When a customer or address is created in Dynamics NAV/Financials, the ETags are not automatically included in the results of the create in TIBCO Scribe Online. When a customer or address is updated in Dynamics NAV/Financials, the ETag is required. The sample Maps use a Lookup Block to retrieve the ETags. The Lookup Blocks perform the lookup using the key field(s) from the Create Block and return the matching ETag. This ETag is stored in the scribe_etag field of the account and/or address in Dynamics CRM for future processing. In addition to the ETag, the Dynamics NAV/Financials Customer.No field is stored in the scribe_scribeexternalid field in Dynamics CRM. Sample Maps: Microsoft Dynamics NAV/Financials

35 Dynamics CRM And Dynamics NAV/Financials Maps CRM Account -> NAV Customer Update Merge Map This Map updates Customers in Dynamics NAV/Financials from Accounts in Dynamics CRM, including the basic customer information and the main address. This Map retrieves all active Dynamics CRM Accounts updated by users other than the integration user since the last run date time. Additional addresses are handled in the CRM Account Address -> NAV Customer Ship To Address Create or Update Merge Map. The Map uses the OData Update Merge operation, only updating linked fields. Payment terms and the address format are handled in the same manner as in the CRM Account -> NAV Customer Create Map. Working with ETags In this Map: The match criteria in the UpdateMerge NAV Customer Block matches records where the Dynamics NAV/Financials Customer.No equals the Dynamics CRM Account.scribe_ ScribeExternalId in the Fields tab. The scribe_etag field from Dynamics CRM is linked to the Customer.ETag field in Dynamics NAV/Financials. The ETagConcurencyBehavior field is left blank, causing the default behavior of Always Overwrite to take effect. As in the Create Map, after the update completes successfully, a Lookup Block retrieves the updated ETag, which is then used to update the corresponding account.scribe_etag in Dynamics CRM with the updated value. Sample Maps: Microsoft Dynamics NAV/Financials

36 Dynamics CRM And Dynamics NAV/Financials Maps CRM Account Address -> NAV Customer Ship To Address Create Or Update Merge Map This Map updates customer Ship to Address information in Dynamics NAV/Financials from addresses in Dynamics CRM. It retrieves all addresses modified by users other than the integration user since the last run date/time, where the address number is 2 or greater and line1 is not NULL. It also retrieves the related parent account information. The address format and address CODE work as described in the CRM Account -> NAV Customer Create Map section. Create A check is performed to determine if the address already exists in Dynamics NAV/Financials, based on whether or not the source Dynamics CRM address contains a value in the scribe_ ScribeExternalId field. If the field is empty, the address is created in Dynamics NAV/Financials. The Map presumes the parent account has already been synchronized and uses the scribe_scribeexternalid of the related Dynamics CRM Account as the parent Customer.No when creating the address. Update If the scribe_scribeexternalid of the Dynamics CRM source address contains a value, the address is updated in Dynamics NAV/Financials using the OData UpdateMerge operation, only updating linked fields. The match criteria is configured to match when the following are true: The Dynamics NAV/Financials Ship to Address Customer_No equals the scribe_ ScribeExternalId of the related source Dynamics CRM parent account. The mapped CODE equals the scribe_scribeexternalid of the source Dynamics CRM address. This is an example of a multi-key update. Working With ETags As in the prior Maps, after the update completes successfully, a Lookup Block retrieves the updated ETag, which is then used to update the corresponding customeraddress.scribe_ ETag in Dynamics CRM with the updated value. Sample Maps: Microsoft Dynamics NAV/Financials

37 Dynamics CRM And Dynamics NAV/Financials Maps NAV Customer -> CRM Account Create Map This Map creates Dynamics CRM accounts with a main address and any additional addresses. It retrieves all customers with a Post_Code like %US% that were modified since the last run date. In this Map: Dynamics NAV/Financials does not provide a last modified by user. All records, including those last updated by the integration, are retrieved. Dynamics NAV/Financials only provides a modified date, not a create date. All records created or updated since the last modified date are retrieved and processed. The last modified field is a date there is no time component. This must be taken into consideration when you create a Solution schedule in a real-world use case. The Map presumes the customer and addresses do not already exist in Dynamics CRM. You can add logic using If/Else and Lookup Blocks to check for an account/address in Dynamics CRM where the scribe_scribeexternalid equals the Customer.No/Address.CODE. If a matching record exists, skip the record. Otherwise, create the record. Payment Terms/Domain Value Mapping This Map populates the payment terms in Dynamics CRM from payment terms in Dynamics NAV/Financials. Although payment terms are not required, they are included to demonstrate different approaches for domain value mapping. The Payment Terms from Dynamics NAV/Financials need to be set up in Dynamics CRM, ensuring the full name values, such as Net 21 days, are the same. The Create CRM Account Block contains examples of using either the Payment Terms Lookup table or the PaymentTerms.csv file to manage the domain value mapping between Dynamics CRM and Dynamics NAV/Financials. The default option, enabled, is the Lookup Table option. Sample Maps: Microsoft Dynamics NAV/Financials

38 Dynamics CRM And Dynamics NAV/Financials Maps //The below provide examples on how to transform the payment term values between NAV and CRM using the CSVLOOKUPVALUE function and the LOOKUPTABLEVALUE2 function. A sample PaymentTerms.csv file and a sample file to generate the Payment Terms lookup table have been provided in the overall sample package. //CSVLOOKUPVALUE option. Requires an On-Premise Agent. //IF(ISNULLOREMPTY(Customer.Payment_Terms_Code), NULL, CSVLOOKUPVALUE ("PaymentTerms.csv", "NAV", Customer.Payment_Terms_Code, "CRM", True, 1)) //LOOKUPTABLEVALUE2 option. Can be used with On-Premise or Cloud Agents. IF(ISNULLOREMPTY(Customer.Payment_Terms_Code), NULL, LOOKUPTABLEVALUE2 ("Payment Terms", Customer.Payment_Terms_Code)) Related Entities The Dynamics NAV/Financials OData implementation does not support retrieving related entities in a single call. This Map demonstrates using a Fetch Block to retrieve related entities. After the customer records are created, the Fetch Block retrieves all Dynamics NAV/Financials Ship to Addresses with a Post_Code like %US%, where the Customer_No equals the Customer.No of the source query customer. Address Format The main address from Dynamics NAV/Financials is used to populate the address1 set of fields in Dynamics CRM. The Customer.No from Dynamics NAV/Financials is linked to the account.scribe_scribeexternalid field. The Dynamics NAV/Financials Ship to Addresses create additional addresses in Dynamics CRM. The CODE is linked to the customeraddress.scribe_scribeexternalid. For more information on how the address formats differ between Dynamics NAV/Financials and Dynamics CRM, see the CRM Account -> NAV Customer Create Map section. Working With ETags In both the Create CRM Customer and the Create CRM Address Blocks, the ETag from the source Dynamics NAV/Financials records are linked to the scribe_etag fields in Dynamics CRM. Sample Maps: Microsoft Dynamics NAV/Financials

39 Dynamics CRM And Dynamics NAV/Financials Maps NAV Customer -> CRM Account Update Map This Map updates accounts in Dynamics CRM from customers in Dynamics NAV/Financials, including the basic customer information and the main address. Additional addresses are handled in the NAV Ship To Address -> CRM Customer Address Create or Update Map. In the NAV Customer -> CRM Account Update Map: Dynamics NAV/Financials does not provide a last modified by user. All records, including those last updated by the integration, are retrieved. Dynamics NAV/Financials only provides a modified date, not a create date. All records created or updated since the last modified date are retrieved and processed. The last modified field is a date there is no time component. This must be taken into consideration when you create a Solution schedule in a real-world use case. The Update CRM Account Block matches where the Dynamics CRM account.scribe_ ScribeExternalId equals the Dynamics NAV/Financials Customer.No. The payment terms, address format, and ETag information are handled the same as in NAV Customer -> CRM Account Create Map. Sample Maps: Microsoft Dynamics NAV/Financials

40 Dynamics CRM And Dynamics NAV/Financials Maps NAV Ship To Address -> CRM Customer Address Create Or Update Map This Map creates or updates address information in Dynamics CRM from Ship to Addresses in Dynamics NAV/Financials. It retrieves all customers with a Post_Code like %US%, modified since the last run date. In this Map: Dynamics NAV/Financials does not provide a last modified by user. All records, including those last updated by the integration, are retrieved. Dynamics NAV/Financials only provides a modified date, not a create date. All records created or updated since the last modified date are retrieved and processed. The last modified field is a date there is no time component. This must be taken into consideration when you create a Solution schedule in a real-world use case. A Lookup Block checks to determine if the parent account exists in Dynamics CRM. The Lookup criteria checks for an account in Dynamics CRM with a scribe_scribeexternalid equal to the Dynamics NAV/Financials Ship to Address Customer_No. If no account is found, a custom error message is written to the Execution History and that address is skipped. If the parent account exists, the Lookup returns the account.accountid. The match criteria in the Update/Insert Block is configured to match where: The customeraddress.parentid equals the account.accountid returned in the Lookup Block. The customeraddress.scribeexternalid equals the Dynamics NAV/Financials shiptoaddress.code. This is an example of a multi-key match. If a matching record is found, the address is updated. If there is no matching record, a new address is created. The address format and ETag information are handled the same as in NAV Customer -> CRM Account Create Map. Sample Maps: Microsoft Dynamics NAV/Financials

41 Text Files And Dynamics NAV/Financials Maps Text Files And Dynamics NAV/Financials Maps Customers/Addresses Text -> NAV Customers Create Creates a customer in Dynamics NAV/Financials from a customer in Customers_Initial.txt. Each related address in the Addresses_Initial.txt file is created as a Ship To Address in Dynamics NAV/Financials. Customers Text -> NAV Customer Update Merge Updates a customer in Dynamics NAV/Financials from a customer in Customers_ETagUpdate1.txt. Addresses Text -> NAV Customer Ship To Address Update Merge Updates a customer Ship to Address in Dynamics NAV/Financials from an address in Addresses_ ETagUpdates1.txt. NAV Customer -> Customers Text Create Creates Customers_Final.txt from customers in Dynamics NAV/Financials with a US address. Customers/Addresses Text -> NAV Customers Create Map This Map creates customers with a main address and multiple Ship to Addresses in Dynamics NAV/Financials. It uses the Customers_Initial.txt file as the source for customer data, and the Addresses_Initial.txt file as the source for address data. The address data in the Customers_Initial.txt file is used as the main address for the customer in Dynamics NAV/Financials, and the data from the Addresses_Initial.txt file is used to create Ship to Addresses associated with the customer in Dynamics NAV/Financials. The file contains a CustomerID field, which correlates to the IDs used in the Customers_Inital.txt file. The text files are set up with US addresses, using state, zip code, and country values that exist in the Postal_Code configuration in the sample data in the Dynamics NAV/Financials Cronus International, Ltd. company. Payment Terms/Domain Value Mapping The Map populates the payment terms in Dynamics NAV/Financials from payment terms in the Customers_Initial.txt file. The payment terms are not required, but are included to demonstrate different approaches for domain value mapping. To include payment terms on the customer in Dynamics NAV/Financials, you must provide the Payment Terms Code. For these sample Maps, the Payment Terms from the text file are defined so the full name, such as Net 21 days, matches the Dynamics NAV/Financials values. The Map contains a Lookup Block, which uses the payment terms from Customers_Initial.txt to look up the corresponding Payment Terms Code in Dynamics NAV/Financials. The Payment Terms Code value returned in the Lookup Block is then linked to the Payment Terms Code in the Create NAV Customer Block. Sample Maps: Microsoft Dynamics NAV/Financials

42 Text Files And Dynamics NAV/Financials Maps Address Formats This Map provides examples of transforming data for US address formats between the text file and Dynamics NAV/Financials. It presumes: The two-character ISO code is used for both the country and state. The Dynamics NAV/Financials configuration also uses the two-character ISO code for the country region field. The postal code only contains 5-character postal codes. The expected Post_Code format is: Country-State PostCode For example, US-FL While this is the expected format, Dynamics NAV/Financials allows any value to be written to the Post_Code field in the main customer address and the Ship to Addresses. Address CODE When creating a Ship to Address, Dynamics NAV/Financials requires a unique CODE. This CODE is what you see in the interface when you select an address. The Maps populate that field with the first 10 alphanumeric characters of address line 1. Microsoft suggests defining a value that is representative of the address. Working With ETags ETags are required for future update operations. The Dynamics NAV/Financials services do not automatically return the ETags. The sample Maps Lookup Block retrieves the ETags, using the key field(s) from the Create Block and returning the matching ETag. Customers The Create Customers_ETagUpdate1 Block mimics a target application, writing to the Customers_ETagUpdate1.txt file, which is the source file in the Customers Text -> NAV Customer Update Merge Map. For demonstration purposes, all of the source fields are included in this file, along with the Dynamics NAV/Financials Customer ETag and No returned in the Create and Lookup Blocks. Sample Maps: Microsoft Dynamics NAV/Financials