Overview Spring 2017 update to Dynamics 365 is coming up in July 2017. And there are exciting new additions and improvements coming to Dynamics 365 For Sales. Here are the highlights on what’s up next – LinkedIn Sales Navigator: Improve performance of their sales processes from LinkedIn Company and Sales profiles Display Navigator person and company information on Lead, Account, Contact and Opportunity pages. Automatic daily updates between the two systems. Write select Sales Navigator activities (InMails, messages, notes and call logs) to D365 For Sales. D365 Connector for LinkedIn Lead Gen Forms (only if you use Lead Gen Forms for LinkedIn): Bring LinkedIn Leads to D365 Online using this connector. Automatically captures and syncs leads to further nurture them. Support for multiple LinkedIn member accounts. Configure how Leads will be captured. Analyze Lead performance. Prospect to Cash Integration: Connect D365 For Sales and D365 For Operations using Common Data Service. Maintain Accounts in Sales and sync to Operations as Customers. Sync Contacts Sync Products from D365 for Operations and sync them to Sales. Create Quotes in D365 for Sales and sync them to Operations. Generate Sales Orders in Sales for existing Productions and sync them to Operations. Generate Invoice in Operations and sync them to Sales. Relationship Analytics: Relationship health Most Contacted Relationship KPIs Dynamics 365 Administrator Role in Office 365: Assign D365 Admin role at a tenant level. Can manage instances and admin functions, access D365 application if they are licensed. Bulk Data Loader:  New cloud based service for bulk import/export to cloud staging tables and perform light data-quality functions. Then push back to Dynamics 365. Will be accessed from a link in Admin Center and will redirect of LCS. Cortana Integration: Surface relevant Activities, Accounts and Opportunities to Salespeople. Customer backup and restore (online only): Customer backup and restore on Azure servers securely. Database Level Encryption with Customer Managed Keys: Ability for customers to generate their own keys and upload it to Azure Key Vault. Also revoke access on demand in a self-service manner. Portal Features Ability to Include attachments on knowledge articles so that they can be displayed on the Portal. Improved Admin Wizard on Portal to add an entity to the Portal. When data is updated in the entity, it will be automatically available to Portal users who have access to these data. Source Code for Portals will be available on the Microsoft Download Center under MIT license for developers to download. This will let Portals be deployed for D365 Online as well as on-premise environments. Support Azure Ad-B2C for Portal authentication using a single sign-on configuration Configure portal authentication for SSO. Manage Portal security in Azure. Support Timezone independent date formats in Portal forms. This means that  

Introduction: Info code is used to capture additional information and Point of Sales. It Prompt Point of sales User to enter information at time various action on Point of Sales. This various can be like, Sales transaction, Return, payment method, customer. In this blog we demonstrate info code setup on Sales return Product. Scenario: Customer want to return some product, company want to know why customer is returning the Product and want to capture reason in Point of sales. Follow the below steps to configure info code setup return transaction. Step 1: Open then Dynamics 365, go to the retail and commerce Go to Channel Setup and click on info code. Step 2: Click on New Button. In Info code Number mention “Sales_Ret” , In description write “Sales Return Info code”. Prompt text will display on Point of Sales. In Put type Select Option Text. It Mean Point of Sales User will enter the reason in text format. In General Tab Select Yes in Input required Step 3 : Go to POS Profile and select Functionality Profile Select functionality Profile of store which you want to change. Step 4: Click on Edit button and go to Info Code Tab. In Info code tab Click on Return Transaction and Select “Sales_Ret”.Click on Save button. Step 5 : go to Channel Database and run the Job for that store. After that login in MPOS Or CPOS and Post return sales Entry. POS will POP-UP with Return Info code. From above steps with you can assign info code entry to POS Transaction.

Introduction: While customizing or adding a button to ribbon there are chances that you want to add same behaviour as of an existing button. But it is not known how to check what logic has been applied to that button. Description: If you want a custom button to have same behavior as that of system button, then how to achieve this. This can be achieved by using the workbench Ribbon customization tool. Let’s see how to do that. Open Ribbon Workbench and select the solution which you want to customize. Here I want my custom button to have same behaviors as of the Qualify lead Right click on the Qualify button and select customize command. As soon as click on the customize button you will able to see all the customization that are applied on that button as show below. Now you can add all the display and enable rule to your command as shown below. Similarly, you can add display rule as show below. Now you have same customization as that of the lead button.  

