Introduction: To modify the layouts you can remove the fields, tables, or change the position fields. There is an option to extend the Table and Page but to make changes in the existing report there is no extension yet but there is a way you can change the layout of the report. Steps to achieve the goal: Search for Report Layout selection. Select the Report ID which you want to modify. Go to Process ->Custom Layout.  Make a copy of the layout file to do that select new action it will ask you to insert RDLC or WORD according to it will create a file. Then go to layout action in Custom Layout Page->Export layout. Make changes in that file again. Import new modified layout using Import layout action. Make sure to update the layout. Import layout will only import your file you need to update as well. And then go to the Report layout selection page choose the selected layout of the report to be Custom Layout and select your modified report file in the Custom layout description. You can test your new report by Reports-> Run Report. Conclusion: Thus we saw how we can change the layout of existing reports using Report Layout Selection. Thank you very much for reading my work. Hope you enjoyed the blog!

Introduction: LS Central provides an easy way to add Custom functionality through the use of POS External Commands. These commands are executed on the POS and let me know you how to create them. For this example, we will create a POS Command, to remove all the lines from the current transaction. Pre-requisites: Microsoft Dynamics 365 Business Central On Premise V16.5 LS Central V16 Demonstration: You will need a Codeunit in which we define all the custom commands, all your Custom commands can be added in a single Codeunit. Make sure to set the “TableNo” property to “POS Menu Line” table. In the OnRun trigger, we have to handle two cases: Registering the module and associated commands. Procedure to execute when a command is called. For handling the first case, we create a procedure “Register” which takes a “POS Menu Line” as a parameter. In this procedure we use the “POS Command Registration” codeunit to register this module and all the associated commands. I prefer to use Global Labels to store the Module Code/ Module Description and Command Code/Command Description, as this way, any and all changes need be done only once but it is not necessary. Once this is done, the next step is to register the POS Module, this can be done in two ways: Using Retail Modules: Search for Retail Modules in BC Search. Click on “Process” and then “Register.” Search for your Codeunit and click on OK. Using “POS External Commands”: Search for Retail Modules in BC Search. Click on “Process” and then “Register” Search for your Codeunit and click on OK. You can confirm that your commands are visible by checking the list of POS External Commands. Now on the POS, we right-click on a button and click on “Button Properties” Then set your custom command, Now we add multiple Items. And when we press the button, this is the result, as expected. Conclusion: Thus, in this blog, we saw how to create Custom commands which can be used on POS. Thanks for reading!

Introduction: There are some needs where the client wants to add fields in the standard business central report. You cannot make changes in the Standard Business central report. We can change the layout of standard reports by using a custom layout that is present in Report Layout Selection. Steps to achieve the goal: 1. Go to Visual Studio Code -> Download the AL Object Designer Extension I want to modify Sales Credit Memo and I will make a copy of the standard report from the AL Object designer. Create a new report and paste the standard report code. Change the Report ID and Name and add a field that you want to be present in the Standard report. Build and Publish the code in business central. Go to Report layouts selection->Custom layouts download the original layout of the standard report and import it to the new report which you created -> Update Layout. Download the report layout from the new report. Change the layout according to your needs add the new fields which you want to be in the standard business central report. After adding the fields in the new report layout. Import the layout file and Update it. And use your customized report. Conclusion: Thus we saw how we can add fields in a standard business central report by using the AL Object Designer extension. Thank you very much for reading my work. Hope you enjoyed the article!

Introduction: There is a need where you want to replace your customized report with the standard business central report. In which the customized report is a copy of the standard report along with new fields added. So how can you avoid to show two reports with same caption one is your customized report other is standard Business central report. Steps to achieve the goal: In my example, I want to add a field in the Vendor Payment Receipt field. I copied the standard report code. Once you have updated the Layout and add the field publish the code you will be able to see two reports of Vendor Payment Receipt. So in order, that client doesn’t use the old report we can use the Report Management Codeunit. Publish the code and open the report you will be redirected to your Customized Report. Conclusion: Thus we saw how we can replace the Standard report with our own Customized Report using the Report Management Codeunit. Thank you very much for reading my work. Hope you enjoyed the article!

