Introduction: A “shared shift” configuration lets retailers have a single shift across multiple registers, cash drawers, and users. A shared shift has a single starting amount and a single closing amount that are summarized across all cash drawers. Shared shifts are most typical when mobile devices are used. In this scenario, a separate cash drawer isn’t reserved for each register. Instead, all registers can share one cash drawer. Note: Before using shared shift make sure that all the existing shifts at all the POS terminals of the store are closed. Steps: Login with user id at the main MPOS terminal. Open a new shift Now login at all the other terminals of the store Select the option: Resume an Existing Shift Perform Sales and other functions on all the devices End of the day before closingthe shifts Make sure that all the users have logged off from the other terminals except Main MPOS. On the Main POS: Close the shift. Conclusion: Using Shared shift all the transactions done across the store would be captured under one shift. At one particular time only one shift can be shared.

Introduction: In this blog article, we will see how we can fetch Form Control and its value which is of different datatype in EventHandler in D365 Operations Scenario: I am working on Global Address Book functionality for checking Duplicate values for PartyID (String), Tax Id (CheckBox) and Tax Id Type (ComboBox). I am using Event Handler of form method to enable a button based on value of above three fields. Steps: Create Event Handler with below code: [PostHandlerFor(formStr(DirPartyCheckDuplicate), formMethodStr(DirPartyCheckDuplicate, enableSearch))] public static void DirPartyCheckDuplicate_Post_enableSearch(XppPrePostArgs args) { FormRun formRun = args.getThis() as FormRun; FormCheckBoxControl TaxId = formRun.design(0).controlName(“TaxId”) as FormCheckBoxControl; FormStringControl PartyNumber = formRun.design(0).controlName(“DirPartyTable_PartyNumber”) as FormStringControl; FormComboBoxControl TaxIdType = formRun.design(0).controlName(“TaxIdType”) as FormComboBoxControl; FormControl searchBtn = formRun.design(0).controlName(“searchBtn”); if(TaxId.value() || PartyNumber.valueStr() || TaxIdType.valueStr()) { searchBtn.enabled(true); } else { searchBtn.enabled(false); } }

Introduction: In this blog we will discuss how we can solve XML issue while importing solution from one environment to other. Scenario and Steps: 1. Deploying a solution from one environment to other causing issues below issue. This error occurs when there are some integrations enabled for your entity. 2. Click on “Help me resolve this issue” and a Dialog will be opened which shows the specific error. As you can see element “IsMSTeamsIntegrationEnabled” is present in the solution which is not present in target solution. Thus we will remove this element from XML and import the solution. 3. To remove the element from XML follow the below steps: Extract the solution you want to import. Open customizations.xml file. Remove “isMSTeamsIntegartionEnabled” element from XML and save the XML. Zip all the files and import the solution to your environment. Your solution will be imported to the targeted environment.

Introduction: When facing a task of naming a new file, every personnel will name it accordingly what may think is the best. You can organize and manage documents more effectively. Organizations should have a standard naming convention for documents, libraries, lists and pages in SharePoint Online. To improve the user experience for SharePoint, here are few points to consider while naming a document. General Instructions: 1. No Spaces – Spaces on the Internet are “%20”. It is the character encoding for space. So, do not provide spaces while naming any document library, documents, etc. Instead, you can use underscore “_ “or dash “- “in place of a space. 2. Make sure document versioning is turned on so that you can store, track & restore files in SharePoint Online. 3. A name should be meaningful and make sense. 4. Dates – Dates are commonly used for two objects “Articles” and “Documents”. For article place the date in front of the name like “20180911_Article” For documents dates should be placed at the end of the name like “Document_20180911” Date Format – yyyymmdd. 5. Make it short and simple – The file name should be as short as possible without losing its potential to be identified and searched. Longer names take more time to search or read. SharePoint includes file name as well, so the short name will make short URL. We can use abbreviations – Invoice can be “INV”, Quotes can be “QTE” 6. No special character, except “_” & “- “. 7. Data Order (From general to specific) – We can consider using the abbreviation (Point 5) followed by Project and then date. We can also consider adding versions & document id. Example – INV-CloudFronts-20180911.pdf 8. For Site Pages – It is not a best practice to name pages with a “_” or space. Instead, it is recommended using “-“. Example (This-is-a-site-page). 9. Many organizations like to prefer placing versions numbers in a document name. Place the version at the end of the file name. Use dash “- “to separate major versions and minor versions or drafts. Example (Document_V01-01.docx). Here, V01 is the major version and “-01” is the minor version. 10. Do not change the name of Lists & Libraries. Conclusion: A simple naming convention is a best way to avoid naming related issues or accidental overwrites which affect end users’ experience. Though it varies from company to company, but each organisation should have a standard naming convention.

Introduction: This blog is to give an introduction regarding how to integrate the data from Business Central to an API and also gives a comparison of the API integration in Business Central on-premise and Business Central on Cloud. I will demonstrate it with an example for Sales Order Entity. Pre-requisites: 1. Microsoft Dynamics 365 Business Central (on-premise) 2. Microsoft Dynamics 365 Business Central (Cloud) Demonstration: For Business Central on-premise: 1. Add the page whose data has to be integrated to the page API Setup (5469) and click on Integrate APIs. 2. Go to Business Central Administration and to the Server Instance properties and in the OData properties check the “Max Page Size” parameter and set it to the number of records you want to integrate. (Note: Enable API Services and Enable OData Services checkboxes should also be ticked.) 3. Now go to the browser and enter the URL to get the list of 44 standard APIs. (Format of the URL for Business Central on-premise is given as follows:    “http:<<Server Name>>:<<Odata Port>>/<<Service Name>>/api/beta/” 4. Now you can get to the sales order using the following URL. “http:<<Server Name>>:<<Odata Port>>/<<Service Name>>/api/beta/companies(company id)/salesOrders”. This data is available in JSON format and further can be confirmed that there are 1500 records. Thus, the number of records integrated here depends on the Max Page Size parameter. For Business Central on Cloud : 1. First add the page whose data has to be integrated is added to the API Setup Page similar as above. Use the following URL “https://api.businesscentral.dynamics.com/v1.0/<tenant domain>/api/beta to access the API for getting the data from the Business Central on Cloud. Enter the username of the user in the Business Central and the Password will be the user’s WebServiceAccessKey. 2. When you click on Sign in, you will get a list of all of the standard 44 APIs. 3. Similar to the Business Central on-premise you can navigate to the SalesOrder. URL Format is as follows:    “https://api.businesscentral.dynamics.com/v1.0/<tenantdomain>/api/beta/companies(company id)/salesOrders”. It can be seen from the images below that only 1000 records have been integrated from the SalesOrder in Business Central to the API. Here, as there is no administration this number of records integrated cannot be changed and they remain as the standard defined for OData. Conclusion: This is the difference in the API integration in Business Central on-premise and Business Central on Cloud. It also shows the number of records that can be integrated in Business Central on-premise and Business Central on Cloud. As we will find the solution as to how to alter the number of records that can be integrated in Business Central on Cloud we will post the blog.

Problem Statement: D365 Sales on CRM in general has ability to revise Quotes to track the Quotes revision. In sales, the process was to Activate the Quote, and then you get option to Revise Quote which will create the Copy of Quote with new revision number in Draft state. In Project Service quotes, we don’t see the option to Activate Quote or Revise Quote. Solution: Steps to Revise Quote in Project Service Quotes. Close the Quote as Lost using the button – “Close as Lost” Then you can see the button – “Revise Quote” This action will revise the quote with new Revision Number.

Introduction: If Stocked product checkbox is selected, then inventory transaction will be generated, and product inventory will be tracked. If this checkbox is not selected(Mainly for service items), then Inventory transaction will be not generated, and product inventory will be not tracked. Scenario 1: If Stoked Product Checkbox is not selected Posted purchase invoice for product for which stock product checkbox was unchecked. Inventory transaction has not been generated. This setting mainly uses for service type of products. Scenario 2: If Stoked Product Checkbox is selected Posted purchase invoice for product for which stock product checkbox was checked. Inventory transaction has been generated. This setting mainly uses for those products for which you want to track the inventory. Conclusion: This functionality is helpful to take decision for the product for which you want to track the inventory, or you want to book directly as an expense for service item without tracking inventory.

Introduction: Controller class is used to control the report execution as well as pre processing of the report data. The SSRS reporting framework uses this class to modify the report dialog, calling the SQL Server reporting services, as well pre processing parameters for the report. How to do? Create a new class. Open AOT –> Classes Open the class declaration and select on View Code Now write the following code: class SSRSDemoController extends SrsReportRunController { } Create a new method and write the following code: public static client void main(Args args) { //define the new object for controller class SSRSDemoController ssrsDemoController; ssrsDemoController = new SSRSDemoController(); //pass the caller args to the controller ssrsDemoController.parmArgs(args); //set the report name and report design to run ssrsDemoController.parmReportName(ssrsReportStr(SSRSSessionQuery,Design)); //execute the report ssrsDemoController.startOperation(); } Conclusion: Reports that are opened from a form – Controller class is also used when reports are opened fro a form and are needed to show selected records details. Use preRunModifyContract method to achieve this.

Dynamics 365 application development provides an end-to-end solution for your business right from design, development, appsource listing upto enhancements and support. The team has a set of expert developers, architects and technicians who are involved 24*7 in the process to enhance your business and take it to the next level. The team understands your business needs initially and then starts working on the goals for the betterment of your business. Based on the case scenarios, applications are designed and developed that could be easily fitted and implemented on to your business model. While Dynamics 365 is taking care of your business needs through cloud, you can focus on your core business strategies, needs and allocate time to your clients making a better relationship with them for enhanced business. Introduction: In this blog we will discuss how we can add entities to the by default App for Outlook look while we track emails using App for Outlook. Steps: By default, the App for Outlook does not show any entities in its sitemap. As we all know that there is new concept of Apps in MSCRM. We can develop Apps so that we can give users a limited and required access to entities. Every module in CRM is now a app like Field Service App, Project Service App, Service App. Similarly there is App for Outlook App. Below is the default sitemap for App for Outlook. You can add Area, Sub area and groups to the default sitemap and publish the changes. Below is the screenshot after addition of required area, sub areas and groups. This is how you can change the entities visible in D365 App for outlook.

Overview: I had a requirement where I needed to make certain fields on BPF as required. So, I tried accessing the control using Xrm.Page.getControl(“header_process_description”) and then getAttribute().setRequiredLevel(“required”) on it would serve my purpose. But actually, not! To set perspective, the code runs and make the field required too. But there’s a catch! Required fields on the BPF are supposed to throw an error when you are trying to move to the next stage without filling in the required fields. But, using the code I’m talking about above (sample shown below), will force you to save the form entirely. Let alone moving the stages further. That when ‘How Did You Hear About Us?’ field has Employee Referral as value, make Purchase Process field required. Field is on the BPF But asks you to save on the form Workaround: The easiest workaround to this is using the conditional branching of your business process flow – You can use conditional branching of the BPF itself – You can replicate the same stage twice, one having your required field and other having that same field as optional However, limitations I found with this approach is – I couldn’t use the same for the first stage of the BPF The condition had to be from the previous stage itself   P.S.: Business Rules isn’t a solution as well. Also, I tried to inverse the logic by first making the field required in the BPF itself and then trying to make it not required using code. That doesn’t work either.