The “Record ID” in the Integration Record table in Microsoft NAV 2013 shows as “<Binary Data>”


If you install the CRM Connector for Microsoft Dynamics NAV 2013 you will find that you cannot read the “Record ID” value directly in the Integration Record table as you used to in Microsoft Dynamics NAV 2009 R2. If you try to look at the contents of this table you will see the following:




This can make troubleshooting a CRM Connector problem difficult as the Record ID is often required to associate a change transaction with a specific row in the relevant NAV table. The solution is to create a Dynamics NAV Page to enable you to format the Record ID into human readable format. The steps below will give the desired result:

1. Create a new Page in the Microsoft Dynamics NAV Development Environment.

2. Specify the page should be built on table id 5151 (Integration Record).

3. Select “Create a Page using a wizard” using the List option:




4. Add all table fields to the new Page and click the “Finish” button:




5. In the Page Designer, amend the SourceExpr, Name and Caption as shown below to ensure that the Record ID value is formatted correctly:




6. Save the Page and run it to see the Integration Record data as required:




7. Note that you can now filter on the Record ID which is a common requirement when troubleshooting CRM Connector issues:




Gerard Conroy

Microsoft Escalation Engineer.

Comments (2)

  1. Janaka83lk says:

    i am referring…/dn250653

    i couldn't comment on that and believe same Gerard Conroy microsoft dynamics nav escalation engineer here

    I am trying to deploy NAV on Azure after run the Example 1 i got these errors

    PS C:NAVonAzureCloudHowTo> C:NAVonAzureCloudHowToExample-1VM.ps1

    WARNING: The names of some imported commands from the module 'NAVRemoteAdministration' include unapproved verbs that might make them l

    ess discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a li

    st of approved verbs, type Get-Verb.

    Please guide me what to do next.

  2. Gerard Conroy says:

    The cause of this warning is indicated in the next VERBOSE error which appears after it in the output. That will show the statement which is using an "unapproved verb". If you are not concerned about your NAV on Azure deployment being discoverable then you can safely ignore this warning message as your newly provisioned environment will still be accessible via the links which will be provided at the end of the log output.

    If you are concerned about it then I would recommend opening a service request with the Microsoft Dynamics NAV support team and providing the full verbose output log for further analysis.

Skip to main content