Introduction: The field properties pane allows you to change the name and description of a field from your fields list. Responsive slicers are the latest update to responsive visuals work. Responsive slicers: Responsive slicers are the latest update to responsive visuals work. With responsive slicers, you can resize them to a variety of different sizes and shapes, from horizontal to square to vertical, and the vales in the slicer rearrange themselves as you do. You can make both horizontal slicers and date and range slicers responsive. As with all our responsive visuals, the benefits are best seen when you use them on the Power BI mobile apps as well, since they resize automatically to fit well on all platforms. Field properties pane and field descriptions: The field properties pane allows you to change the name and description of a field from your fields list. You can access this pane by selecting Properties from the field menu. In the pane, you’ll be able to rename the field and give it a description. Once, you give a field a description, you can see if anytime by hovering over the field in the list. If you have multiple people editing your reports, this is a great way for everyone to understand what fields they should use and how measures are being calculated.  

In NAV 2017, Microsoft have added new field in Sales Area i.e. Work Description, which help users to add details about the Sales Quote and which gets copied over to Sales Invoice. This is the important field for the Sales people to give special instructions which can be used for Production if the goods are to be produced or for Stores department or Dispatch department for trading goods. The field is used to stored detailed information about the Order. There is no limitation on number of characters and it gets copied over to Posted Sales Invoice. It is a small feature in the system introduced in NAV 2017 but can be very useful.

Introduction: Narratives for Power BI is a product that automatically delivers dynamic narratives that explain the insights within your data. No more manually writing explanations and spending time interpreting data. Instead, the narratives, which are powered by advanced analytics, are perceptive and dynamic and explain what is most interesting and important in your data. Drill down deeper into your data and watch narratives update in real-time during the data discovery process Steps: Go to powerbi.narrativescience.com and enter your business email id.  A link for downloading the extension and installation instructions will be mailed to you A pibiviz file will be downloaded on downloading the extension. A pbiviz file is nothing but a custom visual which can be imported in Power BI Desktop. Import the file on Power BI Desktop Benefits: Automated Narratives generated that give more detailed insights about the report which may not even be obvious Real time update on interaction with data Many customization options to personalize your narrative Click on Narrative and select Dimensions and Values based on which Narratives will be generated. After selecting the fields you will have to select your narrative type. Discrete: For distinct data like that in Bar Charts Continuous: For continuous data like that in Line Charts Percent of Whole: For data by percentage like Pie Charts Scatterplot: For data based on scatterplot like Charts A narrative gets generated It also changes on real time interaction The type structure and verbosity can be customized in the Format Pane Type Can be Discrete, Continuous, Percent of Whole or Scatterplot. Structure can be either in Paragraph format or Bullet Points. Verbosity the level of information displayed. Low verbosity would show less detailed narrative with high level information while High verbosity would show a very detailed narrative. Medium verbosity would be a midway between both. I hope this blog encourages you to use this powerful extension to improve your reports by making it as detailed as possible with minimalistic efforts!  

Introduction: The purpose of this article is to help fellow entrepreneurs and sales managers leverage the power of Office 365 and Dynamics 365 to manage and build their sales pipeline with a few easy steps. In this article, we focus on utilizing Business Process Flows on Opportunities in Dynamics 365 and Triggering Email Notifications to team members. Step 1 – Enable the Out of the box Opportunity Sales Process In case you are not using Business Process Flows, please start using it. For a growing Sales team, using Business Process Flows on Opportunities enables a methodical approach to your pipeline management. When you enable the out of the box Opportunity Sales Process, you will see the following Process Flow appear on your Opportunities – The above Business Process Flow has 4 stages – Qualify, Develop, Propose and Close. You can move your Opportunity through each of the stages as you make progress. When the Opportunity reaches the proposal stage, we mark the Present Proposal check box as ‘complete’ as per below – We also ensure that we save the proposal on the Opportunity at that point – Step 2 – Send Email Notification to Project Delivery Manager on Proposal Complete When a proposal is sent to the Customer, we trigger a workflow notification to our HR and Delivery Managers. The Workflow email looks something like this – The above email serves as a reminder to our Delivery Manager that a new Project might be coming their way soon. It also informs our HR Manager, so they can look at our PowerBI Resource Allocation Dashboards to understand staffing and hiring needs. In addition, we also include the URL to the Opportunity, so our Delivery Manager can look at the Opportunity and even the proposal that we attached to the Opportunity. Finally, when an Opportunity is Won, we send a similar workflow email. Hence the ‘Propose’ stage email provides our Delivery Manager with some preparation time to ensure we are ready for Kick off when we Win the Opportunity.  Step 3 – Just do it. Yes, this step is same as in my previous article. Get in the habit of doing this and it will help close the communication loop from Sales to Delivery to HR, thus helping your organization meet its commitments. Remember… ‘Sales cures all.’ Let’s take care of that sales pipeline.’ You can always email me at AShah@CloudFronts.com to discuss your sales processes and technology adoption. In the coming articles, I will continue to focus on efficient ways to build and manage your sales pipeline and how this ties into one of the most important KPIs for running your professional services business.

