Introduction: In this blog we will explore some of the new features added to Power BI. Power BI has upgraded its Q&A Experience in its latest April release. It has simplified and simultaneously improved the natural language recognition process which is one of Power BI’s most powerful tools for Query Processing! Some of Q&A Explorers cool new Features: You can now add a simple image, shape or button which on being click can launch a Q&A Explorer! You just need to toggle the Q&A option on under Action for the particular image/shape/button. Adding a Q&A button can look something like this. On clicking on this newly created Q&A Explorer a dialog appears where the user can ask questions to generate dynamic visuals. To learn more about this feature you can view my previous blog on Natural Language Processing over here. You can add suggested questions which will show on the left side of the dialog when a user clicks on the Q&A button. When you click on Save and close these newly added Suggested Questions will get saved to this specific Q&A button. The Q&A Explorer can also return whole reports now when you search specific keywords. You can do this by going to a particular report and turning it’s Q&A Feature on in Page Information. Searching these keywords in the Q&A Explorer will return this particular report. Optionally, if you have page level filters then you can set Require single selection On for a particular filter. This filter will then be shown in the Dialog while searching for the queried report. Conclusion: These are some of the latest features added to Power BI’s arsenal. Q&A Explorer is an underused tool but if used correctly it can improve your interactive experience with your reports tremendously.

Introduction: Field Service in PSA uses Incident Types. Incident Types can be defined to showcase what are the most common scenarios for field works on a particular Work Order. Having generic tasks, skillsets defined for an Incident Type saves the effort to re-enter the iterative information on a WO. Setting Up Incident Types: Field Service Incident Types can be defined in FS Administration area as shown below: Assuming I’m a branded furniture reseller, most common tasks for my technicians on field is assembling wooden furniture like Beds, Cupboards, Tables etc. So, I’ll create a generic Incident Type called as Furniture Assembly. What all to enter in Incident Types 1. Incident Types has first important section called as Characteristics. Meaning, any resource with that Skillset is required to be performing this WO. In my example, I want the carpenter to be Proficient in using Sawing and Drilling. 2. Next, is the Details In this section, Estimated Duration is automatically calculated based on the Service Tasks (point no. 3 below) to be performed by the resource and what should be the Default Work Order type. Note: Once when Default Work Order Type is selected, if you select the Primary Incident Type on the WO, the Work Order Type is automatically picked in the Work Order you are creating. 3. Service Tasks is the next section where you can list what common tasks should be performed by the resource on field. With the Estimated Duration entered, they drive the Estimated Duration on the Incident Type itself. 4. Products section is next where you can enter the Products that will be used by the field service agent in order to perform their required task. Products can be Inventory, Non-Inventory depending on their use. 5. Services are what field service agents will provide to the customers and might charge for it. Products of type Services can be entered here. Adding Details to the Work Order: Once your Incident Types are set up, you can use them in your WO and get all the data in the WO itself! You can choose to override any data from it if you want. Create a WO and fill out the common details. Then, select the Primary Incident Type as the one you selected. And when you select it, you’ll see the WO type has been automatically populated. And once you save, details from the WO like the Characteristics, Incidents, Service Tasks, Services and Products have been auto-populated. This makes things a lot easier!

Starting from sales until delivery, Microsoft Dynamics 365 offers successful deployment of various business processes. The partners of Microsoft Dynamics 365 list the apps in the app source developed for a specific business need or for a particular business vertical hence showing their expertise. The dynamics 365 application development team has experts who are specialized in developing sophisticated business apps for their partners. The entire lifecycle of the business is supported through Microsoft Dynamics 365 right from developing the apps to listing them in the AppSource and giving support which lets you focus on the core business strategies instead of things which are less important. The qualified team of experts understand your requirements initially and then further work on improving each and every aspect of your business Introduction: This blog explains how to Filter records in PowerApps based on the current user of Dynamics CRM. Steps to be followed: Step 1: Add user entity. For that go to View –> Data sources –> Select Dynamics 365 connection. Select user entity –> click on connect. Step 2:  Now select Browse Screen and add Label control on Browse screen. Set its visible property to false. Set Text property to: LookUp(Users,internalemailaddress=User().Email,systemuserid) Step 3:  Select Browse Gallery and set its Items Property to : Search(Filter(Cases,_ownerid_value = Label1.Text), TextSearchBox1.Text, “description”) (Here Label1 is the name of Label which we have added in previous step && _ownerid_value stores the owner of that particular case record) I have selected _ownerid_values because owner field stores the user value according to which we want to filter the case records. By following above steps you will be able to filter records based on current user.