INTRODUCTION: In this blog I would like to share few functional features which are planned for Business Central Wave 2 2020. Also, in this blog I will be sharing some insights into the planned features. Business Central Company Hub extension: Accountant Hub is deprecated to Company Hub in this release wave. Company Hub contains the same features, and Microsoft recommends using Company Hub as a replacement for Accountant Hub. More details here: https://www.olisterr.tech/2020/07/announcement-microsoft-dynamics.html Group VAT reporting: Ease and support for seamless VAT group reporting which will smoothen VAT liability on intra-group entities and optimizing the tax filing. Default unit cost for non-inventory items: Now users will get the default feature of updating cost on Nonstock or catalog items and service items, as these costs impacts production, assembly and sales transactions. Track packages from more types of sales documents: Now users will be able to reverse the posted bank reconciliations. The bank reconciliation will automate the reconciliation of differences. The Payment Reconciliation journal will support application against employee ledger entries, allow one-to-many matching, have preview posting enabled, separate number series, and user-defined document numbers. Bank reconciliation improvements: Now users will be able to reverse the posted bank reconciliations. The bank reconciliation will automate the reconciliation of differences. The Payment Reconciliation journal will support application against employee ledger entries, allow one-to-many matching, have preview posting enabled, separate number series, and user-defined document numbers. Consolidation file format support for Dynamics 365 Finance: The file format options for a business unit in Business Central will include an option for Finance and Operations. Notify users of high-risk changes in selected setup fields: Notification enabled for any change in the value of highly critical field using change log functionality. Use conversion templates to convert contacts to vendors and employees: User can now convert a contact a vendor or an employee. Contact conversion template can be used using conversion. Use recurring journals to allocate balances by dimension values: In recurring general journal using recurring method ‘Balance’ or ‘Reversing balance’ users can now allocate cost of source GL account dimension-wise, earlier only consolidate cost was possible. Use the Copy Journal function on general journals and G/L registers when reversing entries: Copy Journal functionality will be made available to copy the general journal batch with opposite signs (a reversing journal) and different posting date & document number. Use Word document layouts to customize outgoing customer documents: Users can now export document layout to work for the following documents: Shipments, Return Orders, Service Quotes, Orders, Invoices, and Credit Memos. Simply modify the layouts and import them back into Business Central to use next time you send, for example, a shipment, return order, or a service document. Use contact Mobile Phone Number and Email consistently across application: User can now use the Mobile Phone Number and Email fields on data entry pages, report data sets, report layouts, and segment lines that have contact details in Business Central. CONCLUSION: Once there is a public preview/ general availability is released then I will create a follow up blog explaining each feature in detail. Kindly feel free to suggest. Hope this helps!