In this blog, we shall see how can a user make simple modifications to the CRM Portal Entity Form using ‘Entity Form Metadata’. Pre-Requisites: D365 CRM Portals D365 CRM Environment Why Use Entity Form Metadata? Entity Form Metadata has a modification logic to arguments or has the ability to override the functionality of form fields which isn’t possible using the CRM’s native editing capabilities. Entity Form Metadata allows the user to configure specific pieces on the form like a sub-grid, the notes section or an entire Section or Tab on the form which cannot be modified at the top level configuration. Scenario: In the following scenario the user will see how to make simple customizations like converting a “Lookup” entity field to a “Dropdown” field  on the Create Case Entity Form on CRM Portals using Entity Form Metadata. In the following image below we see that the ‘Product’ field on the  Create Case  Entity Form which is a look up field which we will be converting to a dropdown field using ‘Entity Form Metadata’. Fig 1. Image of the Create Case Form before making changes using Entity Form Metadata Process: In order to make the above changes to the attributes that are present on the Entity Form in CRM Portals the user will have to create a Entity Form Metadata which will convert the lookup attribute to a dropdown list. Step 1: The user will have to go on the CRM Main Menu to Portals> Entity Forms> Customer Service-Create Case Form as shown below. Fig 2. Selecting the Create Case Entity Form Step 2: On the Entity Form the user will have to scroll down to the form till Entity Metadata property doesn’t appear. The user will have to create a new Entity Form Metadata by clicking on the ‘+’ option to the right as shown below. Fig 3. To create a new Entity Form Metadata Step 3: In the New Entity Form Metadata use will have to select ‘Type’ as ‘Attribute’ and select the Entity from the drop down list in ‘Attribute Logical Name’ to which the following change is to be made in this case we will select the ‘Product’ field. Under ‘Control Style’ select the Control Style as ‘Render Lookup as Dropdown’. Fig 4. Entering Specific Details into the Entity Form Metadata Dialogue Box. Step 4: Click on ‘Save and Close’ once the details is entered. Now open the Portal Form Page to which the changes are made. The user will find that the ‘Lookup’ Product field is converted to a ‘Dropdown’ field. Conclusion: Thus, in this way user can make simple customizations to the Entity Form Page in CRM Portals using ‘Entity Form Metadata’ which isn’t possible to be achieved at top level configuration methods.  

Introduction: Want to make a dedicated OneNote notebook per Dynamics 365 record? Dynamics 365 Integration is what you need. This integration provides you the ability to take notes in the notebook in context of Dynamics 365 record for selected entities. OneNote records can be directly accessed on the Activity wall of the record whether on web application or on the mobile apps. Pre-Requisites: Server based SharePoint integration needs to be enabled between D365 and SharePoint Online. OneNote integration is only supported for SharePoint Online. Document Management is enabled for the Entity and the same is setup in Document Management under Settings in Dynamics 365. Setting Up: Before we begin, look that OneNote Integration won’t appear yet in Document Management under Settings since we don’t have Server-based SharePoint Integration enabled yet. Once you’ve enabled Server-based SharePoint Integration, you’ll see OneNote Integration Note: By default, OneNote integration will be enabled for Account, Contact, Lead and Product. So, I’ll enable OneNote integration for one of my custom entities. Following are the steps to enable the same: I have an entity called Order Fulfilment. On this entity, I have the usual Activity Feed as below   First, the entity needs to be Document Management enabled to be able to be listed for OneNote Integration as shown in the image below on entity level. I’ll navigate to Settings > Document Management > OneNote Integration. Because Document Management has been enabled on Order Fulfilment entity, I can see Order Fulfilment (I’ve ticked the same and clicked on Finish)3. And DONE! Accessing OneNote for a record Once I’ve configured this, I’ll open the Order Fulfilment record I was looking at. Once I click on it, I’ll see a Notebook has been created. And clicking on the Untitled Notebook will take me to OneNote Online for that record Hope this was quick and easy!

In this blog article, we will see how we can open a URL in web browser from D3fO using X++ code. It is achieved using Browser class which extends System Class xBrowser having only method navigate(). It has three parameters from which only first is mandatory: downloadURL (string) – URL you want to browse. openInNewTab (Boolean) – It is used to specify url should be open in same tab or new tab showExitWarning (Boolean) – Prompt a dialog to exit the current page. Create a new Class: class CFSBrowseURL { } Call URL: public static void main(Args _args) { Browser browser = new Browser(); browser.navigate(‘www.cloudfronts.com’, true, false); } So, this will open URL within a new tab in browser using X++. Let me know your reviews and queries. I will soon come up with more articles, as I further explore D365 Operations.

Microsoft Dynamics 365 App Development Services is a new generation business application platform from Microsoft that provides an end to end solution to all your growing business needs starting from design, development till the appsource listing and future enhancements. Our App advancement administration group has profound skills in creating sophisticated business applications on the head of Dynamics 365 for our accomplices. We help you through the whole lifecycle, from Development to AppSource posting and improvement support, permitting you to concentrate on your Business Strategy and Marketing. Once the application is prepared and inside tried, we will work with you to present the application to Microsoft, address any issues and get the application recorded on the AppSource. Project Managers often struggle to manage the project plan, keep the Gantt Chart updated.  As there are many activities under the PM’s umbrella to ensure the project delivery goes out smooth and successful. CloudFronts – PM App helps you to keep your project plan updated. Now, you will ask how does that happen? Following is what we do: 1.       We create the Gantt Chart, in which we: List down the Activities Assign duration Assign Billing Code Assign Resources Assign Predecessor’s to the Activities: This is an important activity. What happens when a predecessor is assigned to the task is, that task goes in inactive State. Unless the previous task is marked complete, the dependent task doesn’t turn active. Now, it is Project Manager’s responsibility to ensure that there is 100% time entry done for that task. This will tell you that the task is actually complete. PM-App also provides you this information. Once you double click the task, you see a Progress Field over that. If that is marked as 100%, means the time entry for the task is done by the developer completely. Now the project manager can safely mark the task as complete which is green in colour, so the dependent task becomes Active. Tip: A well-managed Gantt chart provides a lot of benefit to all the stakeholders, so always keep it updated.

Introduction: The tablet app for Dynamics CRM have limits that allows only number of fields, tab and grid that can be view on form. The current limitation are as below, 75 fields 10 Grids 5 Tabs Description: This limitation is put to increase the performance of CRM while using on phone or tables but what If you are using CRM online and you have more than 75 fields on the form than you will not be able to see the fields which falls after that on tablets. Similarly, if you have more than 5 tabs than you will able see only first 5 tab in the tablets. Solution: CRM includes organization settings that can increase these limits. These changes cannot be done directly. You can change these settings using the OrgDBOrgSettings tool, available with any update rollup download. You can download the tool from given link: https://orgdborgsettings.codeplex.com/ You need to import the managed solution into the CRM and Once the import is successful you will able to see the solution. Open the solution and you will able to see the organization setting cannot be changes directly We will change the setting for the for the tablet setting as shown below You can change the setting as below Max fields =500 Max grids=50 Tabs=50 Hope this helps, while designing tablets forms  

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. I use the Outlook Web Application (OWA) for my O365 email access. I also have CRM open in another tab and usually toggle between CRM and email. There are several email conversations that happen with existing customers or partners that I would like to quickly track as a Lead in CRM. I might not know the timeline or even the budget, but I know since it is an existing customer/partner, this would be a good lead. The disadvantage of not tracking these potential opportunities is that after a while you tend to forget to follow up! In this article, we focus on leveraging the D365 App for Outlook to convert emails into Leads which then feeds into our Sales Pipeline. Step 1 – Hit that “D” hard D365 now has a cool new logo (not a logo, may be an icon?). Anyways, once you install D365 App for Outlook, you will see this logo next to any email you have received. Below is an email I received this morning from our partner, on a potential opportunity – Step 2 – Track the Email and Create a Lead! Once you ‘hit the D’. you get to this window, where you would ‘Track’ that email. I already have Andy Neal as a contact in my system, so the app gets me all that info right in my email window! Once you track the email, you will get an option to set the regarding option. On this screen, select New and select Lead – Finally, enter the details for your Lead and close the window or open that Lead right from your email! Step 3 – Just do it. Yes, this step is same as in my previous article. Get in the habit of doing this and you will see a good lead pipeline that you can work through daily and increase your conversion rates. 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.

Problem Statement: User Syncs data in Field Service Mobile App for first time a large data transfer happens and it takes a long time may be around hours depending on data in D365 Field Service. This blog will explain how to filter data been stored in Mobile and save time for data transfer while syncing. Solution: Below are steps to filter data explained with scenario for displaying only Work Order assigned to Login User. 1. Select “Work Order” Entity and click button “Sync Filter” as highlighted in below screenshot 2. Click “Add Condition” button as shown below 3. Click “Save & Close” button after conditions are developed. 4. Publish Solution. Conclusion: Sync Filter saves data stored in Mobile and time for syncing. We need to create Sync Filter for all business entities.