Skip to main content

Posts

Upgrade To NAV 2013 or Later - Transferring Record Links From 5.0 or 2009 To 2013 or Later.

Hi All, Today we will discuss an Common Issue which we face during upgrade to NAV 2013 and Later from NAV 2009 or Previous Versions. After Data Migration All Data come as-is but Due to some Reason the Migration Process did not process Record Links To New Version. The Table 2000000068 Record Link Which we are discussing in This Article, have different architecture in NAV 5.0, 2009 and 2013 Onwards. That Might be one reason. All Thanks To  +Suman Maharjan  , For Raising the Issue To me.

Microsoft Dynamics NAV 2016 - Issue With Deferral Posting.

Hi All, Today I would like to Discuss With you an Issue That I Found with a New Feature Released with Microsoft Dynamics NAV 2016. If you remember, with Microsoft Dynamics NAV 2016 a New Feature have been Released Called as Deferral Posting.

RDLC Report - The tablix ‘Tablix1’ has a detail member with inner members. Detail members can only contain static inner members.

Hi Readers, In This article we will discuss how to resolve an Issue that we face During Creation of a RDLC Report. Applies To - NAV 2009 and Later (RDLC Reports) Scenario - You are creating Say a Document Report. There are multiple tables in Body. For Linking these tables you put all these tables inside a List. When You want to save the Report, You get an Error Message - Error while validating RDL content: The tablix ‘Tablix1’ has a detail member with inner members. Detail members can only contain static inner members.

Add User to Microsoft Dynamics NAV 2016 Database.

Hi All, As New Version Release there are some changes in System Tables and the way how we resolve our issues that we found solution in Previous Versions. With Release of Microsoft Dynamics NAV 2016, our famous issue Get Access to Database Need to be resolved. If You Don't know the issue, here is a simple details - You Receive a Database From Customer or you have a database on your server but you are not part of the Users in the database. When you try to access the Client (Windows / Web / Tablet / Phone) System generates Below Error Message. You do not have access to Microsoft Dynamics NAV. Verify that you have been set up as a valid user in Microsoft Dynamics NAV.

NAV 2016 - Cumulative Update 2 Released.

Hi all, Please find below the details of  Cumulative Update 2 released for Microsoft Dynamics NAV 2016. Title - Cumulative Update 2 for Microsoft Dynamics NAV 2016 Build No. - 43897 Release Date - Dec, 2015 Local Version Included - AU, AT, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, RU, SE, UK. Download Link Note: Implementing this cumulative update will require a database conversion. Some Demanded Changes After Release of NAV 2016 are Part of CU 2- The Symbol menu no longer works. (F5 Will Work Now with Intellisense) An extension object cannot be added when a deleted base object had the same ID. NavEventSubscription error when you start the NAV server if a publisher reference is missing. You cannot publish an extension if it contains too many objects. IntelliSense should not show obsoleted methods. (From Clean Up Series)

NAV 2015 - Cumulative Update 14 Released.

Hi all, Please find below the details of  Cumulative Update 14 released for Microsoft Dynamics NAV 2015. Title - Cumulative Update 14 for Microsoft Dynamics NAV 2015 Build No. - 43887 Release Date - Dec, 2015 Local Version Included - AU, AT, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, RU, SE, UK. Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented cumulative update rollup 9.

NAV 2013 R2 - Cumulative Update 26 Released.

Hi all, Please find below the details of  Cumulative Update 26 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 26 for Microsoft Dynamics NAV 2013 R2 Build No. - 43896 Release Date - Dec, 2015 Local Version Included - AU, AT, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, RU, UK Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.