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!

Sometimes we may get scenario wherein we have to make API calls to an entity from dynamics 365 Portals, so here is my blog that will guide you step by step to how to achieve the same. In CRM navigate to dynamics 365 Portals as shown below. Click on entity list as shown below Click on new as shown below. Enter name in the name field. Select the entity to which you have to make API request. Select website. Click on add view and select view. Click on save and save the record. Now click on OData Tab Select Enabled. Select Enabled. Now Select view (Note: Only the fields in the view will be exposed to the API). To access API use https://domain/_odata/GetAccountsData By accession above URL in browser you will be able to reterive data from Account entity.

When a product can be sold, purchased or stored in more than one unit of measure, it’s important that you set up the correct unit of measure conversions. I recently came across an issue where the unit of measure conversions I created in HQ was not showing up on POS. As you can see in the above image I kept receiving this error. Finally I fixed it after a lot of research and trials. The issue was very minor but it took a lot of time to detect it. Go to units and make sure the language selected in Translated unit descriptions is similar at store level and in workers form as well and then you should not face this issue Hope this helps!

Go to Admin settings. Click on system settings After clicking on System settings, a popup opens, click sales tab as shown below. Select Yes in Customize close opportunity form and click ok, refer below image.

Go to Admin settings Click on system setting After clicking on System settings, a popup opens, click sales tab as shown below. Now, select no for Qualified lead experience refer below image.

In this blog I am going to explain in brief about  the Purchase order approval mobile workspace. This workspace lets you view purchase orders and respond to them through actions. For example, you can approve or reject a purchase order. After a purchase order (PO) has been created, it might have to go through an approval process. After the vendor has agreed to the order, the PO is set to a status of Confirmed. POs that don’t use change management have a status of Approved as soon as they are created. A PO creates inventory transactions only when it reaches the Approved status. Once you’ve activated the Change management, approval workflow is introduced. As a system administrator, you must publish the Purchase order approval mobile work space To do that Click Settings> Mobile app. Select the mobile workspace to publish. Click Publish Now on your mobile go to Playstore and download Microsoft Dynamics 365 Unified Operations App Once you have downloaded the App and logged in you should see the Purchase order approval workspace on your Mobile App  

Introduction  This blog demonstrates one of several ways to display Business Validation Message to be rendered as Errors in Canvas Apps when User Create or Update record in Canvas Power Apps.  Scenario  Developers need to show Validation Messages thrown by D365 CRM Plugin to be rendered as Errors in Canvas Power Apps where D365 records are created or updated by using Power Automate.  Steps  Below are steps needed to be followed to display Error Messages.  Create variables for Message & MessageType of type String and initialize default value as a successful scenario for record creation in D365 as below Set Variable VarMessageType should run after your CDS Action has failed Set Variables for the Error scenario with below settings MessageType – ‘2’  Message – message attribute of a body for action of CDS  Add action Respond to PowerApp or Flow with output as below Set Action Respond to a PowerApp to run after successful or skipped Handle the MessageType return in Save Action button in Power Apps. Note:   You can set only 1 Response to a PowerApp action in single Power Automate.  Conclusion : Hope above blog gives an option for Error handling in Power Apps for records created using Power Automate. 

Problem Statement: I have a requirement where the user will select multiple attachments of choice from a list of Documents and Email them. Pre-requisites: VS Code AL Language Extension Microsoft Dynamics Business Central Solution: Step 1: Create a drill-down on the field where the user will select attachments from a list of Documents. Here we have used Page Document Attachment Details as a drill-down page where I have attached some documents. Drill Down In the above code, I have created a drill-down of page Document Attachment Details. SetSelectionFilter() – To get selected attachments from the list of Documents. Step 2: Here I have created Instream and Outstream Objects for Attachments as shown below: In the below code Rec_Sample is a Record variable for sample table which contains the Media field “Document Reference” which stores the unique Document Reference ID of a single Document. After that, the same document is exported and Imported using Exportstream and Importstream. And AddAttachmentStream is called with the Instream object to add the attachment. This is done for the number of attachments selected and then the mail is sent. Conclusion: This way we can send Multiple attachments selected by the user and email them. Hope this helps!

Introduction: There can be a case where developers might need to display data from different companies in NAV or Unique view of Tables displaying unique values of a table or Joins from Tables. In such cases, developers can use the “LinkedObject” property of a table. Pre-requisites: VS Code AL Language Extension Microsoft Dynamics NAV Solution: Step 1: Go to SQL Server Management Studio and create a view of the table from where you want to display field values. Here I have created a view of Customer Table to display distinct Customer Names. And saved the view as “AdityaCustomer” Company Name as the prefix. View Step 2: Now, In NAV Development Environment create a table with the same as the view that has been created, Do not include the company prefix. And add the field with the same name of the field included in View. Table in NAV   Linked Object Property Step 3:  When this Table is run, you can see distinct Customer names in the Table. Conclusion:  This way developers can display data from Views using LinkeObject property. Hope this helps!

Introduction In this blog, we will look into how to resolve the “Root Web Pages are not getting created in D365 Portal” issue. Whenever we create a new web page in a portal its root web page automatically gets created and this root page renders entity forms, entity list or web form on the portal. In one of our environments, root web pages were not getting created automatically. We followed the steps below to resolve this issue. Steps Navigate to Customizations -> Customize the system => Default solution will open Select SDK message processing steps Change the view to “All” Filter by primary object type begins with “web page” This would show 10 sdk message processing steps, select all and activate these steps. After this root web page will get created successfully.