Skip to main content

Report Region Format and Language finally changeable without Developer intervention

 

Report Region Format and Language finally changeable without Developer intervention

Did you notice? As of BC23 reports have new settings on the request page that can set the output of the report to the desired Region Format and print them in other languages!



New advance functionality is designed to override default settings from my settings and customer it means you can now print report in any language (if you have it installed) and in any desired format. So, let’s take a quick look at it. 

Regular quote base system settings:

Language: German (Germany)
Format region: Italian (Switzerland)

WOW! I know strange combination nevertheless superb outcome! And it works in RDLC and Word layouts!

And for your consideration this will work only and only if you do not specify a specific format for the field in RDLC. So, in RDLC field has to have format set from the dataset.



Comments

Popular posts from this blog

3 Ways to GET a Record We all know to do a GET of one record based on values of the primary key fields. The standard syntax is as follows: [Ok :=] Record.Get(PK1[Value], PK2[Value],...). Example would be like: SalesHeaderFind.FindFirst(); SalesHeaderGet.Get(SalesHeaderFind."Document Type", SalesHeaderFind."No."); The most used one, isn’t it? What if I tell you that there is a way to make this code shorter. SalesHeaderGet.Get(SalesHeaderFind.RecordId); Yes! It will! This is because RecordID is already the primary key itself and not one of the fields that forms it, as the method expects. Also be aware that in case that the primary key field is of type RecordID you cannot use GET. In this case you will have to use the SetRange method. And the last one as of Business Central 2019 release wave 2 there is a new method, GetBySystemId. The syntax is as follows. [RecordExists := ]  Record.GetBySystemId(SystemId: Guid) Example would be like: SalesHeaderGet.GetBySystemId(Sales...

How to? Integrate into new posting routine V19 – Businesses central.

Since V19 Microsoft has introduced a new posting interface. Depending how you concepted your integration in to a posting routine you might have to refactor your code. Let’s start by looking into what has changed. What we have now from Microsoft is a codeunit 825 "Sales Post Invoice Events" in this codeunit you can find a bunch of publishers that will enable you to integrate into a function from codeunit 80 (for newbies this is the codeunit that handles posting in Sales transferring Sales Order to a Posted Sales Invoice for example). To integrate your logic into posting for any new application you are developing you can use these publishers and find a specific point that suits you the most. Alternatively, you can implement interface "Invoice Posting" if it suits you better. Another change is that the table 49 "Invoice Post. Buffer" is discontinued. Yap! A little bit about this table, in general it is a preparation table for the lines in order for them...

How to? Debug a live session

Did you ever encounter a situation where you cannot replicate the behavior of the bug someone reported, in a test or local environment? Microsoft just made your life a bit easier! As of version 23 access to a session in purpose of debugging is available from the web client. If you go, (screenshots below), to “Help” then “Help and Support” scrolling down a little bit to a troubleshooting tab you will see “Attach debugger to this session” this not only that will jump you to a Visual Studio Code it will also either create a new project for the purpose of debugging or if you have your project open create a launch configuration for the current session, of course after login you will be able to download symbols and attach debugger using one of the created launch configurations. Great, isn’t it? 😊