Skip to main content

Notifications

Microsoft Dynamics SL (Archived)

SLOW PERFORMANCE RELEASING SCREEN AR 08.050.00 PAYMENT REGISTER

(0) ShareShare
ReportReport
Posted on by Microsoft Employee

Hola, estoy experimentando lentitud en el sistema al momento de liberar lotes en la pantalla 08.050.00 registro de pagos.

Versión 7FP1  con SQL2008 R2

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: SLOW PERFORMANCE RELEASING SCREEN AR 08.050.00 PAYMENT REGISTER

    08 screens are AR.  The tables I mentioned have records for each period.  So if someone, as was the case for us, entered a payment received date of 03/03/3015 SL creates the 12000 future periods.  Then when you post another batch to the current period it updates the closebal in CashAvgD for the period of the transaction, then it has to updated the future periods (12,000) of them.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: SLOW PERFORMANCE RELEASING SCREEN AR 08.050.00 PAYMENT REGISTER

    Can you explain why this would affect performance?  I'm so confused about that.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: SLOW PERFORMANCE RELEASING SCREEN AR 08.050.00 PAYMENT REGISTER

    Hi, I would look for a future date in ARtran and\or CAtran.  Fix that then delete the future records from CashAvgD and CashSumD.

    No warrenty expressed or implied.

    thx, google translater

    Ayrin

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: SLOW PERFORMANCE RELEASING SCREEN AR 08.050.00 PAYMENT REGISTER

    Hola, me gustaría ver a una fecha futura en Artran y \ o Catran. Fijar que a continuación, elimine los registros futuros de CashAvgD y CashSumD.

    No Garantia expresa o implícita.

    thx, google traductor

    Ayrin

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: SLOW PERFORMANCE RELEASING SCREEN AR 08.050.00 PAYMENT REGISTER

    This screen, and others, can be slower if the SQL transaction log is very large.  Routine maintenance of the transaction log needs to be done to shrink that log file down in order to keep performance up.

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

News and Announcements

Announcing Category Subscriptions!

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 Verified Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

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

#2
Martin Dráb Profile Picture

Martin Dráb 230,370 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans