Introduction: What is Workflow User group? Workflow user group is a group of users under one group title in Workflows with the users’ number in a process sequence such as an approver chain. To define an approval request to be not approved until multiple approvers in a approval chain have approved it, set up approvers with incremental sequence number.Here the approval request is sent to the user with highest sequence number i.e. 1. This user will have to approve the request then an approval will be sent to the next user with sequence number 2 and so on. To define approval request is not approved until multiple equal approvers have approved it regardless of the hierarchy assign same sequence number to the users.Here the approval request is sent to all users in the group at the same time. Here, both the approval requester and approver must be set up in the Approval User Setup. This blog provides a step wise procedure how to create approval workflow using workflow user group. Pre-requisites: Microsoft Dynamics NAV 2017 Steps: I’ll explain workflow user group using a scenario. Scenario:  A sales department has a group of two sales managers. An approval request must be sent to the sales managers if the sales order amount is greater than 4000 and even if one of the sales manager approves the request, the document should be released. 1. Create a workflow user group Navigate to Workflow User group in the search bar in Dynamics NAV and click on New. Enter the code and description for it. Insert the approver users with sequence number as 1 2. Create a new Sales Order Workflow Open workflow using the path CRONUS International Ltd./Departments/Administration/Application Setup/Workflow/Workflows Click on New Workflow from Template button from the ribbon. click on the Sales Documents category and select Sales order workflow Here the Sales Order Approval Workflow opens. Click on the first event condition and add a condition on amount > 4000 The response of the first event sets the Sales order status to Pending approval, creates and sends the approval request to the approvers. 3. Set the Approver Type to Workflow User group  We are using the approval type as workflow user group hence, we need to specify this group in the workflow. Now click on the assist edit button of the first response and click on the third response line. By default the approver type is Salesperson/Purchaser Select the Workflow User group from the Approver Type drop down and select the workflow user group code. Now the approval request will be directly sent to the Workflow User group with code SALES MANAGER 4. Set the sales order workflow condition Click on the second event ‘An approval request is approved’. Here we observe that the condition reads Pending approval :0 which means that when all the approver users approve the request i.e. when the the count of the pending approval is 0 then according to the response, release the document. Now we want even if one of the approver users approves the request, the sales order document must be released. we’ll have to change the condition to Pending approval :1 Here when the approval request is sent to both the sales managers, the pending approval count is 2. Now when one of the sales manager approves the sales document the count decreases to pending approval:1hence when the one of the sales manager approves the sales order document the sales order is Released Finally enable the workflow 5. Send an sales order approval request Navigate to sales order and create a sales order greater than 4000 and click on send approval request. Observer the status of the sales document changes to Pending Approval. Login Microsoft Dynamics NAV with the sales manager user credentials and navigate to ‘Request to Approve’ To view the sales order click on Open Record To approve the order click on Approve. This will Release the sales order document. To reject the order click on Reject. This will change the status to Open. Comments can be added by clicking on comments. The sales manager approves it and the document is approved thus the status changes to Released Conclusion: To summarize everything, create a sales order workflow from the template. Create a workflow user group and assign sequence number to 1. Set the condition of amount > 4000 and Pending approval to 1. Select approver type as Workflow user group and select the workflow user group code. Finally enable the workflow.

Introductions: This blog highlights the feature for Drillthrough in Power BI Services, this is the ability to define a report page as a drillthrough page. You can now define an individual report page as a Drillthrough page. Ideally these report pages should be configured across a single entity. With that focused report page, users can right-click on a data point in other report pages, and drillthrough to the focused page to get details that are filtered to that context. Report Example: Below example uses the NORTHWIND database as a data Source, you can download sample database from here. To use drillthrough, create a report page that has visuals you’d like to see about the type of entity for which you’ll provide drillthrough. Your entity Relation should exist while you provide the drillthrough. Entity Relation Diagram: To use the drillthrough functionality right click on the any model and then you can go to the next related page, and data will be filtered according to that data point. How to create Drillthough in Power BI Reports: Select the entity that is used in the report, place the column that will be used from the drillthrough and at the page level drop the column in Drillthrough section below, this needs to be added to child page. When this is added in child page, there will be a back button that will be enabled in the child page. This button helps to navigate back to the parent page or to Drill Up. When this setup is complete you can use the drill up functionality in the parent page when you right click on any visual, option will be enabled. You can try this by yourself on the below power BI Report: Parent Page: Product Child Page: Orders, Region, Customer Feel free to leave comments if there are any issue while implementing the same, or feel free to contact us.

Introduction: Encryption is the process by which information is encoded so that only an authorized recipient can decode and consume the information. Steps: The process to setup and enable Office 365 Message Encryption is easy. There are three main steps that need to be followed: Activate Azure Rights Management. Setup Azure Rights Management for Exchange Online. Setup transport rules to enforce message encryption in Exchange Online. Step 1: Activate Azure Rights Management for O365 Message Encryption. Sign in to Office 365. In O365 Admin Center, go to Settings > Services & Add-ins and select Microsoft Azure Information Protection. Click on Manage Microsoft Azure Information Protection settings and you will be redirected rights management Activate the Rights Management. Step 2: Set up Azure Rights Management for O365 Message Encryption. In this step we will use PowerShell to connect to Exchange Online, Open PowerShell as Administrator and enter the following commands to connect and import the session Set-ExecutionPolicy RemoteSigned $cred = Get-Credential $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $cred -Authentication Basic –AllowRedirection Import-PSSession $Session Verify your IRM is not already configured Get-IRMConfiguration Configure RMS with the online key-sharing locationfor Exchange Online with PowerShell (locations below). Set-IRMConfiguration -RMSOnlineKeySharingLocation https://sprms.ap.aadrm.com/TenantManagement/ServicePartner.svc  Location RMS key sharing location North America https://sp-rms.na.aadrm.com/TenantManagement/ServicePartner.svc European Union https://sp-rms.eu.aadrm.com/TenantManagement/ServicePartner.svc Asia https://sp-rms.ap.aadrm.com/TenantManagement/ServicePartner.svc South America https://sp-rms.sa.aadrm.com/TenantManagement/ServicePartner.svc Office 365 for Government https://sp-rms.govus.aadrm.com/TenantManagement/ServicePartner.svc Import the Trusted Publishing Domain(TPD) from RMS Online Import-RMSTrustedPublishingDomain -RMSOnline -name “RMS Online” Verify successful setup of IRM in Exchange Online. Test-IRMConfiguration –sender admin@domain.com Disable IRM templates in OWA and Outlook.  Set-IRMConfiguration -ClientAccessServerEnabled $false Enable IRM for Office 365 Message Encryption. Set-IRMConfiguration -InternalLicensingEnabled $true Viewthe IRM Configuration. Get-IRMConfiguration Step 3: Create transport rule to encrypt message. In Office 365 Admin Center, go to Exchange Online Admin Center. Go to Mail Flow > Rules. Click the + and create your transport rule. This rule will encrypt anything that is sent external. Make sure the rules are active. Testing that the transport rule applies Office 365 Message Encryption. Conclusion: Its easy to encrypt your mail and secure it in Office 365.

Introduction: You can import XML as a data source, using Scribe Insight, to execute two primary actions: Integrate with locally available XML data. Receive data as XML from remote systems. Steps: Open Scribe Workbench and click on ‘Configure Source’. Click on ‘New’ and select XML. The XML Component Connection Wizard will open. Click Next. Select ‘Use as a Source’. Click Next. Select ‘Dynamic’ and click Next. In the ‘Sample Source Document File’ field, input the XML File (.xml) path and in the ‘Schema File or URL’ field, input the path of the Schema file (.xsd). Click Finish and give a name to the XML source. Click OK. Select ‘XML Objects’ and select the entity. Click OK. It will now be configured as the Source. Now you may proceed with mapping the fields required for integration with XML as the Source.

Introduction: Power BI comes with a powerful language recognition engine that lets you ask questions of your data using conversational phrases and questions. Based on these questions, Power BI dynamically creates charts and graphs. For example, if the data is defined as a date type, it is more likely to be displayed as a line chart. Data that is categorized as a city is more likely to be displayed as a map. Questions can be asked on a dashboard. The feature is called as Q&A or Questions & Answers. Natural Language Q&A is really an underused tool in Power BI despite of being really powerful. Following is my dashboard on a Credit Card transaction dataset. I will be performing simple Q&A questions on this dashboard. Pre-Requisites: Power BI Subscription Features of Q&A: Auto Prompts: This prompts are created on the basis of: a. the questions used to create tiles that are already pinned to the dashboard, and b. the name of tables in the underlying dataset(s). Can build a question using the prompts (Eg. What is the total amount in April) Dropdown pops up while typing a question. Helps with auto-replacement terms as well. Can use Aliasing table to make querying more powerful. Featured Q&A Questions Click on your Dashboards Ellipses and then select Settings. Click on the Datasets tab and select Featured Q&A questions. Select Add a question and type a question and then click on Apply. Now whenever a user starts typing on Q&A they will be prompted with this question first. Dims words it does not understand. Can combine results from more than one data set. When you type a query, Power BI looks for an answer in any dataset that has a tile on that dashboard.  If all the tiles are from datasetA, then your answer will come from datasetA.  If there are tiles from datasetAand datasetB, then Q&A will search for the best answer from those 2 datasets. Dynamically generates a visual depending on the question. Can change the visual type using the ‘as’ keyword. Can pin this new visualization back to your dashboard. The visual answers can also be edited. Just by using the Visualizations and the Filter panes on the right side of the screen we can alter the layout, adjust filters and change fields. Conclusion: We have discussed the various features that can be used with Q&A which can improve our ability in analyzing data.  