Most of the businesses that are now using Dynamics NAV are slowly migrating to 365 business central. You need to find and engage with a Dynamics 365 Business Central development company likes us that has vast experience and a good reputation in the market. Since it is cloud-based software, a lot of companies are ramping up their migration efforts. But, there are so many other companies that are still unsure if they should make this move, they are asking if it is worth the penny that they are going to spend on it.  Here are five key reasons why Microsoft Dynamics NAV upgrade to Dynamics 365 Business central  is necessary: Microsoft Cloud Data security is something that most of the IT professionals these days worry about. The best part about Microsoft Cloud is that is not only stable but is also safe and secure. Microsoft is the leader in the industry and they have more than 3,500 cybersecurity professionals working with them. The level of support and guidance that they provide is beyond imagination. It will not only easy to out but will make the IT professionals working with you a lot more productive. You do not have to worry much about the security regulations that change every now and then as well as the managing servers.  Price of the Product It is true that Dynamics 365 is a bit more expensive than the Dynamics NAV. The best part about Dynamics 365 is that it will provide you with a better understanding of the monthly expenses so that you can plan your budget carefully. Shifting to the cloud is a costly affair as you need to take care of various aspects such as licensing fees and so forth. Now, this is the final upgrade that your company requires.  Modern Platform Dynamics 365 Business central is very easy to use as it has similar features as that of Dynamics NAV. Now, this means, you do not have to spend any money on training or other activities to assist the employees that are going to use the system or the software. The best part about Dynamics 365 Business central is that people can access the software from almost any device they have from almost any place they are in using the internet. Users have more flexibility when they use this software.  The New Features Dynamics 365 Business Central relies upon the core functionality of Dynamics NAV. Apart from that, it also has some of the best new features that you do not find in Dynamics NAV. Some of the notable features that you can find in this software are fuzzy search, focus mode, late payment prediction, and a lot more. Since many new add ons and apps are getting added onto AppSource Daily. It helps companies to expand their functionality substantially when they use this software. Business Insights Your business will embrace and adopt Artificial Intelligence (AI) and Machine Learning to become efficient and effective in the way they operate things. Machine Learning can assist with activities such as spam filtering, equipment monitoring, image detection, forecasting, ad targeting and so forth. Microsoft Power Platform which works on Power BI, Power Apps and Flow will provide you with all the relevant data that is timely and accurate so that you can make better decisions related to business. If you are planning for Microsoft Dynamics NAV upgrade to Dynamics 365 Business central, you need to partner with the best company. We are one of the leading and the best Dynamics 365 Business Central development company in the world. Contact us to learn more about the process.

Introduction: In this blog, I will be addressing some of the Table properties in Microsoft Business Central. Pre-requisites: VS Code AL Language Extension Microsoft Dynamics NAV /  Business Central Properties: 1. CharAllowed It sets which characters are allowed in the field. This property can be applied to Table and Page fields. Charalowed takes parameters in a combination of two characters as shown below, where characters “1 to 4 “, “7 to 9” and “a to d” are allowed. An example of this property is given below. Definition Error 2. DataPerCompany It sets whether the table data applies to all companies in the database or only the current company. The default value for this property is true. This property can only be applied to Tables. The User table is an example where Datapercompany is false. 3. DataCaptionFields Sets fields defined on the Top Left Position of the Card page. It can be applied in Table. Syntax: DataCaptionfields= Field1,Field2,Field3; In below example, I have used No, Name and Type fields for Caption. Definition Result 4. Enabled Sets a value that indicates whether a field is enabled or disabled. It can be applied to Page fields, Table fields, and Actions. In the below example, I have set Enabled Property to True on Name field, therefore Name is field is visible to users but it is not editable and it is displayed Gray in color making it less highlighted than other fields. Enable = False   Hope this helps!

Problem: A friend of mine was looking to migrate their Business Central development and support from one partner to another. While, asking me for advice, I was evaluating what was the best solution knowing that their Business Central had customization installed and I found this which made it easy for them as their going to continue customizing Business Central from another partner. Solution: In Business Central version 14 Sandbox, you are allowed to Download Source Code. But in Business Central version 14 Production, this was not the case. No Apps. could have been downloaded even though you got it developed from a Partner/ Developer and installed from them.In Business Central version 15 Sandbox, you are allowed to Download Source Code just like you would in Business Central Version 14 Sandbox. Download Source Code for Installed Extensions in Business Central V15 Sandbox And this is also the same condition  for Business Central version 15 Production tenant as well. Download Source Code for Installed Extensions in Business Central V15 Production Without this, the possible solution to get your app source code back from Production, you would be required to make a copy of Production into Sandbox and download it from there in Business Central Version 14. Note: This doesn’t apply to apps installed through MarketPlace.  Trust me I have tried 😜!!! Conclusion: When App was installed in Business Central Version 14 Production ensured Partners / Developers that app couldn’t be reused on other tenants. This put most of the pressure on the Customers to explicitly to ask the Vendor to provide the App File. Whereas when an App is installed on Business Central Version 15 Production, it can be downloaded and installed in another Business Central Tenants. This means that if the Customers want to change their partners, they can seamlessly do this without having the awkward conversation of asking the code from their previous partner.

