D365 App for Outlook Sitemap Edit
Dynamics 365 application development provides an end-to-end solution for your business right from design, development, appsource listing upto enhancements and support. The team has a set of expert developers, architects and technicians who are involved 24*7 in the process to enhance your business and take it to the next level. The team understands your business needs initially and then starts working on the goals for the betterment of your business. Based on the case scenarios, applications are designed and developed that could be easily fitted and implemented on to your business model. While Dynamics 365 is taking care of your business needs through cloud, you can focus on your core business strategies, needs and allocate time to your clients making a better relationship with them for enhanced business. Introduction: In this blog we will discuss how we can add entities to the by default App for Outlook look while we track emails using App for Outlook. Steps: By default, the App for Outlook does not show any entities in its sitemap. As we all know that there is new concept of Apps in MSCRM. We can develop Apps so that we can give users a limited and required access to entities. Every module in CRM is now a app like Field Service App, Project Service App, Service App. Similarly there is App for Outlook App. Below is the default sitemap for App for Outlook. You can add Area, Sub area and groups to the default sitemap and publish the changes. Below is the screenshot after addition of required area, sub areas and groups. This is how you can change the entities visible in D365 App for outlook.
Share Story :
Create Leads when Email is received to the Queue
Introduction: This blog explains how to Create Leads when Email is received to the Queue. Creating Queue in MS CRM: Settings -> Service Management -> Queues Click on “+NEW” Enter Name and Incoming Email for the Queue. Save record. After Saving the record Mailbox will be created for the Queue. Configuring the Mailbox Open the Mailbox Click on Approve Email Click on Test & Enable Mailbox After Configuring Successfully, you can see Status as Success for Incoming and Outgoing Email. Create Workflow to Create Lead: Go to Settings -> Processes Create new process. Select Entity: Email Below is the Workflow: To set the regarding of email. Click on Set Properties of Update Email Step. Click on Set Properties of Create Lead Step and add details in fields. After Writing all the steps Activate the workflow.
Share Story :
Power BI – Row Level Security
Microsoft Power Bi enables you to find and visualize data, share your findings and collaborate in the modern ways in the form of reports and dashboards. In short, it is a collection of online services and features to enhance your business. Power bi support allows you to migrate huge data from various sites into power bi desktop using the integration process. You can easily edit the data or you can also plan to edit it later after you have imported it on your desktop. Power bi helps you to overcome all your business problems with ease making you stay up-to-date with all necessary and relevant information that is of utmost value for you. The team of experts involved have a huge experience in working with all kinds of businesses across the world. Introduction: Row-level security (RLS) with Power BI can be used to restrict data access for given users. Filters restrict data access at the row level, and you can define filters within roles. Steps: To create on a Power BI Solution, you will start by going to the Modellingribbon and then select Manage Roles. This will launch the Manage roles window where you will select Createto add a new role. After you give the role a new name you can begin assigning DAX filter expressions to it. Click the ellipsis next to the table you would like to apply the filter to and then select Add filter. If you select Hide all rows,then all rows for this table will be hidden (as the name implies) but if you choose a field you can apply a filter to specific values in the table. Once you are happy with your selection, hit Save. To test the security model, go back to the Modellingribbon and select View As Roles. Here you can select the role you want to test and then click OK. This will filter the result to only show your selected roles filters. To stop impersonating this role you can click Stop Viewingto return to seeing the results without this filter applied. The next step is to assign users to the roles, which must be done from the Power BI Service That means you must deploy your model to the Power BI Service first. To do that go to the Homeribbon and select Publish. Once you’ve published to the service login to Power.com and click on the ellipsis next to the dataset you just deployed. In this menu you will select Security. Next, select the role you created and enter the email addresses of the users you would like to have the role assigned to. Click Add after you’ve entered all the users. Once you click Saveon the bottom your security is ready to go! To test it out click the ellipsis next to the role name and select Test as role. This will allow you to now view reports while impersonating this newly created role.
Share Story :
Show Company Insights V 4.2 for Custom Form in D365 Customer Engagement
Introduction: This blog details steps for displaying Company Insights V 4.2 for Custom Form in D365 Customer Engagement. Pre-requisites: 1. Company Insights solution installed with version 4.2 2. Custom Form for Entity Steps: Below are steps to configure Company Insights on custom form “FSA Account” for Account Entity 1. Open custom form “FSA Account” 2. Insert new section and label as Insights 3. Insert new web resource as detailed below Select Webresource – “iv_/webpages/summary_mashup.htm”. Insert details in Custom Parameter(data) – “solutionVersion=4.2&crm_version=v140”. Check setting – Pass record object Type code. 4. Insert new Navigation Link for Insights in Common area as detailed below. Set Name as “Insights”. Select Icon – “iv_/images/insights_32px.png”. Select WebResource – “iv_/webpages/detail_mashup.htm”. 5. Add new Parameter in Form Properties with below details. Set Name as “iv_onLoadAction”. Set Type as “SafeString”. 6. Publish Custom Form and Company Insights is rendered as below. Note : If User skips step 4 will get error – “You do not have the ‘ISV Extensions’ privilege assigned to your security role”. Conclusion: Hope this blogs helps CRM Administrators to enable Company Insights V 4.2 on Custom Form in D365 Customer Engagement with no errors.
Share Story :
Installation Process for Microsoft Dynamics 365 Business Central (Business Central On-Premise Partner Preview 02).
With more than 1 lakh 60 thousand customers worldwide, dynamics 365 business central development has surely established itself in the market quite well. It is one of the most widely used ERP systems in the world market currently and specifically targets small and mid-sized businesses which are sold across 195 countries. Recently, Microsoft has migrated Dynamics NAV to Dynamics 365 business central by expanding it. This application is designed keeping in mind the ongoing transformation of businesses to cloud-computing. One of the good things about business central apps is that it is available on-premise as well apart from being available on cloud. In terms of migration, very less effort is required to migrate to business central as both Dynamics NAV and business central contain the same code. Introduction: Finally the Developer preview version for Business Central is out. This blog basically gives an idea about the installation process and the basic difference in the process from Microsoft Dynamics NAV 2018. Pre-requisites: Access Microsoft: Ready-to-Go Program/Collaborate Microsoft Dynamics 365 Business Central (Business Central On-Premise Partner Preview 02) Demonstration: Download the setup file on the basis of your region(localization if available) or the world version (if localization is not available) and run the setup file. Click on next and choose the type of installation as per you work needs. You can choose an free online trial, or download the business central application from the Microsoft store and download it on your PC/Tablet/Laptops etc thus having an access to it from any location. The advanced installation options allows you to download Business Central on your computer or local server. The .NET Framework required for the Microsoft Dynamics 365 Business Central is downloaded first. After that restart your PC/Server. Run the setup again, this will download the Web Client and Business Central Administration. The latest version of the web client can be seen with all the latest functionalities. Now to add the Windows Client, go to add or remove components in the setup and add the required components (Dynamics NAV Client etc). This is the difference from Microsoft Dynamics NAV 2018 where you did not have to add the windows client as a separate component. The installation has been completed now. Now, you can open the Windows Client which has an interface similar to that of Microsoft Dynamics NAV 2018. Conclusion: This is the process for the installation and the basic differences from the Microsoft Dynamics NAV 2018 installation have also been noted. In the next blog, I will provide the further differences in the Administration, updations in web client etc.
Share Story :
Work Hours in CRM
In this article, we will learn how we can leverage the work hours in Reporting. The calendar entity stores data for customer service calendars and holiday schedules in addition to business. Each calendar is set for a specific time zone. A calendar describes the availability of a service or a resource. Calendars are related to calendarrule records, which include details about the duration, start and end times, and recurring patterns of events included in the calendar. There are two types of calendar rules in Microsoft Dynamics 365: Root: A calendar rule that contains an inner calendar or that has nested (leaf) rules. You can specify an inner calendar for a root calendar rule by using the InnerCalendarId attribute. The attribute value of CalendarRule.InnerCalendarId of a root rule is the same as the attribute value of CalendarRule.CalendarId of its leaf rules. Leaf: A calendar rule that doesn’t contain an inner calendar, and therefore, is the end of the “branch.” Referred from Blog: https://msdn.microsoft.com/en-us/library/gg328538.aspx To obtain Work Hours of a resource, you can use the following fetchxml code: <fetch version=”1.0″ output-format=”xml-platform” mapping=”logical” > <entity name=”bookableresource”> <!– You can use systemuser to retrieve same data –> <link-entity name=”calendar” from=”calendarid” to=”calendarid” alias=”c” > <link-entity name=”calendarrule” from=”calendarid” to=”calendarid” alias=”cr” > <attribute name=”starttime” /> <attribute name=”effectiveintervalend” /> <filter type=”or” > <!– These filters are applied to get calendar of this year only –> <condition attribute=”starttime” operator=”this-year” /> <condition attribute=”effectiveintervalend” operator=”this-year” /> <condition attribute=”effectiveintervalend” operator=”ge” value=”12/30/9999″ /> <!– 12/30/9999 is the max end date i.e infinite time –> </filter> <link-entity name=”calendar” from=”calendarid” to=”innercalendarid” alias=”inc” > <link-entity name=”calendarrule” from=”calendarid” to=”calendarid” alias=”incr” > <attribute name=”duration” /> <filter> <condition attribute=”duration” operator=”lt” value=”1440″ /> <!– 1440 minutes equals 24 hours which is redundant. As the calendar includes Business Closures and holidays we want to avoid such calendar records –> </filter> </link-entity> </link-entity> </link-entity> </link-entity> </fetch>
Share Story :
How to Export and Import Voice of the Customer Surveys
Introduction: This blog explains how to Export and Import Voice of the Customer Surveys. Steps to be followed: Step 1 : Go to the Survey that you want to export. (survey should be in published state) Step 2 : Navigate to Notes section and download both the files. Step 3 : Navigate to your destination environment where you want to import the survey. Go to Settings -> VOC Settings -> VOC Imports Click New Enter name for the import Open the download Survey Stored xml file with notepad and copy and paste the content in Survey XML to import. Save the record Step 4 : You can see the imported survey in Draft state. Open the record. Delete the automatically created Translations file from Notes section. Attach the downloaded Translation file in notes. Step 5 : Publish the survey.
Share Story :
Integrating Twilio with D365 CRM Online to send SMS Messages using Microsoft Flow
One of the most popular ERP systems that is amazingly popular among all small and mid sized businesses is Microsoft dynamics NAV integration. Installing CRM NAV integration is extremely easy and simple and its interface is so easy to understand that anybody can learn it within no time. This is the reason NAV integration has earned a good reputation in the market and people love using it as well. In today’s cloud based environment if you upgrade dynamics NAV you will surely have an edge in your business as compared to your peers. With improved functionality enhanced capabilities and new features your business productivity will be boosted multiple times reducing your overall business cost improving customer service. Introduction: SMS Messages can be sent from a D365 CRM Online to an individual using the Twilio. In this blog, we will see how we can send SMS Messages from CRM using Twilio and we will be using Microsoft flows to achieve this. Pre-Requisites: Twilio Account D365 CRM Microsoft Flow Steps to be followed: Dynamics 365- Create two fields in Contact Entity, named as a. Send SMS b. SMS Sent Data Type (Two options) Twilio- To Connect Twilio in Microsoft Flow You require: Twilio Account Id Twilio Access Token Steps: Sign in to your Twilio account Click on Dashboards Under Project info tab you can find the Account SID and Auth Token (Copy this value and paste it somewhere you will require this values in MS Flows) Setup Phone Number. a. Click on “All Products & services” b. # Phone Numbers MS Flow Login to Microsoft flow. Select Create from Blank. Select Dynamics 365 connector.a. Select when a record is updated trigger.b. Select the organization name and Entity. Select “+New Step” and “Add a condition”a. Enter condition in “Edit in advance mode”.Condition: @and ( equals(triggerBody()?[‘cf_sendsms’], true), equals(triggerBody()?[‘new_smssent’], false) ) If Yes a. Enter Twilio Account Id which is Acoount SID and Twilio Access Token which is Auth Token. b. After Connection is being established. Enter the From and To Phone Number. Enter Text message which you want to send. Click on “Add a connection” –> Dynamics 365 – Update a record. Overall Flow:
Share Story :
CRM Option set in Power BI
Introduction: In this article, we will learn how to dynamically use Dynamics 365 CRM option set/ CRM picklist in Power BI. As you may be aware that CRM picklist stores Integer value in the backend and not the actual display name. So, whenever you query an entity with picklist fields in Power BI you will get picklist Integer value and not the display names. Pre-requisite: The option set/picklist should be a global. You can check the IsGlobal property for the picklist field in the Metadata Browser. In Metadata Browser, when you expand Get Options for OptionSet there is a (+) button. Click on that button and option set properties will appear. Steps to get Option Set Values: Login in to Power BI Click Get data Select Odata Feed as the connector Enter the OData URL for querying the Global option sets and click Ok. URL Format: https://orgname.api.crm.dynamics.com/api/data/v8.2/GlobalOptionSetDefinitions(OptionSetMetadataId) Example: https://contoso.api.crm.dynamics.com/api/data/v8.2/GlobalOptionSetDefinitions(ae2a3b9d-395a-4dbd-9abc-c32aeb10888b)Note: OptionSetMetadataId is highlighted in the Pre-requisite screen capture Once the query is loaded, the Edit Query window will pop up. Click on Advance Editor and modify the code as below (Add null and MoreColumns parameter) and then click Done: let Source = OData.Feed(“https://fasttrackleasingllc.api.crm.dynamics.com/api/data/v8.2/GlobalOptionSetDefinitions(ae2a3b9d-395a-4dbd-9abc-c32aeb10888b)”, null, [MoreColumns = true]) in Source After loading, an additional row will be added to the table named More Columns. Click on the Record field beside More Columns. A new view of the table will be loaded as shown in the below screenshot. Right Click on List and Select ‘Into Table’ Once the table is loaded, expand the Value column by clicking on ‘Expand to New Rows’ Expand the Value Column and select ‘Value’ and ‘Label’ Columns. Click Ok. Expand the Value.Label Column and select ‘UserLocalizedLabel’ Column. Click OK. Expand the Value Column and select ‘Value’ and ‘Label’ Columns. Click Ok. Finally, we get the Option set Code (Value.Value) and Option Set Value (Value.Label.UserLocalizedLabel.Label) from CRM. Conclusion: As the above method creates a separate table for option set, you have to add relationship (1-*) between the newly created Option Set table and the Main table.
Share Story :
Extend Schedule Board Filter Section in D365 Field Service/PSA
Introduction: This blog explains how to enable custom field in Filter section of Schedule Board in D365 Field Service & PSA. Scenario: Need to filter resources on Schedule Board by custom fields other than standard fields like characteristics, roles, business units, terriotries etc. Pre-requisites: Configure 2 Custom Entities with below Details 1. Crew Entity with Name as text field. 2. Crew Member Entity with Crew and Bookable Resource as lookup field. Steps: Below are steps to configure custom field “Crew” of type lookup in filter section of Schedule Board. 1. Open Schedule Board to Customize 2. Customize the Filter Layout Template Open Filter Layout as highlighted below. Insert below code above controls closing tag. <control type=”combo” source=”entity” key=”ResourceCrew” label-id=”Crew” entity=”cf_crew” multi=”true” /> Click “Save” button to save the changes to Schedule Board. Crew field will be shown in filter section as highlighted below. 3. Customize the Retrieve Resources Query. Open Query Template as highlighted below. Insert below code in Query template above closing tag of filter. Click “Save” button to save the changes to Schedule Board. 4. Click “Apply” button to save the changes to Schedule Board. 5. Select Crew and click Search button in Filter Section and Resources are filtered as below Refer this link for more information. Conclusion: This blog explains steps to filter resources based on custom entities in Filter section of Schedule Board in D365 Field Service and PSA.