Introduction: In the blog we will be discussing about the error while connecting to Dynamics 365 version 9 using console app. Implementation: In our example we will show how to connect to Dynamics 365 using a Console app in v 8.2 and when the same code is used to connect to version 9 we get an error. We will also discuss about how to resolve the issue Step 1:  The code show below is used to connect to Dynamics 365 version 8.2 using Console App. Step 2: When we run the above code, we get the following output. Step 3: Now we change the credentials and try connecting to Dynamics 365 v 9 with the same code, we get the following error. Step 4: To solve this issue there are two ways, in the first method, set the Target framework to “.NET Framework 4.6.2 or above”. Step 5: After changing the target version build the solution again and run the app.The connection to Dynamics 365 version 9 environment will be successful. Step 6: The second method is by using the below code before making a connection. TLS stands for “Transport Layer Security,” and is a protocol that is an industry standard designed to protect the privacy of information communicated over the Internet.

Introduction: In this article, we will learn how the Filter changes its default values during Parameter selection in SSRS Reports with Examples. Scenario: I have 4 parameters in my report: Start Date: Default is today’s Date End Date: Default is today’s Date + 60 Days Department: No Default value. Project: Dependent Filter on Department. Once the Department is selected, default all projects will be selected. Filter Working: Below listed is various test cases which shows how the Select ALL in Project Filter changes according to other 3 parameters. Default Filter: Start Date: Current Week Start Date End Date: Today’s Date+ 60 days Department: Select all manually Project: Disabled Results: All projects will be automatically displayed and selected based on dates and Department. Selecting wide range of Dates after Initial run (After Step 1): Start Date: less than Current Week Start Date or Current Week Start Date End Date: Greater than Today’s Date+ 60 days Department: Select one manually Project: Not all the Projects will be selectedResults: All projects between the date range will be displayed but the projects after today’s date + 60 will be un-selected. Selecting more Department (After Step 2): Start Date: Any End Date: Any Department: Select two department Project: Not all the Projects will be selected Result: All projects between the date range and department will be displayed but the projects in newly selected department will be un-selected. In this example, projects in Assurance Department will not be selected. Conclusion: Dependent filter (Project Filter) will be disabled initially. Dependent Filter will be displayed and open once all the other filters are selected. Dependent Filter will change based on the other Filters change. After initial run, any change in other filter will control the behavior of Dependent Filter. Selecting Wide Range initially and then reducing the Range will keep the Dependent Filter as Select All. E.g.: Decreasing the Date Range or Selecting less number of department selected initially. Selecting a range initially and then increasing the range will remove Select All in Dependent Filter (Only the initial range Project will be selected). This the default SSRS behavior. E.g. Increasing the Date Range or Selecting more departments selected initially. EXCEPTION: If you increase the Date Range and then Reduce the Department Selected, All Projects will be selected by default.

Objective: This blog demonstrates how to get the source code of the extension app installed in Microsoft Dynamics Business Central. Pre-requisite: Docker Microsoft Dynamics 365 Business Central on Container Nav-Container Helper Module installed in Powershell Demonstration: 1. List the Docker Container: Command: docker ps 2. Entering the Container: Command:   Enter-NavContainer <Container Name> 3. List all directories in Container: Command: dir / ls 4. As Extensions are stored in C:\Extensions getting into Extension directory Command: i. cd C:\Extensions ii. dir 5. Exit the Container: Command: exit 6. Copy the .app file inside the container to local path: Command: docker cp <Container Name>:C:\Extensions\<Filename><LocalDirectory> 7. Make a copy & rename the file with .rar as extension 8. Extract the .rar file and explore the ‘src ‘ folder to get the source code in .AL files Conclusion: Thus, in this way the source code is visible and can be used for reference.

