Reason:

---

• NAV and CRM can be integrated using inbuilt standard features. However, there are certain scenarios where CRM have new / customized fields. These data if required in NAV, then you’re at the right blog to see ‘How-To-Do’ this.

Who can do it?

---

• Knowledge of NAV Development
• Knowledge of NAV Table objects
• Basic knowledge of PowerShell commands
• Basic knowledge of CRM, its Entity and Fields

Pre-requisites:

---

• NAV 2016 or above
• Access to NAV Development environment and NAV developer’s license
• CRM access (credentials and connecting URL required)

Steps:

---

1. IDENTIFICATION-
   1. In CRM, identify all Custom fields in Entity. (just for cross-verification later)
   2. 
   3. These fields will be required in NAV as well.
   4. What in case if there is any new Entity in CRM which need to relate to NAV? (Ans: I will show steps for that too)
   5. 
   6. Now, what do you think is required to connect this entity and field with NAV?
      1. Maybe same table structure in both application’s DB? (yes)
      2. Connectivity between NAV and CRM? (yes)
2. TABLE MAPPING-
   1. In NAV, we can either use existing table or create new table-
      1. When to go for new NAV table, if-
         • New Entity in CRM disconnected with NAV
         • Existing Entity in CRM disconnected with NAV
      2. When to modify existing NAV table, if-
         • Existing Entity in CRM connected with NAV
         • New fields to be added in NAV
         • Fields to be deleted/disabled in NAV
   2. Below are steps to create new NAV table which will relate to CRM entity-
      1. Very simple!! Just execute a Windows PowerShell command (with Administrator rights).
      2. After you import required PowerShell script of NAV, you can use ‘New-NAVCRMTable’ command.
      3. 
      4. How this command works and parameters required to generate something? (Answer on next point)
      5. Consider a sample command ‘New-NAVCrmTable -Credential (Get-Credential -UserName crmnav@xyz.com -Message “Enter Password”) -CRMServer https://<CRMInstance>.<CRMServerDomain>.com/crmnav -EntityLogicalName <CRM Entity name> -ObjectId <NAV Table Object ID> -Name <NAV Table Object name> -OutputPath <File path>’
         • New-NAVCrmTable – Refer (https://docs.microsoft.com/en-us/powershell/module/microsoft.dynamics.nav.model.tools/new-navcrmtable?view=dynamicsnav-ps-2018)

Parameters	Description	Example(s)
-Credential	Specifies a credential required to connect to provided CRM Server	I’ve used ‘Get-Credential’ command of Windows PowerShell which is more secure way.
-CRMServer	Server details of CRM. It is basically in URL format.	-CRMServer https://<CRMInstance>.<CRMServerDomain>.com/crmnavOr -CRMServer https://<CRMInstance>.<CRMServerDomain>.com/
-EntityLogicalName	This is Entity name of CRM. This can be identified in step 1. d.	-EntityLogicalName quoteOr -EntityLogicalName salesorderdetail
-ObjectId	This is new NAV Table object ID which will be created by PowerShell.	-ObjectId 50000
-Name	This is new NAV Table object name which will be created by PowerShell	-Name “CRM Sales Quote”Or -Name “XYZ Table”
-OutputPath	This is file path where PowerShell will generate and export .txt file of NAV Table object	-OutputPath C:FilePathOr -OutputPath D:FilePath

• Get-Credential – This is PowerShell provided command. It is used so that developer enters the credential of CRM instead of mentioning it on command. Refer (https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/get-credential?view=powershell-5.1).

6. After successful execution of PowerShell command, it generates a .txt file with ‘T’ as a prefix followed by Object id. For example, T50000.txt
7. Import .txt object file in NAV and compile it
8. New Table object will be created in NAV with all fields available in CRM’s entity
   • This table will not run until ‘CRM Integration’ is enabled in NAV
9. TABLE thing DONE 😊

1. Below are steps to work on exiting NAV table which will relate to CRM entity-Below are steps to work on exiting NAV table which will relate to CRM entity-

1. You need to follow all the steps in 2.b
2. Beware, do not directly import or replace existing NAV table.
3. Here additional work will be to merge existing NAV Table object’s text and recently created NAV Table object’s text (from step 2.b.vi.)
   • This may include merging of new fields
   • Merging of field properties
   • Merging of new field type (rare case)
4. After successful merging, you need to import merged object in NAV and compile
   • This table will not run until ‘CRM Integration’ is enabled in NAV
5. Pretty Easy!!

3. FIELD MAPPING-
   1. Field mapping is only required when existing NAV Table object is modified.
   2. All CRM fields in Entity will be readily available in a .txt file which was generated from above steps.
   3. Hence, no manual work in this case.
      

      ---

      Feel free to mail me on manish.kutar@ecanarys.com if you need any further information on this