Introduction: In this Blog article, we explain about the new feature of the power BI: Bookmarking. Bookmarking: Bookmarking is the a very powerful way to save and share out your Reports and Dashboards with other people. Bookmarking lets you save your interesting states as part of your report. You can create list of bookmarks. Using this Bookmarking you can create report navigation and many more. You can add a bookmark to your report for: The current page Drill location Filters Slicers Visibility ‘Focus’ Mode Once you turn on the preview feature, you can add bookmarks by opening the bookmarks pane under the view tab. Set up your report, with all the filters properly set, and click the Add button. Once you hit the add button the it will add a bookmark to pane. You can rename this bookmark and also you can update or delete the bookmark. You can easily access the save states. You can add many bookmarks as you want. Also You can used your Bookmarks as a story by clicking on the View option. By clicking on the view you will enter into the view mode of the bookmark. In the view mode, there is a title bar for each bookmark that includes the bookmark name and navigation arrows. At this point, you can close the bookmarking pane if you want. This mode is a good way to preview your bookmarks in the Power BI Desktop. It’s also a great way to navigate bookmarks in the Power BI service, where you can also enter into full screen mode to hide all the navigation menus. To enable the preview option: This feature is in preview, so you need to enable it the first time through File>Options and Settings>Options. Open Preview features tab – > select Bookmarks option.

Transform administration calls into a vital preferred position with Dynamics 365 Field Service management software. It gives all that you need – from advanced work request planning to prescient support  Elements 365 Field Service is intended for organizations who do deal with sites at a client’s home or premises. This can incorporate establishment, booked or repeating support, or reacting to break/fix issues. Any help based association that has an emphasis on conveying nearby establishments and break/fix will profit by Dynamics 365 Field Service. The test for these organizations is to improve the profitability of field based groups while additionally expanding consumer loyalty.  With highlights including plan improvement, resource the board and receipt handling, Field Service is a start to finish arrangement that furnishes colleagues with admittance to what they have to take care of business. Introduction: This blog explains how to configure Notes on Entity in D365 Portal. Steps of Implementation: Below steps explain how to configure Notes section on Partner Work Order form in D365 Partner Field Service Portal. Create new Section for Notes on Form in D365 Field Service. Save and publish the changes. Navigate to the Portal -> click on the Entity Permission -> click on the new button. Create entity permission for Work order and screenshot for reference. Set Scope to “Global”. Enable all Privileges In this record -> go to child entity permission sub grid follow below steps and screenshot for reference. Create “Note” entity permissions for Work order. Set Scope to “Parent” Parent Entity Permission as “Work Order Comments” Enable all Privileges Navigate to the Portal -> click on the Entity Forms -> Open Work Order Entity Form. Set Tab Name as “None” on Entity Form and save record.Refer the below screenshot. Add Notes in Entity Form Metadata and screenshot for reference. Conclusion: Above description in blog configure Notes on Entity in D365 Portals and below is screenshot for reference.

With Scribe Insight, you can import XML as a data source to fulfill two main tasks: Support integration with locally available XML data. Receive data as XML from remote systems. Creating A Publisher Expand the Console site node. Expand the Integration Server node, and then click Publishers and Bridges. The Publishers/Bridges window opens. Click ‘Add’. The ‘Add New Publisher/Bridge’window opens. Add a new Publisher/Bridge using the following steps: (i) Step 1: Publisher/Bridge Type: Select the Type from the drop-down menu and give an appropriate name. Proceed to Step 4 – Publisher/Bridge Properties. (ii) In Step 4 – Publisher/Bridge Properties, click ‘Add’ after Connecting. Select the Entity and fill in the Message Label. Select the Event checkboxes you require and add any related parent or child entities as well as Priority. One can also choose to ignore changes from a User. (iii) Select ‘Active’ in Step 5 and click Apply. To Retrieve An XML File Now that a Publisher has been created, the User can get an XML file of a record that has been created or updated after the activation of the Publisher. To retrieve an XML file of a record created or updated, go to Queue Browser in the Console and click on ‘[INPUT] CLOUDFRONTSBI\PRIVATE$\SCRIBEIN’. The message label of the Entity in the Publisher will be displayed. Right-click on the Message Label and click on ‘Save Body’. Select the Destination Folder and click OK. This will save the XML File (.xml) of the record. To Retrieve XML Schema In Step 4. Publisher/Bridge Properties, click ‘XML Schemas’. Scribe Insight generates the new XML schema of ‘Account’, which is required when you connect to the XML schemas using the Scribe Workbench XML Source Connection Wizard. Browse to where you want to save the schema file (.xsd) and click OK. You are prompted to verify the location. Click OK.

New SQL Server Management Studio 17.3 Release update: This wizard was created to improve the current import experience leveraging an intelligent framework known as Program Synthesis using Examples (PROSE). For a user without specialized domain knowledge, importing data can often be a complex, error prone, and tedious task. This wizard streamlines the import process as simple as selecting an input file and unique table name, and the PROSE framework handles the rest. This wizard is driven in a very simple manner to ease the data load in SQL Server from Flat Files. This Feature limits to SQL Server Management Studio 17.3 and higher versions. To access the Import Flat File Wizard, follow these steps: Open SQL Server Management Studio. Connect to an instance of the SQL Server Database Engine or localhost. Expand Databases, right-click a database (ImportFlatFile in the example below), point to Tasks, and click Import Flat File above Import Data.   Sample Data Load From Flat File using Import Flat File Wizard. Run the Import Flat File Wizard. Click on Next to provide the Input Source File, your source file could be any delimited file. NOTE: File Extension doesn’t matter unless the file is a Flat file and is a Delimited file.   Click on Next, it will take you to preview of the data, the preview limits to first 50 Rows fetch from File.   Clicking on Next, will allow user to Alter the metadata of Columns that will be created by this wizard. Flat File provides default datatype, we can change it in below screen. Event Primary kea and Not Null Constraint can be created with this wizard.   Clicking on Next will take you to Summary page and will provide final information of the data transfer and Table that will be created.   Clicking on Next will start the import process.   Table create and data is successfully Loaded.   This features uses PROSE analyses data patterns in your input file to infer column names, types, delimiters, and more. This framework learns the structure of the file and does all of the hard work so our users don’t have to.

Introduction: In a scenario where a company uses Excel to keep the data and wants to move its ERP to Dynamics NAV.  A lot of data needs to be added in NAV in order to get a full system working. Thus, copying each entry could be a time-consuming task. Microsoft Dynamics NAV is enabled with the feature to Import and Export Data to and from Excel. Procedure: Ways to Import Export Data from Microsoft Dynamics NAV to Excel There are two ways to Import Export Data to and from NAV Using XMLPORT(Server Side) Using Configuration Packages(Client Side) XMLPORT Method Steps: 1. Create a new XMLPORT in NAV Server Object Designer Window 2. Adding Entries in the XML Port NodeName: Root > Node Type: Element > Source Type: Text > Data Source: <Root>(By Default) NodeName: Table Name(Anyname is fine) > NodeType: Element > SourceType: Table > Data Source: Table(Select the Table click on the Rollup Button) NodeName:Field Name > NodeType: Element > SourceType: Field > Data Source: Field(Select from the Rollup) 3. Indent the Entries as Root(Indent: 0) > Table(Indent: 1) > Fields(Indent :2) 4. Changing the properties of the XMLPORT Delimiter: <‘’> Separator: <TAB> 5. Change the Properties of the Table Format: Variable Text AutoUpdate: Yes AutoReplace: No 6. Save the XMLPORT and RUN For the first time Choose the Direction as ‘Export’ > Save > Filename.xls 7. Open the file, make change the entries and close the file 8. Run the XMLPORT and choose direction as ‘Import’ and select the file Verify whether the import is successful by checking the entries in the table. IMPORT EXPORT using Configuration Packages 1. >Open the Microsoft Dynamics NAV (Client Application) and search Configuration Packages. 2. Create a New Configuration Packages > Enter the following values in required fields as Code: 123(Appropriate Number) and Package Name: Excel Import(Appropriate Name) > Select the Table ID:50001(Using Drop Down) and Table Details will be updated. 3. Under the ‘Tables’ ribbon click on Excel > Export to Excel > Save as appropriate file 4. Open the Excel File and change the entries 5. From the ‘Tables’ ribbon, select Import from Excel and Select the file 6. By this time the data is not written to the table just imported. Thus have to apply the data. After applying, it gives the data inserted or modified or errors if any. Conclusion: The fields are mapped first, thus all the fields to be Imported and Exported are to be known first. Only one excel file per table can be used. The file extension needs to be .xls and not .xlsx as it gives an encoding error while opening the file. Importing or Exporting computed fields cannot be done by this method.