Introduction: Let’s consider a scenario where we need to raise an expense entry for a Fixed Bid project. PSA by definition does not charge for expenses. If you want to have fixed price for the project and expense to be charged for other things, you need to do it via adjusting the contract. Steps: Follow the steps below to prepare the contract: Prepare a contract and add a Fixed Bid project with “Time” and “Fee” as the option shown below: Add another line and create another Time and Material Type project and select “Expenses” as the option. You will have to inform the team to select the right project while raising the expense, that is the T&M one. Now when you create the invoice via that contract, you will get your milestone as well as the expenses coming up in the same invoice as shown below.

Introduction: When content reaches the end of its retention period, there are many reasons that you might want to review that content. You might need to assign a different retention period, suspend the deletion, etc. A disposition review includes only content in SharePoint sites, OneDrive accounts, and sites for Office 365 groups. A disposition review can’t include content in Exchange Online, Skype, public folders, or mailboxes for Office 365 groups. Sign in with Office 365 credentials, go to Admin Center > Security & Compliance > Data Governance > Disposition. Permission for Disposition: Reviewers must be the member of Disposition Management role and the View-only Audit Logs role. Setting up the Disposition review by creating a Label: Disposition review option is only available when you create a Label with retention settings. This option is not available in a retention policy. For creating a Label, navigate to Office 365 Security & Compliance, go to Classification > Labels. With Labels, you can classify data across your organization for governance, and enforce retention rules based on that classification. Switch toggle button to ON for applying Retention. Tick Trigger a Disposition review for setting up Disposition. When a content (to which this label is applied) reached retention period, reviewer is notified by email that content is ready to review. Reviewer can then go to Disposition page and select one or more item. The reviewer can: Apply a different Label. Extend the retention period. Permanently delete the item Export the Disposition item: In addition, you can export the items in .csv file that you can open in excel. Conclusion: It is important to review content when it reaches it’s retention period so if it requires you can assign different retention tag or label.

Introduction: Supervision lets you define policies that capture email and 3rd-party communications in your organization so they can be examined by internal or external reviewers. For creating Supervision policy, one must made add himself to the Supervision review role group so that they can set up policies. Go to Office 365 admin center > Security & Compliance > Permissions. Or Sign in to https://protection.office.com with your Office 365 credentials. Create Policy for Supervision: Go to Office 365 Security & Compliance > Data governance > Supervision. Click Create and then follow the wizard to set up the following pages of the policy. Enter a name and description for your policy. Choose users to supervise, here you can provide list of users or you can make Group in Office 365 and provide the Group name. If you provide Group, then you can exclude any user from Supervision by providing that user name under Exclude these users. Choose communications to review. If you want to scope the review further, click Add a condition. You can specify multiple conditions. Specify percentage to review. If you want to reduce the amount of content to review, specify a percentage. If you want reviewers to review all items, enter 100%. The users and groups you choose will use the Supervision app in Outlook web app to examine the communications that are returned by this policy. You can include email addresses for internal and external reviewers. After you have completed all sections of Supervision policy, review your settings and click Finish. Reviewers will use the Supervision add-in for Outlook web app to review communications. The add-in is installed automatically in Outlook web app for all reviewers you specified in the policy. Conclusion: It is good practice to create Supervision policy to capture email communication in your organization.

Introduction: In this article, we will learn how to configure Live connection for Analysis Services in Power BI. Requirements: Power BI Licence SQL Server Analysis Service Power BI Gateway (Refer this link to configure Power BI Gateway) Steps to Connect Analysis Services Live in PowerBI Open PowerBI Desktop Click Get Data and Select Analysis Services In the Analysis Services Connection details, select Live Connection Mode for Live Connection. Once the Data, Measures, KPIs are loaded you can create Power BI Dashboard. Live Connection enabled status is visible at the right bottom of the Power BI Desktop. Before publishing the Dashboard, login into Power BI Service. Under Manage Gateway, we must add a data source for Analysis Services. Note: The account should be a Server Admin on the Analysis Server and should be a domain account in the same domain that the Analysis Services instance is located. (Click here for more information on Analysis Server Connection) Go back to Power BI Desktop and publish the Power BI dashboard. In the Power BI Service, under the Reports you will be able to see the published Live SQL dashboard.

