![]() ![]() Map all accounts from the shared chart of accounts to additional consolidation accounts from the government-mandated chart C. Set up currency exchange rates for the government-mandated chart. Which two steps should you take to enable the mandatory statutory reporting? Each correct answer presents a part of the solution. You need to ensure that foreign subsidiary is able to complete the mandatory statutory reporting while adhering to the local government regulations. This chart is the same for some accounts in your shared chart of accounts, but not for all of them. One subsidiary's local government requires the use of a government - mandated chart of accounts for reporting. Your company has many subsidiaries in various countries that all use a shared chart of accounts. ![]() We will discuss more about the checks, extra spaces issues and other possible ‘black-hole’ scenarios in my next post. ![]() It may seem like a repetitive process, but it’s legit and pays in the long run. So, the best bet is to work on a subsection of report, build/deploy and see if that subsection on the check looks the way you wanted (if not, work on the subsection you just modified), if yes then work on the other subsections turn by turn. With that said, yes theoretically there are couple of settings one can tweak around to get rid of the extra page issue, but they don’t work like charm at all (at least not all the time). I’ve found it easier to play it by ear this way, rather than modifying all the textboxes and then eventually realizing that you accidentally added some extra space somewhere, causing the text to get jeopardized or print extra pages (every developer’s nightmare). If I have lot of modifications involving re-sizing, or particularly changing the layout of the textboxes on the report, I personally try to modify each textbox (or each subsection) and then go for build/deploy to see what the modified cheque looks like. The second part of modifying the check is modifying the Cheque Report itself, i.e. TmpChequePrintout.SlipTxt = strFmt('\t\t'+ '+slipChequeNum+'\n) ![]() One can also use ‘\t’(tab) or StrlFix or StrRFix methods for aligning the string lines, such as if a customer wants check Number to fit the pre-printed cheques, we can deliberately use ‘\t’ tabs: The output method mainly contains the code for adding the check number to the stub. So, whatever we need to do as far as Text formatting (for check stubs) goes, we should get it done before this text (‘chequeSlipTxt’) leaves the class. The getSlipText method is responsible for most of the data that is printed on the check slip lines the key point here is that it is sent as a single block of text which leaves the developer very little room to actually modify the cheque without getting into a stream of circular reference errors (I’d call them ‘black-hole’ type errors, which we will discuss in ‘Check – Intermediate’). Dynamics GP to Dynamics 365 Business CentralĬheck customization is generally easy (at least theoretically) as it revolves around two objects, namely CustVendCheque ( a class ) and Cheque_USReport ( a Visual Studio Report ).įirst we’ll walk through the cheque class itself and see what methods are generally modified to get the checks customized:.Dynamics NAV to Dynamics 365 Business Central. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |