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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

Low performance with rapidstart in NAV2018

(0) ShareShare
ReportReport
Posted on by 225

Hi everyone,

I'm finding a extrange problem in NAV 2018 that it's driving me mad, I upgraded a customer's server from 23013 to 2018. In 2013, rapidstart was workimng perfeclty, but in NAV20418, we're finding performance issues. For example, a package from a table with 2 records, and 600 occurrences,  it takes over 10 minutes when applying the package. When I import he excel, it is really wuick, but the problem appears when I apply the package, it takes too long as you can sse, and Navision stays in "Not responding" until the process ends.

This procecss should be realy quick, more gicen that this process, in NAV2013, with a worse server, was working perfectly.

has anyone found this issue? It's a known problem? How can be improved the performance of rapidStart?

Thank you very much

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Stefano Demiliani Profile Picture
    37,166 Most Valuable Professional on at

    Rapidstart performances are the same.

    Is the same package? Are you triggering fields validation?

  • jgaztanaga Profile Picture
    225 on at

    Thanks Stefano,

    The problem is generalized. For example, I've created a new table, with 2 fields, without any validation. Just to load the old and the new code for a few products, and then with an easy procees, to change the codes for those products.

    So, one table, with 2 fields, and exactly 633 records. But as I commented before, it happens with any configuration, not when importing, it's when applying

  • Community Member Profile Picture
    on at

    Hello,

    I have the same problem.

    I've seen there one difference in Codeunit 8611 "Config. Package Management", the ApplyPackage function has now at the end a call to the function FixIntegrationRecordIds.

    This function ends calling the function ApiSetup in Codeunit 5465 "Graph Mgt - General Tools". This function is an integration event which has a lot of suscribers. I guess this is the cause of the low performance, but, why is that FixIntegrationRecordIds function called after we apply data? Can that be removed?

    This is driving me mad too after we migrated customer database from 2009 to 2018.

    Thanks in advance,

    Arsenio

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans