Number := Codeunit1.GetNumber(); MESSAGE(Format(Number));<\/code><\/p>\nThe SingleInstance property in Codeunit1 is set to Yes. Form1 calls a function on Codeunit1 and sets the parameter to 100. Codeunit1 saves this parameter in a local variable. Form2 is now able to get the parameter value (=100) from Codeunit1. A message is displayed.<\/p><\/blockquote>\n
The purpose of this, is that an instance of the object can set a value of variable, that can be accessed from another instance of the same object (codeunit).<\/p>\n
Another important point for single instance codeunits, is that they are not under the rules of the rollback of transactions. So even if an error happens, you can still read the values that were set in the previous rolled back transaction. This is where it becomes handy for as our little detective to finding the G\/L inconsistencies.<\/p>\n
Lets look at Ahmed’s actual code for the single instance codeunit:<\/p>\n
\nOBJECT Codeunit 50000 Single Instance CU\n{\nOBJECT-PROPERTIES\n{\nDate=10\/11\/07;\nTime=[ 2:50:02 PM];\nModified=Yes;\nVersion List=MOD01;\n}\nPROPERTIES\n{\nSingleInstance=Yes;\nOnRun=BEGIN\nIF NOT StoreToTemp THEN BEGIN\nStoreToTemp := TRUE;\nEND ELSE\nFORM.RUNMODAL(0,TempGLEntry);\nEND;\n\n}\nCODE\n{\nVAR\nTempGLEntry@1000000000 : TEMPORARY Record 17;\nStoreToTemp@1000000001 : Boolean;\n\nPROCEDURE InsertGL@1000000000(GLEntry@1000000000 : Record 17);\nBEGIN\nIF StoreToTemp THEN BEGIN\nTempGLEntry := GLEntry;\nIF NOT TempGLEntry.INSERT THEN BEGIN\nTempGLEntry.DELETEALL;\nTempGLEntry.INSERT;\nEND;\nEND;\nEND;\n\nBEGIN\nEND.\n}\n}\n<\/pre>\nThe code you need to insert into codeunit 12, is in the function FinishCodeunit():<\/p>\n
\nFinishCodeunit()\nWITH GenJnlLine DO BEGIN\nIF GLEntryTmp.FIND('-') THEN BEGIN\nREPEAT\nGLEntry := GLEntryTmp;\nIF GLSetup."Additional Reporting Currency" = '' THEN BEGIN\nGLEntry."Additional-Currency Amount" := 0;\nGLEntry."Add.-Currency Debit Amount" := 0;\nGLEntry."Add.-Currency Credit Amount" := 0;\nEND;\nGLEntry.INSERT;\n\/\/MOD01 Start\nSingleCU.InsertGL(GLEntry);\n\/\/MOD01 End\nIF NOT InsertFAAllocDim(GLEntry."Entry No.") THEN\n<\/pre>\nTo use the “detective” you first run the codeunit, that will set the variable StoreToTemp to TRUE, and instantiate the codeunit as single instance.<\/p>\n
Next you run your posting that causes the inconsistency error. NAV will error the same way as it originally did, but now you have also written the GL Entries to our single instance codeunit, where they are stored in a temporary table.<\/p>\n
By running the codeunit again, you will now display a form with the temporary GL entries, and it will be easy to see why the transactions do not balance.<\/p>\n
Kudos go out to Ahmed Rashid for this great tip, and hopefully this blog post can get more people to know about this cool trick. I have it in my toolbelt, and have used it multiple times to troubleshoot with.<\/p>\n","protected":false},"excerpt":{"rendered":"
One of the most difficult errors in NAV to troubleshoot is: “The transaction cannot be completed because it will cause inconsistencies in the G\/L Entry table”. In a standard, unmodified database it is usually related to tax\/rounding issues. And in customized databases, it can be all sorts of issues. I have seen all kinds of […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[56,3,61],"tags":[37,77,60,27,59,39,58],"class_list":["post-770","post","type-post","status-publish","format-standard","hentry","category-basic-cal","category-navision","category-toolbelt-2","tag-application","tag-navision","tag-gl-entry","tag-how-to","tag-inconsistency","tag-programming","tag-single-instance"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/gotcal.com\/index.php\/wp-json\/wp\/v2\/posts\/770","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gotcal.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gotcal.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gotcal.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/gotcal.com\/index.php\/wp-json\/wp\/v2\/comments?post=770"}],"version-history":[{"count":8,"href":"https:\/\/gotcal.com\/index.php\/wp-json\/wp\/v2\/posts\/770\/revisions"}],"predecessor-version":[{"id":1021,"href":"https:\/\/gotcal.com\/index.php\/wp-json\/wp\/v2\/posts\/770\/revisions\/1021"}],"wp:attachment":[{"href":"https:\/\/gotcal.com\/index.php\/wp-json\/wp\/v2\/media?parent=770"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gotcal.com\/index.php\/wp-json\/wp\/v2\/categories?post=770"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gotcal.com\/index.php\/wp-json\/wp\/v2\/tags?post=770"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"\"](\"\/wp-content\/uploads\/2010\/10\/ohno.jpg\" "\\"ohno\\"")
One of the most difficult errors in NAV to troubleshoot is: “The transaction cannot be completed because it will cause inconsistencies in the G\/L Entry table”. In a standard, unmodified database it is usually related to tax\/rounding issues. And in customized databases, it can be all sorts of issues.<\/p>\n![\"\"](\"http:\/\/45.63.48.66\/wp-content\/uploads\/2010\/10\/inconsistency-300x77.jpg\" "\\"inconsistency\\"")
<\/a><\/p>\n