Use case – Our requirement is to mark field Purchase time Frame disabled in Business process flow on change of disable field(custom field) on opportunity form. Let’s see how we can achieve this Solution – Step 1 – Create web resource with below function- Add header_process before schema name of field. Here schema name of purchase time frame field is purchasetimeframe. And after adding header_process_purchasetimeframe var opportunityCustomization = {     //opportunityCustomization.disableField     disableField : function(executionContext)     {         var formContext = executionContext.getFormContext();         var disable = formContext.getAttribute(“cf_disable”).getValue();         if (disable == true)         {             formContext.getControl(“header_process_purchasetimeframe”).setDisabled(true);         }     } } Step 2: Add this web resource on form load, on Save and on change of the field. And try Output – Hope this helps !

In this blog, I am going to showcase how to resolve the error while printing the X/Z report from POS. In the store, go to payment methods. Select the tender Remove/ Float payment method. The payment method configuration for “Tender remove/float” was incorrect. If you don’t want to have the same problem be sure to unmark all the “tender declaration options” at this payment method. If you need to unmark after saving it you need to do it at RetailStoreTenderTypeTable.counting required there will be a record per payment method per store, so update as many as you need. After performing these steps, run Full sync from Channel Database. Refresh the POS link. You will able to see the start amount in both X/Z report. Hope this helps!

In this blog, I am going to showcase how to resolve the error while returning invoice orders in Retail POS. When a customer will come to the shop and want to return the order which already invoices then getting following error on the POS This error was occurred because the return reason code setup is missing. Steps to Configure Return reason code. Set up return reason code groups Go to Sales and marketing > Setup > Sales orders > Returns > Return reason code groups. Select New to create a line for a new return reason code group. In the Return reason code group field, type an identifier for this group. In the Description field, type a brief phrase to explain how this group will be used. Set up return reason codes This procedure helps you set up return reason codes that you can use to indicate why a product was returned by the customer. Go to Sales and marketing > Setup > Sales orders > Returns > Return reason codes. Press CTRL + N to create a new return reason code line. In the Return reason code field, enter text to identify this code. In the Description field, enter text to describe the return reason code. Use the Return reason code group drop-down list to add the code to a return reason code group. Once all setup complete. Run 1030, 1070, 1090, and 1110 and refresh the POS link. Now you will get the below info code to enter the reason for the return and you will successfully return the invoice order. hope this helps!

As of now as a POS user if you want to check the inventory of an Item , you will need to click on the inventory lookup button on homepage and you will have to then enter the item number to display a list of store wise inventory. While this feature is useful, there is a need to check inventory directly from the cart itself. Microsoft has finally made this feature available. However, this will be available from 10.0.19 release. Once this feature becomes operational, you will need to add an ‘Inventory lookup’ button to the button grid. After adding a line to the cart you can select the any line and then click on inventory lookup button to check the stock for that particular item. If you select no lines and click on the inventory look up button you will see an empty form Hope this helps!

This particular error ‘A database error has occurred’ took a very long time to resolve for us as neither us or Microsoft were able to figure out what was causing it. We verified and double checked following to resolve the issue but to no avail. I suggest you to first ensure the below things before you escalate it to Microsoft support team. Validate the created products Make sure product has category assigned. Ensure product is added to store assortment and assortment is published Process the assortment and all the jobs are in applied state If the issue still persists, then its possible the issue is with scheduler sub jobs. Check the InventTable. There should be 1040 job in the scheduled by Tab If its missing then go to 1040 jobs and then scheduler jobs and add Inventtable to it. Hope this helps!

In Retail store you will need to assign address books i.e. One for store staff/employees and the second one for customers. If you fail  to do that then on POS you will not be able to login or see/search for customers The above setup is the ideal for the store to function properly. However, some employees you want to create as customers too. You can do this manually or you can keep it automatic. The meaning of automatics is, you will be able to search for store employees on POS and as soon as you click on their names, a customer with the same employee name will be created in the system. To do this automatically on POS the below setup is required. As you can see ‘Houston’ address book is common in the store Customer address book and Employee address book As a result of this setup, whenever you search for any employee on POS and select it, it will be created as customer in the system. Here, I have searched for Eric who is an employee and his customer ID field is blank as he is an employee. As soon as I click on it, it will create the customer in the system. Hope this helps!

Loyalty programs can help increase customer loyalty by rewarding customers for their interactions with the retailer’s brand. In Dynamics 365 Commerce, you can set up simple or complex loyalty programs that apply across your legal entities in any commerce channel.  You can set up your loyalty program in many ways so that it includes options such as: multiple types of rewards, incentives, earning rules, manual point adjustment. Some customers will also require to setup multiple loyalty cards for every customers. For example as you can see Stuart has 2 loyalty cards associated with his account. The provision to allow customers to have multiple cards is a useful feature but it makes the loyalty card process a bit complex. Complex in a way that loyalty card will not be selected by default hence cashiers will need to be careful and choose a loyalty card during every transaction. If you do not select a loyalty card, then points will not be earned for the customer while making a purchase. To avoid this from happening, what cashier can do is always search for the customers with their loyalty card numbers. This way the loyalty card would be selected automatically while customer is making a purchase. However if the customer does not have the card number handy then the cashier will need to select a loyalty card I hope this helps!

D365 gives us a functionality to assign a record to a group of users which can be archived by using a D365 Team these users then are know as members of that respective team, due to functionality restrictions we cannot send an email to a  D365 team, however there are a few workarounds by which we can achieve this functionality. Lets consider a case. Suppose we have a D365 team called as “Accounts Associates” we have added a set of users in this team. Now if an invoice milestone is in the ready state i.e. “Ready For Invoicing” we need to send a reminder email to this “Accounts Associates” team to take an action regarding the ready invoicing. Solution :- The following case can be achieved by using an Out of the box functionality i.e. By using a distribution list Note :- (we must have an Microsoft Exchange License). Lets Begin with the implementation. Step – 1 Creating a Distribution List Login to your admin center (Link –https://admin.microsoft.com/) In the Admin center  Section of the  Left navigation bar select “Exchange”. Under the “recipients” select “groups”. In the “+ New Microsoft 365 Group” pull down the dropdown and add the distribution list. Add the Display name and the “Alias” and save the Distribution list. Add same users which are present in the teams to this Distribution list. Step – 2 Creating a Queue in D365 Go to “Settings” -> “Service Management” ->” Queues” and click on “+NEW” -> give it a name -> “Save”  A mailbox would be created with the same name that of the queue.   Open the mailbox. The Email address field will be blank, add the Distribution List’s email address created in Step 1.    Step -3 Create a New Team or select an Existing Team. In the Default Queue lookup, select the Queue created in Step 2. Step – 4 Create a Flow which triggers on update of a project contract line milestone i.e. When status is ready for invoicing Flow triggers when Project Contract Line is Updated, Condition Invoice Milestone is Ready for invoicing for which click on the “…” select settings and add the following condition in the trigger sectio Get the Teams ID in this case I have hardcoded the ID as no record was associated with it to retrieve it Get the Teams Details. Get the Default Queue to which the email will be triggered . Send an Email to the Incoming Email of that Queue which is Email ID set on the Distribution list. Note : (We will have to Manually add or remove the users from both the Distribution list and the Teams. i.e. both the team and the distribution list must be sync, if a member is added or removed from the team the same should be done in the distribution list ) Output . Hope this helps.!

D365 gives us a functionality to assign a record to a group of users which can be archived by using a D365 Team these users then are know as members of that respective team, due to functionality restrictions we cannot send an email to a  D365 team, however there are a few workarounds by which we can achieve this functionality. Lets consider a very case. Suppose we have a D365 team called as “Accounts Associates” we have added a set of users in this team. Now if an invoice milestone is in the ready state i.e. “Ready For Invoicing” we need to send a reminder email to this “Accounts Associates” team to take an action regarding the ready invoicing. Solution :- The following case can be achieved by using an Out of the box functionality i.e. By using a distribution list Note :- (we must have an Microsoft Exchange License). Lets Begin with the implementation. Step – 1 Creating a Distribution List Login to your admin center (Link –https://admin.microsoft.com/) In the Admin center  Section of the  Left navigation bar select “Exchange”. Under the “recipients” select “groups”. In the “+ New Microsoft 365 Group” pull down the dropdown and add the distribution list. Add the Display name and the “Alias” and save the Distribution list. Add same users which are present in the teams to this Distribution list. Step – 2 Creating a Queue in D365 Go to “Settings” -> “Service Management” ->” Queues” and click on “+NEW” -> give it a name -> “Save”  A mailbox would be created with the same name that of the queue.   Open the mailbox. The Email address field will be blank, add the Distribution List’s email address created in Step 1.    Step -3 Create a New Team or select an Existing Team. In the Default Queue lookup, select the Queue created in Step 2. Step – 4 Create a Flow which triggers on update of a project contract line milestone i.e. When status is ready for invoicing Flow triggers when Project Contract Line is Updated, Condition Invoice Milestone is Ready for invoicing for which click on the “…” select settings and add the following condition in the trigger section. Get the Teams ID in this case I have hardcoded the ID as no record was associated with it to retrieve it Get the Teams Details. Get the Default Queue to which the email will be triggered . Send an Email to the Incoming Email of that Queue which is Email ID set on the Distribution list. Note : (We will have to Manually add or remove the users from both the Distribution list and the Teams. i.e. both the team and the distribution list must be sync, if a member is added or removed from the team the same should be done in the distribution list ) Output . Hope this helps.!

D365 gives us a functionality to assign a record to a group of users which can be archived by using a D365 Team these users then are know as members of that respective team, due to functionality restrictions we cannot send an email to a  D365 team, however there are a few workarounds by which we can achieve this functionality. Lets consider a very case.Suppose we have a D365 team called as “Accounts Associates” we have added a set of users in this team. Now if an invoice milestone is in the ready state i.e. “Ready For Invoicing” we need to send a reminder email to this “Accounts Associates” team to take an action regarding the ready invoicing Solution :- The following case can be achieved by Looping through all the users in of a D365 Team.Lets Begin with the Implementation. Step 1 – Create a D365 Team.Go to Security – > Teams -> Create a new team. Step 2 – Create a Flow to send email.1. Flow triggers when Project Contract Line is Updated, Condition Invoice Milestone is Ready for invoicing for which click on the “…” select settings and add the following condition in the trigger section. 2.Get the Teams ID in this case I have hardcoded the ID as no record was associated with it to retrieve it3.Get the Teams Details.4.Get the User Details by using the following fetch XML Query. 5. Query :<fetch version=”1.0″ output-format=”xml-platform” mapping=”logical” distinct=”true”>   <entity name=”systemuser”>     <attribute name=”fullname” />     <attribute name=”businessunitid” />     <attribute name=”title” />     <attribute name=”address1_telephone1″ />     <attribute name=”positionid” />     <attribute name=”systemuserid” />     <attribute name=”internalemailaddress” />     <order attribute=”fullname” descending=”false” />     <filter type=”and”>       <condition attribute=”internalemailaddress” operator=”not-null” />     </filter>     <link-entity name=”teammembership” from=”systemuserid” to=”systemuserid” visible=”false” intersect=”true”>       <link-entity name=”team” from=”teamid” to=”teamid” alias=”ag”>         <filter type=”and”>           <condition attribute=”teamid” operator=”eq”  uitype=”team” value=”{Your Team ID}” />         </filter>       </link-entity>     </link-entity>   </entity> </fetch> For all the users Send an Email individually to the user OutputUser 1. Which is CRM Admin in my case in the team. User 2 Vidit Gholam system Administrator Hope that helps. !