Skip to main content

Notifications

Announcements

No record found.

Finance | Project Operations, Human Resources, ...
Answered

Smartlist Latency After Moving to a New Office

Posted on by 769

Our customer is experiencing Smartlist Latency after moving their offices.  They are running a GL Detail Smartlist for their auditors.  At the old location it runs fine, at the new location it populates very slowly field by field.  What kind of tests or troubleshooting can be done to pinpoint and resolve the problem?

Categories:
  • RE: Smartlist Latency After Moving to a New Office

    Thank you for the information.  

  • Verified answer
    RE: Smartlist Latency After Moving to a New Office

    The question then becomes, has the SmartLists ever ran faster on this new network/new office, or are we trying to compare the performance between the two offices, which isn't really a 1 to 1 comparison?

    We see this often as well, when customers upgrade from one version of Dynamics GP to another, then find something is slower on the new version of Dynamics GP than it was on the original.

    That being said, all of the performance troubleshooting we have is in this white paper that we've put out:

    docs.microsoft.com/.../mdgp2010_whitepaper_performance

    It has the information we've found over the years that have caused performance issues with Dynamics GP, to include SmartLists.

    There's also some information on optimizing and maintaining a network as well that may be useful.

    Other than that, we here on the Dynamics GP support team don't really troubleshoot network latency issues, besides what is mentioned in this white paper.

    Thanks

  • RE: Smartlist Latency After Moving to a New Office

    Derek thank you for your response.  The customer said they are on a new network and I do believe it is a network problem.  The servers have not moved.  The users moved to a new office across the parking lot from the old office.  When the user goes across the parking lot to the old office and runs the reports there is no latency.  So while the test is not on the actual server, the old location does not have latency.  What kinds of tests can be run to narrow down the problem?

    Thank you 

  • Suggested answer
    RE: Smartlist Latency After Moving to a New Office

    The first test I would do is install Dynamics GP directly on your SQL Server where the GP databases are located, then test the SmartList reports from that GP instance, do you still see latency?

    You also don't mentioned what moved? Did the GP server move and/or the SQL Server? I ask because, if it is just a matter of the customer moving to a new location and taking the GP and SQL Servers with them, that in itself shouldn't cause performance issues, though the network in the new location could definitely be different than the network they had at the old location.

    I'd also mention that SmartLists in themselves, are only designed to return approximately 1000 to 3000 records maximum, so if your customer is attempting to run SmartList reports that return more than this amount, they may want to look at using something like SSRS or Excel Reports, which can handle a heavier record volume load than SmartList reports.

    Thanks

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans