Item Master Data Mass uploading via Data Management In the world of data management, it has become essential that the business users are provided solution for mass data uploading. Where the data is managed by very less expert users who’re required to upload and download data in bulk at very less given time. Today I am going to show you the way to upload Item Master Data quickly and with no errors via Data Management in MS Dynamics Commerce and Retail. Note: Masters as Item group, tax codes, units, category, item model group etc should be pre-configured or created for this to work accurately otherwise this operation will fail with errors as the masters are not created/configured. For this operation to work first we need to identify the fields that are required to do two steps. First, Item Master Creation Secondly, Item Master release in released products. So now to identify the necessary “importable” fields first we will export the required fields in excel as below. Goto Workspaces> Data Management and in Data Management click Export Button. Upon Clicking “export” create project as data filled in below. Desired Project name in my case I have named it “product master fields” Generate Data package to be set as No. Now when project is created click on “add entity” Select entity as “Released product creation V2” or anything as “Released product creation” whichever is latest according to your version of D365. Select output as “EXCEL”. Use sample file and skip staging to be set as NO. Very important step to select fields to be set as “Importable Fields” And “add” the entity to the project. Now again click on “add Entity”, select the rest of the fields as mentioned in pt. II., and select “released products V2) in entity name and click on add. Now click on export button as below Now on export screen Click on “refresh” button until you see  mark on thee screen, and then “download File” to obtain excel file. Note: click each project one by one to download table fields. After downloading file replace the data with required information that you want in your product master so that we can Import the Master data. (Note: You can hide fields that doesn’t require user to input any data but are required by AX this you will identify in released products format). Assuming that you have created your files for upload we will now continue with “Import” data, Goto Workspaces > Data Management and in Data Management click “Import” Button. Upon clicking “Import” create a project and add entity as below. Add group name, in my case added as “import Master Data” Now when project is created click on “add File” Select entity as “Released product creation V2” or anything as “Released product creation” whichever is latest according to your version of D365. Click the upload data file and select the appropriate file, in my case it is “Released product creation V2 – Format.xlsx” Select “Source data format” Click close. Now again click on “add File”, select the rest of the fields as mentioned in pt. VIII., and select “released products V2) in entity name and click on Close. After adding both the files, now its time to click on “import”, but first ensure that the sequence of the below files are as such 1st for Released Product Creation and 2nd for Released products. If this is not in sequence the above operation will fail. After Clicking on Import, you will have to click on refresh button until the  come. Upon success you can see the validation message that the master data has been uploaded successfully and released the product for use. In my case I had uploaded a test product which got successfully uploaded to the system. Hope this helps!

At times you may come across issues such as database related error while trying to earn or redeem loyalty points. The way I was able to resolve it by restarting the IIS services from the life cycle services(Sandbox environment). You may need to do a full sync of retail jobs as well. In the production environment you may not have access to restart the IIS service. You may need to raise a Microsoft Support Ticket to resolve this. Before you try the above, please ensure that loyalty programs, tiers, rules are properly defined in back end HQ. Hope this helps!

User property disableMru = true; You can refer below code       selectProjectLayout: () => {         var lookupOptions = {}; var _projectLayoutName = null; var customFilter = ‘<filter type=”and”>’ + ‘<condition attribute=”cf_project” operator=”eq” value=”‘ + Operations.selectedProjectId + ‘”/>’ + ‘</filter>’; lookupOptions.allowMultiSelect = false; lookupOptions.defaultEntityType = “cf_tcmaplayout”; lookupOptions.entityTypes = [“cf_tcmaplayout”];         lookupOptions.disableMru = true;// used to hide recent items try { if (Operations.selectedProjectId !== null) { lookupOptions.filters = [{ filterXml: customFilter }]; Xrm.Utility.lookupObjects(lookupOptions).then( function (result) { if (result !== undefined && result.length > 0) { // your code } } }, function (error) { if (error != null) { Xrm.Utility.alertDialog(error.message); } } ); } } catch (e) { Xrm.Utility.alertDialog(e.message); } }

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.