Introduction: The much awaited Dynamics 365 Business Central officially released on 2 April 2018. We are often used to creating virtual machines and setting up Microsoft Dynamics NAV but D365 Business Central doesn’t require a VM, we can set it up on Azure and use it locally. Pre-requisites: Microsoft Azure Licence File Steps: 1. Create a resource group in Microsoft Azure. I have named it navbc. 2. Click on NAVBC resource group and open Azure cloud shell Enter the below command az container create –name MDBC  –image “microsoft/dynamics-nav:12.0.21229.0″ –resource-group NAVBC –os-type Windows –cpu 2 –memory 3 –environment-variables ACCEPT_EULA=Y USESSL=N LICENSEFILE=” ” –ip-address public –port 80 443 8080 7049 Here, –name: your container name –resource-group: your resource group name –environment-variables ACCEPT_EULA=Y – mandatory parameter. –ip-address public: mandatory LICENSEFILE=” ” : Here upload your licence to the cloud and then copy the link. –port: list of ports. 8080 is a default value. Use 7049 port number to download symbols whichout which you cannot connect VS code to your container Open your Resource group, the container instace is created click on the instance. This will open the container instance overview page. This will take quite some time approx 15-30 mins get your container instance running. For more information on azure commands click https://docs.microsoft.com/en-us/azure/container-instances/container-instances-quickstarthere 3. To get the container infomation enter the below command az container logs –resource-group navbc –name mdbc 4. Download .vsix file Open your container Instance you will find your IP address. copy it. Copy the link under Files http://<containerIP>:8080/al-0.15.18771.vsix and replace b08..  with the conatiner IP address.This will download your .vsix file. now launch your VSCode and click on Extensions. Install .vsix and AL Language for D365 BC. 5. Publish an Extension Open the launch.json file and replace the server with “http://containerip”. Download symbols using command Ctrl+P Build(ctrl+shift+B) the package and publish it! (Ctrl+ F5). Yay! Now the final step open D365 Business Central. (http://containerip/NAV) This will prompt you for User name and pass word and bang D365 Business Central opens.

Introduction: If your organization uses forms to collect sensitive information, Document Fingerprint makes it easier for you to protect this information by identifying standard forms that are used throughout your organization. Document Fingerprint is a feature of Data Loss Prevention that converts a standard form into a sensitive information type which you can use to define DLP Policies. Working: Documents have unique word patterns. When you upload a file, the DLP agent identifies the unique word pattern in the document and creates a document fingerprint based on that pattern and uses that document fingerprint to detect outbound documents containing the same pattern. Limitation: Document Fingerprint DLP agent will not detect sensitive information in the following cases: Password protected files Files that contain only images Documents that don’t contain all the text from the original form used to create document fingerprint. To upload a blank form: Go to Exchange Admin Center > Compliance Management > Data Loss Prevention. Click Manage document fingerprints. Click + New, provide a Name and Description. The name you choose will appear in the sensitive information types list. Click Add + to upload a form. Choose a Form and click Open. Click Save. The Document Fingerprint is now part of your sensitive information types, and you can add it to a DLP policy . Creating a rule in DLP policy: Go to Compliance Management > Data Loss Prevention. Click + New, choose custom DLP policy. Provide a Name and Description for DLP policy, Enable the state of the DLP policy and Enforce the policy. Click Save. New created DLP policy will be shown. Click Edit and go to Rules > Create a new rule. Add a Condition, so that if this (Employee Information Form) sensitive info type is sent to the external Recipient. Depending upon your organization requirement add an Action, that it will block the message, but sender can override and can send the documents to external recipient if there is a business requirement. Fill out the other properties of this rule as per your requirements and Save. So, whenever a user will try to send a form which has been managed by Document Fingerprint to external contacts the results will be as below. Conclusion: In this way you can secure and monitor the sensitive information from leaking outside your organization.

Introduction: In this blog article, we will learn how to create entity Store in Dynamics 365 For Finance and Operations. Steps: 1. Add new Items 2. Under Dynamics 365 items –> Analytics –>Aggregate Measure. 3. Assign a table to the aggregate measure. 4. Add Measures to the aggregate Measure . Mention the field and Set appropriate properties of the measure. 5. Create a new dimension. 6. Assign a table or view to your Dimension. 7. Now from the solution explorer drag the newly created dimension to the aggregate measurement. The aggregate dimension will have system generated dimensions already present by default. Select the dimensional field and make appropriate relations. Save the Project. Clean and rebuild the project. Synchronize the database . This entity store will be available under entity store in Dynamics 365 for Finance and Operations.

Introduction: This blog demonstrates how to modify the non-key fields with respect to the key fields. Pre-requisites: NAV 2017 Demonstration: Generally, when modifying the records, the syntax used is Record.FieldName := New_Value; Record.MODIFY(TRUE); In order to do modify the Key fields of the table, we need to know the order in which the keys are assigned. To modify the primary key, the syntax used is Record.RENAME(Key1,Key2,Key3); Where, Key1 corresponds to value that is supposed to be assigned to ‘No.’ field. Key2 corresponds to value that is supposed to be assigned to ‘LineNo.’ field. Key3 corresponds to value that is supposed to be assigned to ‘Leased to Driver No.’ field. Even when the single key field is to be changed, all the key fields should be present in their sequential order. If there is any mismatch in the number of keys, NAV throws the following runtime error. Note: Renaming operation is a costly operation. Creating a New record and Deleting the old record is faster as compared to Rename. In case where the performance is the requirement, the second method is preferred.