olisterr.tech | Blog on Dynamics 365 Business Apps, NAV / Business Central, Power Platform and Azure

Introduction: In a typical Business Central implementation or support project, we might need to Support requests to Microsoft Team. A Microsoft partner is most likely to have a Support Contract in place. In this blog, I'm going to showcase how to raise a support ticket through Business Central Admin Center  Pre- requisites : Understanding of Business Central Admin Center A brief idea of Microsoft Partner Center Demonstration: 1. Business Central Admin Center: You can visit Admin Center by visiting -  https://businesscentral.dynamics.com/<AZURE AD TENANT ID>/admin Or through Business Central, you can click on Settings > Admin Center. If your Business Central Production Environment is down, I recommend raising the RED FLAG ticket and the highest priority ticket will be raised by using Report Production Outage. Report Production Outage Fill in Contact Details Fill in issue details   For any other issues, I recommend using Support > New Support Request 2. Power platform Adm

Introduction: When you are using Business Central On-Premise, we might need to set up the Development Environment for AL Extension through Business Central Administration. In this blog, I will be sharing how to set up Development Environment connectivity on your local device and Business Central On-Premise hosted on a Server using UserPassword. Pre- requisites : Understanding of Authentication  Understanding of Business Central Administration VS Code AL Language Extension Business Central On-Premise Demonstration: 1. Set up Networking:  i. Enable Port through Inbound Port Rules in Azure: By default the Development Port required for Connectivity is disabled. Hence you will need to add the port in the Inbound Port Rules. ii. Enable Port through Inbound Port Rules in Advanced Firewall Settings: Add the port in the Inbound Port Rules in Firewall Settings. Add Inbound Port in Firewall 2. Set up Development Configuration in Business Central Administration: By default, Business Central Admini

  Introduction: With Business Central getting stable, Microsoft is adding more features in order to make the lives of Users easier. One such feature I would like to discuss is the Standard Journals in General Journal. Pre- requisites : Microsoft Dynamics Business Central (OnPremise or SaaS) Understanding of General Journals Books & References: https://docs.microsoft.com/en-us/dynamics365/business-central/ui-work-general-journals Demonstration: 1. Open General Journal and create Entries: You can do a search in Business Central for General Journal and select General Journal Batch which will open the General Journal. You will need to add Journal Entries as usual. Basically these entries are the ones that you will be repeating over a period of time. For Eg: Recurring G/L to G/L Transfers Create General Journal Entries 2. Save Entries with/without Amounts: On the General Journal, click Save Entries in General Journal which will open a form to ask you the basic details. Open General Jour

Introduction: When you setup a Business Central Server on Azure for Development / Non- production activities and do not have Disaster Recovery backup setup, there are chances that your VM might not boot up. Most of the times there are issues with billing, networking or even Windows Update and still can be recovered through Azure Support. However the situation I face was Blue Screen of Death and there was lower chances of booting up. Pre-requisites: Fundamental understanding of Azure Microsoft Azure Subscription  Demonstration: 1. Create Disk Snapshot: Generally installations can be done again. However Databases are something important for you. Hence, you will need to attach your crashed VM Disk Drives as auxiliary Disk Drives to a working VM. For existing Drives, you will need to make a Disk Snapshot from the existing Disk Drive. Go to VM > Disks > Select Disk Drive > Make Snapshot. Disk Drive you would like to backup Create Disk Snapshot Create Disk Snapshot > Provide Disk

Introduction: In the previous blog, we saw that you can migrate Data from crashed VM to a new VM. Generally, if a machine is re-setup, the IP address of the machine changes implying that whichever services consumed the services from the original machine has to be reconfigured. In this blog, we will see how to migrate IP Address (Network Interfaces) from one Azure VM to another Azure VM. Pre- requisites : Understanding of Azure Azure Subscription Demonstration: 1. Disassociate your Network Interface: Disassociating the Network Interface will disable the networking connectivity with a specific IP. Please note that your existing work has to be saved to avoid disturbed Network Connectivity. Disassociating works similarly to physically disconnecting your machine from your gigabit ethernet. Goto VM(to disconnect from) > Public Address > Overview > Hit the Disassociate Button Goto Public Address on Azure VM Network Interface - Overview - Disassociate 2. Associate the Network Interfac