Introduction: Missing Registration For Location Error Can come when we are trying to publish the web application on azure from Visual studio. Solution: There are many blogs which says updating your  visual studio or Upgrading Azure SDK will resolve your problem but this solutions did not work for me. So I used alternative approach for publishing. Steps: Publish your web application using visual studio. It gives this  error. but It creates App Service Plan and App Service in Azure.  sign in to portal.azure.com Select the App Service which you have created. Click on Get Publish Profile. Now Again Go to Visual studio and Publish. This time while publishing select Import. Select the file which you have downloaded from azure. Click Ok. Click On Publish. 10. Your Application will get Publish. I hope this solve your issue also.

Introduction: This blog explains how to Integrate PowerApps with Dynamics 365. Keep the following restrictions in mind: Only PowerApps users in the same tenant can access the embedded app. To access PowerApps using Internet Explorer 11, you must turn off Compatibility View. Steps to be followed: In powerapps.com, on the Apps tab, click or tap the ellipsis ( . . . ), then Details. Copy the App ID. Substitute the [App ID]value in the URI.: https://web.powerapps.com/webplayer/iframeapp?hideNavBar=true&source=iframe&appId=/providers/Microsoft.PowerApps/apps/579938ff-e1a0-4891-a8b9-8d69c103fd84 Embed your app in a website: Embedding your app is now as simple as adding the iframe to the HTML code for your site.http://<iframe width=”[W]” height=”[H]” src=”https://web.powerapps.com/webplayer/iframeapp?hideNavBar=true& source=website&screenColor=rgba(165,34,55,1)&appId=/providers/Microsoft.PowerApps/apps/[AppID]”/> To add PowerApp inside CRM  as web resource: Keep the following points in mind for authenticating users of your app: If your website uses Azure Active Directory (AAD) based authentication, no additional sign-in is required. If your website uses any other sign-in mechanism or is not authenticated, your users see a sign-in prompt on the iframe. After they sign-in, they will be able to run the app as long as the author of the app has shared it with them Steps: Specify the width and height for App. Specify the app id. Sample HTML code: <!DOCTYPE html> <html>  <head> <title>HTML Iframes</title> </head> <body> <p>App Goes here…</p> <iframe width=”250″ height=”250″ src=”https://web.powerapps.com/webplayer/iframeapp?hideNavBar=true&source=website&screenColor=rgba(165,34,55,1)&appId=/providers/Microsoft.PowerApps/apps/579938ff-e1a0-4891-a8b9-8d69c103fd84″ /> </body> </html>  

Overview: In this blog we will see how we can prepopulate lookup and dropdown (option set) fields on an Entity form in D365 CRM Portals using JS. Pre-Requisites: D365 CRM Portals D365 CRM Environment Introduction We know that if we want to prepopulate a lookup or a dropdown field on a form in CRM Portals the best method is to use Entity Form Metadata. But there is an alternative way to prepopulate the Lookup and dropdown (Option set) fields on an Entity form in D365 CRM Portals using JS. Scenario: To implement the functionality of prepopulating a lookup field we will be using the account lookup field on the CRM entity form based on the value entered in the contact field for a created opportunity in the partner portal. For the prepopulating the dropdown field we will be using the opportunity status field. Process: First of most we will see how to prepopulate the lookup field on the entity form based on the value entered in another field. As mentioned in the above scenario we need to prepopulate an account field on an opportunity form based on the value present in the contact field. To insert a value into a lookup field using JS(jquery) we need the following information as mentioned below. The field value to be displayed. For eg. Account full name. The GUID if the record to be displayed. For eg. GUID of the account record. The logical name of the entity. For eg. Logical name of the account entity. Now we will see how to get these details form the existing information we have on the opportunity form. When we open an opportunity record, on the details page in the URL section we get the id of the opportunity record as shown below We will insert this id into the fetch xml using liquid template to obtain details of the contact related to the following opportunity record as shown below. As shown above we have used the opportunity id in the fetchxml to get the contact details. Once we have obtained the contact details from which we will be using the contact name value in the next fetchxml to get the related account information. In the following below shown fetchxml we will get the value and the id of the account record to be inserted. Once we get the account record details we will write the jquery in the following manner to insert the value into the lookup field. Jquery syntax: <script> $(“form_attributeid_name”).val(“record_value”); $(“form_attributeid”).val(“record_GUID”); $(“form_attributeid_entityname”).val(“entity_logicalname”); </script> Once we publish the liquid code we will see that the account field on the opportunity form is prepopulated with the value related to the value present in the contact field. For prepopulating the dropdown(option set) field we need the option set value of the record to be displayed. To set the value in the option set we will write the following jquery. $(form_attributeid).val(“attribute_optionsetvalue”); Hope you all find this blog helpful. Happy coding in CRM portals.

