Speed for Journal Entry Posting
-
Speed for Journal Entry Posting
Posted by DSC Communities on June 16, 2017 at 5:53 am-
C S
MemberJune 16, 2017 at 5:53 AM
Hello,
We use a customized version of NAV purchased through a reseller. Ā In general it is an off the shelf version for non-profits. Ā To my knowledge it is the core NAV system with “Fund” accounting added by the third-party as their enhancement. Ā There are a few add-on modules as well but the fund accounting is more integrated to the accounting interface.
Can you tell me how long we should expect for a journal entry to post in a system with 100+ users. Ā Lets assume a 100 line, 500 line, 1,000 line, 5,000 line, 10,000 line or up to an 80,000 line.
Thank you in advance. Ā We just seek a general benchmark to determine if our speed is acceptable to the NAV public.
Chad
——————————
Chad
—————————— -
Ian Ray
MemberJune 16, 2017 at 3:26 PM
The best I can offer is “a couple of minutes” to “a few minutes.”There is a known, recent issue with workflow that can hang a journal posting. Details are here
https://markbrummel.blog/2016/10/03/performance-issue-with-workflow-solution/——————————
Ian Ray
Cypress Grove
Arcata CA
——————————
——————————————- -
Lew Hope
MemberJune 19, 2017 at 2:25 PM
Can you tell us what version you are on? The workflow issue Ian references doesn’t exist onĀ versions prior to 2016.ĀWorking with a non-profit Fund accounting solution I haveĀ run into a “performance” issue when posting aĀ g/lĀ journal. I have seen it a couple of times, larger database, 100+ gbĀ withĀ 100+ users. I don’t see the issue on the same code with a smaller database on the same code and hardware.Ā
Solution 1: During the process of troubleshooting I determined it was during the delete after the journal had already posted. So, I changed the code. I added a line of code that speed the process up.
I look forward to the feedback on this next one. Also based on version may not be an option.
Solution 2: Solution 1 didn’t fix so,Ā I worked with ISV then with Microsoft. The answer was on the instance. There is an option to “Disable SmartSQL”. Microsoft had me check it. In NAV 2016 it is unchecked by default. I believe in NAV 2017 it is checked by default, this maybe a hint. Posting with Disable SmartSQL checked, 277 lines take 40 seconds. Same lines with Disabled SmartSQL unchecked, posting was done after 40 seconds.Ā Then it takes 15 minutes to delete the batch. Screen is frozen at posting 100% with no update on what is happening.Please feel free to have someone from your team or partner contact me and I can show youthem the code. The “Disable SmartSQL” is handled at the instance and you should be able to test that.
——————————
Lew Hope
knk Software
——————————
——————————————- -
C S
MemberJune 20, 2017 at 5:08 AM
Hello –
The version is NAV 2013 r2.
The solutions offered thus far are interesting. Ā I believe the problem to be in the coding, the challenge then becomes encouraging my vendor to take the action.
In hindsight, a different program may have been better? Ā But I am too understand that NAV should have no problem with a 100+ user system and works well at these user levels.
Thanks to all for your help!
——————————
Chad——————————
——————————————-
DSC Communities replied 8 years, 4 months ago 1 Member · 0 Replies -
-
0 Replies
Sorry, there were no replies found.
The discussion ‘Speed for Journal Entry Posting’ is closed to new replies.