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.!

At times you will get an error while creating positions for employees such as this: The assignment end date must not be earlier than the assignment start date Here even if you put an Assignment end date you wont be able to create a position because the actual error is on the below form. Once you make changes to it and add date to available for assignment field, you will be able to create a position successfully Hope this helps !

In my previous blog referred here https://d365feeds.com/2020/07/08/how-do-contract-milestones-and-projects-flow-between-d365-ce-to-fo-in-project-operations/, we saw how the contract and milestones flow between CE and F&O in the integrated scenario in Project Operations. Next step is to Post the Milestones or the Approved Time entries (in case of T&M based projects) in F&O (Finance and Operations) Let’s looks at first Milestone based Invoice posting in F&O for a Fixed Bid Project: PN: How to log in to the environment is shown in my previous blog in the link above. Step 1: Login to the CE Environment to the Milestone that you need to Invoice and flip the status to “Ready for invoicing”. Step 2: The invoice is created in the CE Environment and you need to confirm the same. Upon confirming the invoice it gets integrated to the F&O Environment. Step 3: Navigate to F&O Environment and go to Project Management and Accounting à Import from staging table. This will import all the transactions available in the staging area to F&O environment. Step 4: At this juncture the Invoice is now posted to the F&O Environment. To check the same in F&O environment navigate to Project Management and Accounting Module à Pending project transactions You can see the Invoices milestone below. Step 5: Select the invoice and click on Post. This is when the invoicing of milestone is completed. This step is recommended to be performed by the Accounts Manager. Now we shall see how to Invoice Time and Material projects. Follow the steps to accomplish the same. Step 1: Navigate to CE Environment and get some time entries done on the T&M project as shown below. Step 2: Submit the time entries done by clicking the Submit button as shown below. The status of the time entries changes to Submitted from Draft status. Step 3: The project manager will now have to approve the time entries submitted from the Approvals tab. Step 4: As soon as the time entries are approved they are integrated and reside in the staging area of F&O. You then need to Import all the time entries from the staging area. Navigate to F&O Environment and go to Project Management and Accounting à Import from staging table. This will import all the transactions available in the staging area to F&O environment. Step 5: Post that navigate to Project Management and Accounting à Project Operation integration journal where all the approved time entries in CE environment get collected. Please understand that if there is an active Journal existing in F&O environment, then all the approved time entries for all the projects will be integrated to the same Journal, unless all the entries in that integration journal is approved. Step 6: Select the Journal from the below and click on the Post button from Ribbon. This will post all the transactions from the Journal, which also the final step that the Accounts manager will perform to do the invoicing. Above methods when performed can ensure that the milestones and the time entries for FP and T&M projects respectively are done. The above operations are prescribed to be done by the Accounts Manager in the company. This ends the process of Posting the Invoice in F&O Environment. The above blog is written with the best possible knowledge of Project Operations and practical experience.

In this blog, I am going to explain how to send a notification on Microsoft Teams when a record is created or Updated or Deleted in D365 CRM using Power Automate Steps involved in Power Automate: Select trigger, in my case I used CDS connector when a record is created, updated or deleted. Select trigger condition, in my case I used Update. Select entity name, in my case I used Opportunities. Select Scope, Organization. Add new step to flow. Search Microsoft Teams and select Post a message. Select Team where you want to post a message. Select Channel from team where you want to send a notification. Enter Message in message box. Click Save and check teams. Congratulations! You have successfully created the required flow. Hope this helps!!

 In D365 Finance and SCM there are lot of out of the box SSRS reports in which you have hyperlink to move to that particular record (for example Ledger transaction list). But sometimes when you update environment you might end up with no such option in you SSRS report as you can see in following screenshot.  To enable hyperlink features you need to follow following steps:- Navigate to feature management and go to all section in that Search for Report drill through links and disable this feature Search for Report PDF viewer and disable     you need to disable this feature for following limitation which you can find in screenshot. Now check desired SSRS reportNow you are able to see hyperlinks links in the reports I hope this post will be helpful to you, Thank you!

Many times, we feel like why I can’t access D365 CRM Database directly from MS SQL Server, so here is my blog that will guide you on how you can connect D365 CRM CDS Database using MS SQL Server Steps to enable D365 CRM CDS Database to make it connect from MS SQL Server: Login to https://admin.powerplatform.microsoft.com/ using administrator credentials. In Environment section, click on your environment for which you want to enable D365 CRM CDS for MS SQL Server. (In my case I am clicking on DemoEnvironment as shown below.) When Environment opens click on settings in header. Settings page will open, Click on Product and then click on Features. When features Page opens enable TDS Endpoint (Preview) and click save. Now, we have successfully enabled D365 CRM CDS to connect it from MS SQL Server. Steps to Connect CDS Database from MS SQL Server: Open MS SQL Server. In connect to SQL Server Window enter Server name (It will be your D365 CRM URL) followed by comma and Port Number (5558) e.g. of server name yourdomain.crm.dynamics.com,5558. Select Authentication as Azure Active Directory – Password. Enter Username: Your admin user id e.g. admin@xyz.com Enter Password: (Your Login password) ******** Click Connect. Now, you have successfully connected to D365 CRM DB. Write a select query and test if it’s working.

