Introduction: A field group in table or table extension objects defines the fields to display in a drop-down control on pages that use the table and fields that display when these pages are shown in the tile view. Syntax of fieldgroup is as follows: fieldgroup(<Name>;<Field>) <Name> : It can be either Dropdown, so as to define the set of fields to be included in drop down view or it can be Brick to define the set of fields to be included in a tile view. <Field> : Here, all the fields to be included are specified each separated from the other one by comma. Pre-Requisite: Microsoft Dynamics 365 Business Central Solution: In Business Central, when using the table extension objects one or more fields can be added to the fieldgroup using the ‘fieldgroups’ control. It can be done by using the addlast keyword.Its syntax is as follows: addlast(<Name>;<Field>). In the example below, I created a table extension object in which I have added a new field. I have added that field in the fieldgroup using the syntax mentioned above. Conclusion: Thus, using the above syntax the fieldgroup control can be added to the table in Business Central and even the existing fieldgroup can be modified to add new fields.

Introduction: Difference in configuration of Role Center between Microsoft Dynamics NAV and Microsoft Dynamics 365 Business Central. Pre-requisites: Microsoft Dynamics NAV Microsoft Dynamics Business Central Solution: In Microsoft Dynamics NAV After creation of Role Center. When assigning the Role Center Page to the User the following process is followed. 1. Creating a new Profile in NAV for the and assign the Role Center Page ID . 2. Assigning the User Profile in User Personalization. In Microsoft Dynamics Business Central: 1. Creating a new Profile in Business Central for the required Role Center and assign the Role Center Page ID. 2. Selecting the User Profile directly in the Settings. Conclusion: This is the difference when configuring Role Center Page in NAV and Business Central

Introduction: Companies want to record some of contacts as customers, vendors, or bank accounts. Creating a customer, vendor, or bank account from a contact enables you use existing data. When you create a customer, vendor, or bank account this way, it is synchronized with the contact. Prerequisite: Setup Business relations Select Business relation codes in Marketing setup in Interaction section. Specify number series for Vendor Customer and bank account Steps: In search option type Contact and choose related link. Create new contact and specify Name, Address and other data which are required. Choose the Create As action, and then choose either Customer, Vendor, or Bank. You will get below pop up once Customer, Vendor and Bank account has been created. The contact information is transferred from the Contact card to the Bank Account card, the Customer card, or the Vendor card. You may want to add specific information to each of the cards, such as invoicing and payment details.

Introduction: Whenever the a single field in NAV contains Name, Address and other values seperated by delimiter such as ‘,’. But this field cannot formated in SSRS to look appropriate as follows. For Example in NAV: John Peter, Long Island, New York,US. Formatting in SSRS: John Peter, Long Island, New York, US. Pre-requisites: Microsoft Dynamics NAV. Solution: Getting a combined value field in this we are concating mutliple values seperated by ‘|’. In this case I’m using the comments on Sales Invoice Lines. This can be a single field or combination of mulitple fields Code to combine all comments in single variable Writing a Query in SSRS report query to seperate the values by delimiter Field and its expression: Output: In this output screen the comments are seperated properly in SSRS report. Conclusion: This is one of the easiest way of combining and seperating and formatting the report by the use of  delimeter.

Item Attributes are user-defined classifications that can be assigned to your items for ease of searching, filtering, and reporting. For example, a Marketing team could use attributes to help with classifying their items to aid in the grouping, sorting, and filtering for a catalog or website. The Sales team could use these same Attributes to search for Items while helping customers. To view Items and item attributes, navigate to Items in Business Central. Attributes assigned to a selected item display in a fact box on the right side of the screen. To modify or update attributes assigned to an item, a user simply selects the carrot in the Item Attribute fact box or selects Attributes in the ribbon from the Item Card. Setting up available Attributes Available Attributes and their allowed values are configurable. To add an available Attribute, a system admin or power user navigates to Item Attributes in Busines Central. From this window, a user can view, edit or add a new Attribute. The available Types of Attributes that can be used are as follows. Option– allows a list of options to be predefined for the user to select Text – allows free text entry of an attribute value Decimal – allows a numeric value (options not predefined) Integer – allows a numeric value – whole numbers only (options not predefined) Filtering by Item Attributes Back in the Item list view in Business Central, a user can filter their view by one or more attributes. To do this, select Filter by Attributes on the Home ribbon.   In the popup screen, the user can enter search criteria for one or more Attributes.   Search operators commonly used in Business Central such as @(ignore upper or lower case),*(wild card),<,>, etc. can be used. After clicking OK, the items displayed in the Item List will only be those items that meet the search criteria. To remove the Attributes filter and return to the full list of Items, simply click Clear Attributes Filter.  

