29
Apr2015
Source Code must have a value in Gen. Journal Line
by Mark
in Technical
Error posting Customer opening balances generated by “Create Customer Journal Lines” report:
This error occurs under the following conditions:
- Running the “Create Customer Journal Lines” report to create a journal for customer opening balances
Balances are populated directly in the Journal Line Amount field
The Journal is posted
Under these conditions, the “SetupNewLine” function on the Gen. Journal Line table is not triggered to populate the Source Code. The report itself doesn’t default it either, so the above error will occur on posting.
There are several options to solve this problem:
- Copy the journal out to Excel, delete the journal, enter the balances in Excel and paste back into NAV
- Setup a “Standard Journal” with a blank line suiting your needs, and specify this when running the report
- Modify the report to pull the Source Code from the Journal Template (source below).
The first two options should suit most scenarios, but, where they can’t be used the following minor code change can be added to the report to populate the Source Code as required:
New Function “GetSoureCode” created to lookup the General Journal Template used, and return the Source Code.
In the Customer – OnAfterGetRecord() trigger, in the section of code run if “GetStandardJournalLine” returns FALSE, enter a line to validate the Source Code using the new function created.
Categories
Recent Posts
Archives
- 2019
- 2015
- 2014
- 2013
- December
- November
- October
- Downsizing Dangers - 28th October 2013
- Dynamics NAV NAS/Job Queue - Excel SaveAs method failed - 18th October 2013
- New in XLCubed 7.5 - 16th October 2013
- How to suspend and resume SQL database mirroring - 15th October 2013
- XLCubed: Excel Dashboards - 11th October 2013
- Analytical Applications of Business Intelligence Reporting - 10th October 2013
- What is Microcharts? How can it clarify data? - 10th October 2013
- Can’t print from XLCubed Web Edition - 2nd October 2013
- September
- June
- February
- January
- 2012
- 2011
- November
- August
- July
- May
- A call to SSPI failed in NAV 2009 R2 - 31st May 2011
- Can’t send BizTalk documents from NAV2009 Role Tailored Client - 23rd May 2011
- Unique External Document No. on Sales Order - 23rd May 2011
- CRM 2011 – NAV 2009 R2 Synchronisation – tips and tricks - 10th May 2011
- Manually Create NAV Service Instances - 3rd May 2011
- April
- March
- February
- January
- 2010
- December
- November
- SQL Maintenance plan won't run, modify or delete - 24th November 2010
- Miscellaneous NAV RTC Development Tips - 21st November 2010
- NAV RTC Development training tools - 18th November 2010
- Microsoft Dynamics NAV Application Objects - 15th November 2010
- Delete a rogue Conur Expense Report - 12th November 2010
- CRM - 9th November 2010
- October
- September
- February
Tags
- 2009
- 64bit
- antivirus
- application objects
- BI
- BizTalk
- blocking
- Business
- Business Intelligence
- c#
- C#
- cached password
- calculation
- CGRS
- Cloud
- Commerce Gateway
- concur
- CRM 2011
- CRM 2013
- Crystal Reports
- csv
- Data Type
- date and time
- deadlock
- delete
- DotNet
- Downsizing
- Dynamics
- Dynamics NAV
- EDI
- ERP
- Excel Buffer
- External Document No.
- Generate xsd from SQL table
- impersonation
- Jigsaw
- Job Queue
- MDX
- Microsoft Excel
- NAS
- NAV
- NAV 2009
- NAV 2009 R2
- NAV Application Server
- NAV Development
- NAV Upgrade
- NAV2009
- NAV2013R2
- NAV2015
- Navision
- new version
- no delimiter
- NST
- OLAP
- Permissions
- printing
- regsvr32
- right-click
- security
- Security
- service broker
- SMTP
- SQL
- SSPI
- SSRS
- sync
- synchronisation
- umbraco
- upgrade
- User Setup
- Web Service
- xlcubed
- xmlport
- xp_ndo
- xp_ndo_enumusergroups
- xp_ndo_enumuserids