One of the issues with Dynamics 365 Retail is the way the errors are displayed to end users. I have come across many instances where it becomes very difficult to investigate and get to the root cause of an error message. The lack of clarity becomes an issue when you are not very familiar with the functional/technical aspects of HQ and POS. One of the many common errors I have seen is server side and database related issue as you can see in the below screen grab. Here the issue is with the loyalty card setup in payment methods. However the error message is not very clear in terms of where exactly the issue is. I have seen similar error once when there was an issue with printing the receipt. The issue was with the design itself. When we redesigned the receipts while adhering to proper layout the error went away. Hope this helps!

Introduction: Shortcuts are used to place child nodes(child links) throughout the portal’s sitemap(navigation) which simply points to other nodes that exist in your sitemap, or to URLs external to your portal. Use Case: We have two parent pages- “Hardware” and “Support”.  Both are child pages of another page- “Home”.  “Support” page has a child page named- “Support Create”.  Let’s say we want to add the “Support Create” child page under “Hardware” in the Sitemap(navigation). Steps to create a shortcut Go to the “Portal Management” app. Go to Shortcuts Click on “+New” to create new record Enter following details on the form Attribute Details: Name: Name for the shortcut. For internal use only. Website: The website that the shortcut belongs to. Parent Page: The parent webpage of the shortcut entity in the sitemap. The shortcut will be added to the sitemap as a child of this page. External URL: URL outside of your organization. Web Page: internal webpage of the portal Web File: web file of the portal Title: The title for the shortcut. This is the name that will appear in the sitemap and child navigation view areas. If left blank, the title (or name) of the target entity will be shown instead. After adding all the details save the record Navigate to the portal to see changes you should see new child node named “Raise Support” under “Hardware” If you click on “Raise Support” it will redirect you to the “Create New Support” page NOTE: A shortcut can only have value in one of the ‘Target’ fields (External URL, Web Page, Web File). If more than one target attribute exists for a shortcut, the shortcut will just take the first one, ignoring all others.  Reference Article: https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/place-child-nodes

INTRODUCTION: In this blog I would like to share few functional features which are planned for Business Central Wave 2 2020. Also, in this blog I will be sharing some insights into the planned features. Business Central Company Hub extension: Accountant Hub is deprecated to Company Hub in this release wave. Company Hub contains the same features, and Microsoft recommends using Company Hub as a replacement for Accountant Hub. More details here: https://www.olisterr.tech/2020/07/announcement-microsoft-dynamics.html Group VAT reporting: Ease and support for seamless VAT group reporting which will smoothen VAT liability on intra-group entities and optimizing the tax filing. Default unit cost for non-inventory items: Now users will get the default feature of updating cost on Nonstock or catalog items and service items, as these costs impacts production, assembly and sales transactions. Track packages from more types of sales documents: Now users will be able to reverse the posted bank reconciliations. The bank reconciliation will automate the reconciliation of differences. The Payment Reconciliation journal will support application against employee ledger entries, allow one-to-many matching, have preview posting enabled, separate number series, and user-defined document numbers. Bank reconciliation improvements: Now users will be able to reverse the posted bank reconciliations. The bank reconciliation will automate the reconciliation of differences. The Payment Reconciliation journal will support application against employee ledger entries, allow one-to-many matching, have preview posting enabled, separate number series, and user-defined document numbers. Consolidation file format support for Dynamics 365 Finance: The file format options for a business unit in Business Central will include an option for Finance and Operations. Notify users of high-risk changes in selected setup fields: Notification enabled for any change in the value of highly critical field using change log functionality. Use conversion templates to convert contacts to vendors and employees: User can now convert a contact a vendor or an employee. Contact conversion template can be used using conversion. Use recurring journals to allocate balances by dimension values: In recurring general journal using recurring method ‘Balance’ or ‘Reversing balance’ users can now allocate cost of source GL account dimension-wise, earlier only consolidate cost was possible. Use the Copy Journal function on general journals and G/L registers when reversing entries: Copy Journal functionality will be made available to copy the general journal batch with opposite signs (a reversing journal) and different posting date & document number. Use Word document layouts to customize outgoing customer documents: Users can now export document layout to work for the following documents: Shipments, Return Orders, Service Quotes, Orders, Invoices, and Credit Memos. Simply modify the layouts and import them back into Business Central to use next time you send, for example, a shipment, return order, or a service document. Use contact Mobile Phone Number and Email consistently across application: User can now use the Mobile Phone Number and Email fields on data entry pages, report data sets, report layouts, and segment lines that have contact details in Business Central. CONCLUSION: Once there is a public preview/ general availability is released then I will create a follow up blog explaining each feature in detail. Kindly feel free to suggest. Hope this helps!