Introduction: When coding an app that uses Webservices to connect to the integration solutions, it is generally recommended that there is a Setup, which we can configure, where the Webservices are created as well as deleted. Pre-requisites: Business Central VS Code with AL Language Extension Demonstration: Create a Setup Page having a boolean variable say ‘SetupExtension‘ and create a field having value as ‘SetupExtension Variable’.Output: On the OnOpenPage trigger add a code to Check if Web Services are already created and accordingly set the ‘SetupExtension‘ boolean field.Thus, whenever the Setup Page is Opened, the ‘SetupExtension‘ field is set as per the records in Web Services. On the OnQueryClosePage trigger write a code which will create the Web Services when ‘SetupExtension‘ boolean is set as ‘TRUE‘ and delete the Web Services if ‘SetupExtension‘ boolean is set as ‘FALSE‘.Output:i. When ‘SetupExtension‘ is set to ‘TRUE‘New Webservices are created.ii. When ‘SetupExtension‘ is set to ‘FALSE‘Web Services are deleted.  Conclusion: Thus this way we can keep the existing app installed and enable/disable Web Services as needed. As compared to creating WebServices.xml file which directly creates the Web Services on installation of the app, I’ll be demonstrating it in my next blog.

Sales Quote use to record an offer to a customer to sell certain product on certain delivery and payment term. You can send quote to customer, negotiate with the customer, you can change and resend the sales quote as much as needed. When the customer accepts the quote, you convert the sales quote to a sales order or a sales Invoice in which you process the sale. In the Search box, enter Sales Quotes, and select the related link. Click on new to create new Sales quote. In the Customer No. field, enter the name of the customer Enter the Order date, Due Date, Requested Delivery date, Quote valid to date on Sales quote header. Select item or G/L Account in the type field in quote line. In the field, select the item number or GL number to be ordered. Enter the quantity you want to order in quantity field. Enter the price in in Unit Price Excl. Tax field When the sales quote lines are completed, choose the Send by Email action. If Customer Accept the quote, then on Process tab click on Make order to create Sales order from Sales quote or Make Invoice to create Sales Invoice. You will get below Infolog when Sales order will be created.  

Introduction: In this blog, I have introduced how to fetch a custom table from Microsoft Dynamics 365 Business Central into Microsoft PowerApps using Common Data Service(CDS) and OData. The table that was created in Business Central was fetched into a custom entity(MatchingLists) in CDS that allows me to create a local database in PowerApps for storing the entity data and OData that helps to fetch and integrate the data. Pre-requisites: Microsoft Dynamics 365 Business Central Microsoft PowerApps Steps: 1. Create a custom entity within Common Data Service(CDS) whose data you want to retrieve from Business Central. 2. Add the fields with their required data types. 3. Get Data from Business Central using OData Integration. 4. Go to web services in Business Central, add the custom page in the web services and use its OData V4 URL.  5.Enter the OData URL and the Organization credentials. 6. You will be shown the list of tables in each and every company. 7. Go to the table whose data you want to get into PowerApps, and select that table. 8. Next is to select the entity to be mapped with this table and field by field mapping of the same. 9. Refresh can be set manual or automatically, if automatic then select the time. 10. Create a list structure to dsiplay the table.

Introduction : This functionality helpful to correct posted Purchase invoice if user make mistake or want to do any changes. You cannot correct posed purchase invoice which are partially or fully paid. Steps: In search bar enter Posted Purchase Invoice and chose the related link. Select and open Posted Purchase Invoice which you want to correct. Click on correct button on Posted Purchase Invoice form. Once you click on correct then you will get below pop up. Choose yes to continue. New Purchase Invoice with same information will be created. Make the changes whichever are required and click on post button to post purchase invoice. In Posted Purchase Invoices form, you can check new posted purchase invoice. Choose Show Corrective Credit Memoto view the posted purchase credit memo that voids the initial posted purchase invoice. Conclusion: This feature reduce the effort of users to create manual credit memo and again create new purchase invoice.

Introduction: Dealing with Electronic Bank Payment Setup can be tedious and time consuming. In this blog, I’ve a unusual requirement where the payment date should be the next day of the check issue date. Pre-requisite: 1. Microsoft Dynamics Business Central 2. VS Code and AL Language Extension Demonstration: 1. In standard Data Exchange Definition, I didn’t find any rule to increment the date by 1 day. So using the Integration Event and Event Subscriber, I’ve written AL Code to use the custom transformation rule and perform the +1D operation. 2. I’ve created a custom Transformation Rule in the Feild Mapping on Data Exchange Definition in this case ‘ADD1D’ and set in the field mapping. 3. In the code I’m looking for the transformation rule with the name ‘ADD1D’ and then use the code to actually add 1 day to the date. Code: 4. Output: Conclusion: This type of customization not only can be done with Data Exchange Definitions. This was an example of how the Integration-Event Subscriber can be used to modify existing functionality in Business Central