Introduction: In this article, we will learn how to configure Live connection for SQL in Power BI. Requirements: Power BI  Licence SQL Server Database Engine. Power BI Gateway (Refer this link to configure Power BI Gateway) Steps to Connect SQL Live in PowerBI: Open PowerBI Desktop Click Get Data and Select SQL Server. In the SQL Connection details, select DirectQuery Mode for Live Connection. Once the Data is loaded, you can create Power BI Dashboard. DirectQuery enabled status is visible at the right bottom of the Power BI Desktop. Before publishing the Dashboard, login into Power BI Service. Under Manage Gateway, we must add a data source for SQL Server. Go back to Power BI Desktop and publish the Power BI dashboard. In the Power BI Service, under the Reports you will be able to see the published Live SQL dashboard.

Do you feel like the vast majority of your information lives in Excel spreadsheets? Joining deals with that, as well, Microsoft dynamics nav upgrade improves your operational productivity so you have all the more convenient information. This permits you to know things quicker like when to move stock from area to another, when to markdown items, and how to showcase in one district versus another. Coordination prompts snappier dynamics.  The present clients request a great deal from vendors. Having the option to settle on basic business choices at the ideal time depends on having perceivability into your tasks. Mix is regularly the way in to that kind of perceivability. It gives you a focal area to oversee and see all your information. Introduction: In this blog, we’ll see the ‘UserName’ authentication in Dynamics NAV. It is used when we want to use the existing Windows User and has a password associated with it. This method is preferred when two or more users use the same machine and require a simple password security so that only they can access their account. Prerequisite: Microsoft Dynamics NAV Procedure: Create a User in Windows Client by going to Administration > IT Administration > General or by typing Users in Search. Create a NAV Server Instance from Administration with Credential Type as ‘UserName’. Change the ClientUserSettings ‘C:\Users\<Username>\AppData\Roaming\Microsoft\Microsoft Dynamics NAV\100\ClientUserSettings ‘Give the Server, ClientServicesPort, Server Instance & ClientServicesCredentialType. Open the Windows Client and enter the credentials. Windows Client HomePage: Conclusion: Thus, this method is preferred when two or more users use the same machine and require a simple password security so that only they can access their account.

Introduction: By default, Dynamics 365 online sets user time out 24 hours. In that case a user not required to login in up to 24 hours regardless or active or inactive. Applicable for- Applies to Dynamics 365 (online), version 9.0 Microsoft Dynamics CRM 2016 (on-premises, version 8.2) Microsoft Dynamics CRM 2016 (on-premises, version 8.1) User session timeout: Earlier there was no configuration provided to set the session timeout. Dynamics 365 with specified version have provision to set the session timeout. To enforce the users to re-authenticate after pre-defined time, this can be set by admin. Once the specified time is passes the user will logoff automatically from the system. Configure session timeout: To configure the session timeout, you need to follow the below path and set the time Dynamics 365 -> settings -> Administrator -> System Settings -> General tab By default, it is set to 1440 minutes and maximum value as well. If you want to set session time out as per you convince then you need to select the option “Set Custom” and specify the desire value. You can also specify time for warning message before the session timeouts. Inactivity timeout: By any reason a user forgot to logoff from his system then if Dynamics 365 detects the ideal mode then it will logoff the user automatically after certain period. Configure inactivity timeout: To configure the session inactivity timeout, you need to follow below path and set time Dynamics 365 -> settings -> Administrator -> System Settings -> General tab By default, “session timeout” is inactive and not enabled. If you want to configure inactive timeout, you need to enable it from general tab as shown below point no 6. Session timeout section: Minimum duration for inactivity is 5 minutes and maximum duration of inactivity is 1440. Conclusion: It is good practice to have session timeout and inactive timeout, which will provide security to data.

Introduction: In this blog article, I will talk about the November Updates for PowerBI Desktop. Conditional Formatting based on Rules: You can now set the colour of the text based on a predefined rule depending on your business logic. This enables you to colour-code your data based on a set of rules that you set based on your business logic. To do this, go to the Conditional Formatting card and select the field you want to make changes to from the drop-down menu. Switch the ‘Font Colour Scales’ option On and select ‘Advanced Controls’. The general Font Colour Scales dialog box will open. Select the ‘Colour by rules’ checkbox. The Rules pane is displayed. There are dropdown lists to select the conditions, text fields to set values and a colour selector to set the colour of the data that satisfies the condition. If left empty, they default to the Minimum and Maximum values. To add additional conditions, click the ‘Add’ button. Once done, click OK. You will see the Conditional Formatting Rules being applied and the data being colour-coded accordingly. Also, if a data value satisfies multiple rules, the bottom rule applies. Cell Alignment for Table and Matrix: Now, you can set the alignment of data to Left, Right or Center for cells in a table or matrix. This feature is very useful when formatting your report. To do this, go to the Field Formatting card and select the field you want to make changes to. Go to the ‘Alignment’ option and select the alignment of your choice from the dropdown menu. You will now see that all the data in the selected fields have been aligned according to your selection. Selection Pane Update: The Selection pane now has an added feature of letting the user select which objects are displayed on top of the canvas if there is overlapping. Locking Report Objects: There is now a checkbox called ‘Lock Objects’ that allows you to fix the position and the size of each object in a report so that no changes are accidentally made. This is very useful when browsing reports as the layout will not be affected. One thing to keep in mind is that this setting will not be saved with the report and to ensure this checkbox is ticked when browsing. New options for slow/large data sources: Sometimes, if you have a large or a slow data source, obtaining a response to actions taken in the report can take time. To improve this, options have been introduced to send fewer queries so that it is easier and quicker to interact with the report. To enable this option, go to Options and settings in the File menu. Select Options and then the Query Reduction tab. From here, you can disable cross-highlighting and automatic slicing and filtering within the report. For slicing and filtering, an apply button can be added instead so that the report is only sliced/filtered once you click the ‘Apply’ button. As you can see above, the pie chart is not sliced when ‘Product 1’ is selected. It is only sliced when the ‘Apply’ button is clicked as seen below. Improvement in filtering: The limit of 500 values on the number of values you can match when filtering has been removed. This is applicable for all data sources except Live connections to analysis services models. Conclusion: As you can see from above, the November Update is full of extremely useful features that further optimize the way we use PowerBI Desktop.

Introduction: In this blog article, we will be showing how use fetch XML to retrieve multiple records with the new Web API in Dynamics 365 version 9.0 Implementation: Step 1: The retrieveMultipleRecords() method retrieves a collection of entity records. The basic syntax is as follows: Xrm.WebApi.retrieveMultipleRecords(entityLogicalName,options,maxPageSize).then(successCallback, errorCallback); Here the options parameter refers to the query that will decide the data which has to be retrieved from the system. We will be using the fetchXml attribute  to specify a FetchXML query  to retrieve contacts of a specific account. The maxPageSize indicates number of records to be returned per page. If this is not specified the default value is 5000. In this example we have not specified the maxPageSize. Step 2:  First we write the code and upload it as a JavaScript web resource. Code var scripting = { retrieveMultipleContacts(executioncontext) { debugger; var formContext = executioncontext.getFormContext(); var accountId = formContext.data.entity.getId(); var fetchXml = “<fetch version=’1.0′ output-format=’xml-platform’ mapping=’logical’ distinct=’false’><entity name=’contact’ ><attribute name=’fullname’ /><attribute name=’telephone1′ /><attribute name=’contactid’ /><order attribute=’fullname’ descending=’false’ /><filter type=’and’><condition attribute=’parentcustomerid’ operator=’eq’ uitype=’account’ value ='” + accountId + “‘ /></filter></entity ></fetch > “; Xrm.WebApi.retrieveMultipleRecords(“contact”, “fetchXml= ” + fetchXml).then( function success(result) { for (var i = 0; i < result.entities.length; i++) { console.log(result.entities[i]); } }, function (error) { console.log(error.message); } ); } }; Here we take the execution context as the input parameter and we get the form context using the getFormContext() method. This method returns a reference to the form or an item on the form. Using the formContext we get get the account id which is used to fetch the contacts of that specific account. Step 3: On the account form, in  the form properties we set the Event to OnSave as shown below. Step 4: In the handler properties we set the function name, in our case it is scripting.retrieveMultipleContacts. And it is important to check the “Pass execution context as the first parameter” checkbox as shown below. Step 5: We see that the account A. Datum Corporation (sample) has two contacts. Step 6:  The script runs when the form is saved and while debugging we can see in the console, two contacts are returned in the results. We get the the attributes that were present in the FetchXML query. Hope this article was helpful!

Introduction: In this article, we will learn how to successfully connect to Analysis Services in Power BI for Live Connection. Checklist for Connection: The Domain Account must be a Server Admin in Analysis Server. Right Click on the Analysis Server > Select Properties > Select Security > The domain account must be added/present here.   Check Properties of Domain Account User for UPN (User Principle Name) Open Server Manager >Select Tools at right Upper Corner >Select Active Directory Users and Computers. Drill down the domain name >Select Users >Double-Click on the domain account. Click the Account tab. Note the User Logon name. User Principal Name (UPN) Mapping in Power BI Under the Analysis Server Data Source setting in Power BI Service, Navigate to Users and select the user and click Map User Name. Select CustomData and enter Replace data as the User you are logged in with and With Data as the Server Admin Domain Account UserLogon Name you had noted before. You can even test the mapping rule. For more information on UPN, watch the video for UPN Mapping in Power BI.