Problem Statement: Every document that goes out or comes into Business Central requires some kinda validation to check its originality which confirms the confidentiality of the document. Introduction: This blog is a two-step process in which I will be explaining how things work and how to write a code for this. This blog also is an update on Hannes Holst Blog(https://www.hannesholst.com/blog/technology/hash-hash-baby-secure-hash-algorithm-in-nav-365bc-and-a-little-more/) and you don’t need to access any  .NET variable.   Pre-requisites:   Microsoft Dynamics Business Central VS Code AL Language Understanding of how data is transferred using API   Books & References:   https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/httpcontent/httpcontent-data-type https://www.hannesholst.com/blog/technology/hash-hash-baby-secure-hash-algorithm-in-nav-365bc-and-a-little-more/ https://www.yammer.com/dynamicsnavdev/threads/465800571707392   Demonstration: 1. Creating a Hash Value: Whenever a file is Uploaded to Business Central Document Attachment Table, Business Central should auto-calculate its Hash value. The Hash Algorithm will be selected on a setup. Creating a Local Hash Value field in the Document Attachment Table.   Document Attachment Table Extension   Hash generated by Business Central Create a set of the field on Setup Table where you will be selecting the Hash Algorithm. API Setup for Trokt App Calculating Hash Value using the Cryptography Management Codeunit. Thanks to Natalie(https://www.yammer.com/dynamicsnavdev/threads/465800571707392), who pointed me in the right direction. Creating HASH Value from File After the computation of Hash Value, the Third – Party Tool API should be triggered with a parameter as the Hash Value. 2. Integrating API with Third-Party Tool: When API has triggered with the Hash Value as a form data, the Third-Party Tools recognizes the Hash Value and then auto-computes other parameters and returns their unique value. API Call with Form – Data payload and storing response This unique value is going to be stored in the Business Central Document Attachment Table.   Attaching File and getting TROKT HASH in Document Attachment Table Checking the API Data through POSTMAN passing the HASH Value as a Filtering Parameter Checking if HASH Value was passed to TROKT API Conclusion: Overall, this was the journey as a trial and error process for one of my clients Proof of Concept. I’m really happy with how perfectly it turned out to be.  

Introduction: With Business Central now progressing it’s way in the market, Microsoft will be releasing seamless upgrades every 6 months i.e April(Wave 1) and October (Wave 2). Thus, this means that with each wave there are going to be public preview coming up for the customers to get few insights as to what all is expected. Pre-requisites: Microsoft Dynamics 365 Business Central. Books & References: https://docs.microsoft.com/en-in/dynamics365/get-started/release-schedule https://freddysblog.com/2019/07/31/preview-of-dynamics-365-business-central-2019-release-wave-2/ Demonstration: There are two ways to get Microsoft Dynamics 365 Business Central Public Preview 1. Create a new Sandbox: In the Admin Center for Business Central, you can create a new Sandbox with preview Signing Up Business Central Sandbox for Version 16 Public Preview Microsoft Dynamics 365 Business Central  Wave 1 2020(V16) on Sandbox 2. Create a Docker Container: Referring to https://freddysblog.com/2019/07/31/preview-of-dynamics-365-business-central-2019-release-wave-2/I had noticed that when you are creating a docker container using BC INSIDER, you will get a the latest version of Business Central Docker Container. Microsoft Dynamics Business Central Wave 1 2020(V16) Container Setup Business Central Login Business Central Wave 1 2020 (Version 16) Container Sandbox Note: For you to get access to BCINSIDER, you will need access to Microsoft Collaborate. There inside the packages, you will find the text file which will contain the access credentials to BCINSIDER container image. Conclusion: I hope this blog helped in anyway setting up public preview in Microsoft Dynamics Business Central. In my upcoming blogs, I will also showcase how we can setup public preview in Microsoft Dynamics 365 Business Application.