Background: As we know, we can only work with Extension code in D365 Finance and Operations. In this blog article, we will see how we can add a custom display method to a Table and display it on form using Extension. Steps: Create a new Class Add Display method Display the method on form 1. Create a new Class: Go to Solution Explorer -> Project Right Click -> Select ‘Add new Item’ Select Class -> Enter Name. Class name can be anything ending with ‘_Extension’. Eg. <ClassName>_Extension Click Ok 2. Add Display method: Public Static class CFLoyaltyaddphone_Extension // Class must be static  {      [SysClientCacheDataMethodAttribute (true)]  //This statement will cache display method      public static display LogisticsElectronicAddressLocator CFS_GetPhoneno (RetailLoyaltyCard _this) //Pass Tablename as Parameter      {          DirpartyTable dirPartyTable;          Dirpartylocation dirpartylocation;          LogisticsElectronicAddress logisticsElectronicAddress;          select * from dirpartylocation              where  dirpartylocation.Party == _this.Party              join logisticsElectronicAddress               where logisticsElectronicAddress.Location == dirpartylocation.Location               && logisticsElectronicAddress.IsPrimary == NoYes::Yes               && logisticsElectronicAddress.Type == LogisticsElectronicAddressMethodType::Phone ;           return logisticsElectronicAddress.locator; //Return Field value                       }   } 3. Display the method on Form: Add the field type on form Design. Change the below property  

Dealers must guide out how they need information, for example, stock, requests, clients, and items to move through every framework. At that point, they should assemble a stage that bolsters these streams. This requires a group with broad information on your frameworks to have the option to fabricate a custom combination arrangement without any preparation. Microsoft dynamics nav upgrade provides you all of this Explanations behind structure a custom coordination including your business having incredibly remarkable necessities or the requirement for unlimited oversight and responsibility for venture. You should have the option to assemble, uphold, and keep up the incorporation. On the off chance that you have the correct prerequisites to legitimize it, at that point custom reconciliation could be best for you. Introduction: This blog describes how to change the screen while loading Microsoft Dynamics NAV Pre-requisites: Microsoft Dynamics NAV Steps: 1. Navigate to the path C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\Images. 2. Open the splash screen in Paint and save it with extension .png. I’ve added the text ‘Happy New Year’. 3. Copy and replace the image in the above folder. 4. Launch Microsoft Dynamics NAV.

Introduction: In this blog we will demonstrate how to create and associate records using Xrm.WebApi which provides methods to use Web Api to create and manage records. Implementation: Step 1: The syntax to create a new entity record is as follows: Xrm.WebApi.createRecord(entityLogicalName,data).then(sucessCallback,errorCallback); Here entityLogicalName(string) and data(object) parameters are required. The “data” parameter is a JSON object defining the attributes and values for the new record. Step 2: In this example we will create a sample account record along with a primary contact for that account, associate an opportunity to the account and create task and notes for the opportunity all in a single operation. This type of process is called as a deep insert. The code for the same is as shown below: var scripting = { recordCreation: function () { var data = { “name”: “CRAYONS LTD.”, “description”: “This Account is Created using a Web API”, “creditonhold”: false, “telephone1”: “9954565154”, “address1_city”: “Mumbai”, “primarycontactid”: { “firstname”: “Clinton”, “lastname”: “Dmello” }, “opportunity_customer_accounts”: [ { “name”: “Opportunity Associated to CRAYONS LTD.”, “Opportunity_Tasks”: [ { “subject”: “Task Created” } ], “Opportunity_Annotation”: [ { “subject”: “Note Created”, } ] } ] } Xrm.WebApi.createRecord(“account”, data).then( function success(result) { console.log(“Account Created with ID” + result.id); //perform operations on record creation }, function (error) { console.log(error.message); } ); } }; Step 3: In order to associate to an existing record @odata.bind annotation can be used. For Example: “primarycontactid@odata.bind”:”/contacts(GUID of the contact)”. Screenshots 1. A New Account is created with the name “CRAYONS LTD” and in the primary contact file the primary contact is set with the name Clinton Dmello as set in the code. 2. Also an opportunity is associated to the account as shown below in the associated view. 3. In the opportunity we can see the newly created task in the activities and a note as shown below. Hope this helped!