web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

NAV2016 CU1: Posting Performance of large Gen. Journals

(2) ShareShare
ReportReport
Posted on by

In NAV2016 the posting of large Gen. Journals (>5.000 Lines) is nearly unpossible.

Line Check, Balance Check an the posting itselfs is fast als allways, but deleting the gen. Journal lines is terrible slow.

I found the Problem in 2 Subscriber Functions in Codeunit 1535 and 1550, which are called at every delete.

After deleting this functions the posting process performs normally.

Hopefully in future CUs the event-functions are more performant.

*This post is locked for comments

  • Jens Glathe Profile Picture
    6,092 on at

    Hi Johannes,

    thank's for sharing this.

    with best regards

    Jens

  • 4BzSoftware Profile Picture
    6,073 on at

    Thank you Johannes!

  • Roberto Stefanetti Profile Picture
    12,998 on at

    hi,

    can you test posting with NAV 2016 CU3 ?

    NAV 2016 CU3 released today

    community.dynamics.com/.../cumulative-update-3-for-microsoft-dynamics-nav-2016-has-been-released

  • Johannes Stadler Profile Picture
    on at

    Hi,

    yes - in CU3 it is the same Problem.

  • M. Ionescu Profile Picture
    10 on at

    Hi Johannes,

    I have the same issue but in CU8.

    Please, can you give me more details about what you changed?

    Kind regards

  • Suggested answer
    Community Member Profile Picture
    on at

    If you are not using Workflows in General Journal Lines, Try commenting below line in Table 81 and see if it helps.

    Table 81 - OnDelete() Trigger

    //ApprovalsMgmt.OnCancelGeneralJournalLineApprovalRequest(Rec);

    Pl. do thorough testing in test environment prior implementing solution in Live.

  • Peter D. Jorgensen Profile Picture
    110 on at

    Had the same problem, and solved it by deleting a bunch of event subscribers in codeunit 1535 and 1550.

    For details: forum.mibuso.com/.../nav2016-long-wait-after-having-reached-100-when-posting-g-l-journal

  • Suggested answer
    Jens Glathe Profile Picture
    6,092 on at
  • Andri Wianto Profile Picture
    406 on at

    Thanks, Johanes.

    Your solution is work. While others are not.

    I tried to remark the code, but still bad performance.

    Try to delete this function, or change it to non event, could work.

    I delete 3 functions:

    COD 1550
    RemoveGenJournalLineRestrictionsBeforeDelete
    COD 1535
    DeleteApprovalEntriesAfterDeleteGenJournalLine
    DeleteApprovalCommentsAfterDeleteGenJournalLine

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans