Latest Microsoft Dynamics 365 Blogs | CloudFronts - Page 136

Retention Tags and Policies in Exchange Online

Introduction: Messaging records management (MRM) helps organizations to manage email lifecycle and reduce legal risks associated with e-mail and other communications. MRM in exchange online is accomplished by using retention tags and policies. Retention Tags: Retention tags are used to apply retention settings to folders and individual items such as e-mail messages and voice mail. This specify how long a message remains in a mailbox and the action to be taken when the message reaches the specified retention age. When a message reaches its retention age, it’s moved to the user’s In-Place Archive or deleted. Types of Retention tags: Retention tags are classified into the following three types based on who can apply them and where in a mailbox they can be applied. Default policy tags – Applied automatically to entire mailbox. Retention policy tag – Applies automatically to a default folder. Personal tag – Manually to items and folders. Personal tags are available to Outlook web app users as a part of their retention policy. Creating retention tags: In EAC, go to Compliance center > Retention tags, and then click +. Retention tags are classified into three types, select one of the option. The New retention tag page title and options will vary depending on the type of tag you selected. Enter a name for tag, chose retention actions and period, click Save. Retention Actions: Delete and allow recovery – Allow the user to recover deleted items until the deleted items retention period for the mailbox has not reached. Move to archive – Move the message to user’s archive folder, this is applicable only for tags that are automatically applied to the entire mailbox (default) and applied by users to items & folders (Personal). Permanently delete – Purges the item from the mailbox database. Retention Policies: To apply one or more retention tags to a mailbox, you must add them to a retention policy and then apply the policy to mailboxes. A mailbox can’t have more than one retention policy. Retention tags can be linked to or unlinked from a retention policy at any time, and the changes automatically take effect for all mailboxes that have the policy applied. Creating a Retention Policy: In EAC, go to Compliance center > Retention policies, and then click +. In New Retention Policy, provide a name for the policy and click + to add retention tags. After click +, list of all the retention tags will shown and you can select from that. After linking retention tags to policy, click Save. A retention policy can contain the following tags: One DPT with the Move to Archive action One DPT with the Delete and Allow Recovery or Permanently Delete actions One DPT for voice mail messages with the Delete and Allow Recovery or Permanently Delete actions One RPT per default folder such as Inbox to delete items Any number of personal tags Default Retention Policy: Exchange Setup creates the retention policy Default MRM Policy. The Default MRM Policy is applied automatically to new mailboxes in Exchange Online. You can modify tags included in the Default MRM Policy. Place a mailbox on Retention Hold: Placing a mailbox on retention hold suspends the processing of a retention policy. Retention hold is designed for situations such as a user being on vacation or away temporarily. To set a mailbox on Retention Hold, you need to use Powershell. For placing a mailbox on Retention Hold: Command – Set-Mailbox “Uday Mane” -RetentionHoldEnabled $true To check whether the Retention Hold in enabled on a Mailbox: Command – Get-Mailbox “Uday Mane” | Select RetentionHoldEnabled To remove retention, hold from a mailbox: Command – Set-Mailbox “Uday Mane” -RetentionHoldEnabled $false Conclusion: So, this is how we can use MRM to manage email lifecycle and reduce legal risks associated with email and other communications.  

Share Story :

Resource Bookings as Calendar in D365 Field Service Portal

D365 Field Service Management stage furnishing venture organizations with instruments to smooth out their business forms – from ongoing portability over each significant gadget, to steering and work process computerization.  Make essential field administration assets, for example, item manuals, specialized help documentation, preparing, and related recordings promptly accessible to client care agents, accomplices, and field professionals.  Make work arranges straightforwardly from a case, client gateway, email, or legitimately from your CRM and track against SLAs, privileges, income and related expenses, and invoicing.  Consequently plan and allocate assets dependent on aptitudes, area, required parts, and the remaining task at hand. Courses are advanced to meet SLAs and limit drive times. CRM administration contracts assist you with keeping up guarantee and privilege data association-wide. Introduction: This blog explains how to show Resource Bookings as Calendar in D365 Field Service Portal. Steps of Implementation: 1.  Create a new Entity List in D365 Field Service for “Bookable Resource Booking” Entity as shown below 2.  Set Calendar View on Entity List as shown below 3.  Set Grid Configuration as shown below 4. After creating Web Page for Resource Booking ,Calendar will be shown as below Note: You can refer blog how to configure Web Page in D365 Online Portals by referring to this link. 5. Booking Details can be shown as below Conclusion: Above description in blog enables configuring Calendars in D365 Online Portals. Default Calendar View depends on the field value of “Initial View” in Settings header of Entity List below is view by Month setting.

Share Story :

Power BI new Visual : Ribbon Chart

Posted On September 25, 2017 by Admin Posted in

Introduction: In this blog article, we will explain about the new Visual of Power BI: Ribbon chart! Ribbon Chart: The visual is like a stacked column chart, but each column’s inner categories are sorted according to their rank for that column. Additionally, the inner categories are connected by ribbons across the columns. Refer below Screen Captured: You’ll find this new chart option to the right of the combo chart. The chart’s field well and formatting options are the same as a stacked column chart with some extra formatting options for the ribbons. There’s a Ribbon card in the formatting pane that lets you control the ribbon style: Spacing between ribbons – You can use this option to set a gap width between the ribbons. By default, there is no spacing. Match series color for ribbons – By default, the colour of the ribbons is to match the category’s color, but you can turn this off and the ribbons will be grey in color. Transparency for ribbons – You can control the transparency of the ribbon’s color. By default, it is set to 30. Border for ribbons – By default, the ribbons don’t have a border, but you can turn borders on.  

Share Story :

Steps to create and use a Client Control Add-in in Microsoft Dynamics NAV

Since integrating your ERP takes time and resources, you want to make sure the project is worth it before you dive in. There are many common signs that indicate that you need microsoft dynamics nav upgrade . Without integration, retailers rely on manually entering the same data into multiple systems. If you have teams or individuals solely dedicated to spending hours manually moving data, then you’re ready for automation. All these hours moving the data yourself could be better spent, like improving your customer experience. Relying on manual data entry is also more prone to human mistakes. All it takes is a typo in one system to offset your data. Bad data can lead to inconsistent product information across sales channels, inaccurate delivery addresses for online customers, and wrong inventory counts Introduction: Microsoft Dynamics NAV control add-ins can be created using the NAV .dll assembly viz. Microsoft.Dynamics.Framework.UI.Extensibility.dll assembly. This .dll binds the NAV control add-in and the NAV environment. This control add-in has to be implemented in Visual Studio and then registered in Dynamics NAV by navigating to Control Add-ins. Pre-Requisite: Microsoft Dynamics NAV Purpose: In this article, I will be demonstrating the steps to create and use a Client control add-in in Microsoft Dynamics NAV. Procedure: Open Visual Studio. Create a new C# class library project and add a reference to the Dynamics.Framework.UI.Extensibility.dllassembly. This assembly is present in the following directory: C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client. In the Visual Studio project namespace, create a new interface and add code for the control add in. The code is mentioned below:[ControlAddInExport(“NAVaddin”)] The name ‘NAVaddin’ will be used while registering the control add-in in Dynamics NAV. Now you need to sign the assembly. Navigate to properties->Signing->select Sign the assembly. In the Choose a strong name key file drop down list, select ‘New’. In the Key File name enter an appropriate name and clear the ‘Protect my key file with a password’ check box. The next step is to generate a unique public key in Visual Studio for the project as this public key is required while registering the control add-in in Dynamics NAV. Navigate to Tools->External Tools. Parameters to be filled are as below: Title: Get &PublicKey Command: C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\sn.exe Arguments: Get &PublicKey Now, ‘Get PublicKey’ will appear as an option under Tools which on clicking will generate the public key for the project. After clicking ‘Get PublicKey’->the public key is generated and displayed as below: Save and Build the solution. After successful build of the project, the .dll file will be generated.   Creating the Resource .Zip File.You must create a single .zip file containing manifest and any of the resource files used in Visual Studio. This .zip file has to be used while registering the .dll in Dynamics NAV. The next step will be to copy the .dll file to two locations in Dynamics NAV as given below: C:\Program Files\Microsoft Dynamics NAV\100\Service\Add-ins C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\Add-ins Go to NAV administration and restart NAV services so that the changes are reflected. Navigate to ‘Control Add-ins’ in NAV windows client and create a new Control add-in. Add the same control add-in name which is mentioned is step 2: Click on ‘Import’ action to import the .zip file containing all the Visual studio resources as created in step 7. After performing these steps, the client control add-in will be registered in Dynamics NAV and the triggers defined in Visual Studio, if any will be visible in the NAV Development environment if the Control add-in is selected in the properties of the control. Conclusion: Using this procedure, you can create complex functionalities in Visual Studio and use the .dll control add-in file in Dynamics NAV. I have created SMS functionality from NAV and Digital Signature functionality in NAV using the above procedure of adding a client control add-in.

Share Story :

Integrating Twilio Web Service with D365 CRM Online to send SMS Messages

Disconnected systems cause your business processes to be inefficient. How quickly can you get new products up on your eCommerce store? How long does it take you to update inventory counts? When these processes are too slow, it negatively impacts your performance. You can’t keep up with your competitors. Overall, these issues can lead to poor customer experience. You won’t be able to process orders quickly enough or give customers the accurate information they need to make a purchase. Coordinating with CRM NAV integration permits you to consequently synchronize information between your ERP and different frameworks. You don’t need to contact any catches. You get the opportunity to characterize rules on how information is shared by your operational needs. Introduction: SMS Messages can be sent from a D365 CRM Online to an individual using the Twilio Web Services. In this blog, we will see how can we send SMS Messages from CRM using Twilio Web Service Scenario: We will create a message record from CRM which on save will call the Twilio web service via a plugin and send the message to the destination based on the information passed to Twilio from the D365 CRM. Process: Step 1: Creating Entities Create the following 2 Entities which are ‘SMS Configuration’ and ‘SMS Message’. The SMS Config entity will only consist of three fields which are Username which will have the value of ‘Account Sid’. Password which will have the value of ‘Authentication Key’. From which will have the value of Twilio ‘Account Phone number’. The SMS Message entity will consist of the following two fields which are as follows To which will have the value of the ‘Receiver’s Phone number’. Message Body which will have the value of the ‘Message text’ that the receiver will receive.  **Note: The purpose is to provide dynamic data and to not hardcode any value. Step 2: Creating Plugin Code to Call the Twilio Web Service The plugin code will be consisting of two main code blocks: Web Service Code Block Main Execute Code Block Web Service Code Block We will be using the Web Service code in our plugin code while calling the Twilio Web Service from CRM. For more information on how to call Web Service using plugin refer the following link : https://www.cloudfronts.com/call-web-service-plugin-dynamics-crm/ In this case we need to make modifications to the Web Call Service function block of the Web Service plugin code. Changes made to the ‘Try Block’ of the Web Service Call. We won’t require to make any changes to the WebClientEx code block of the Web Service Call Code. Main Execute Code Block In the Main Execute Code Block we will be calling the above Web Service Code Block. Retrieving of the SMS Configuration Record can be done using fetch XML method. Conclusion: Thus, in this way we can send SMS Messages from D365 CRM Online using Twilio Web Services. Hope you find this helpful.

Share Story :

Web Client UI Refresh: D365 v9

Overview: The new July 2017 update of the D365 is the latest update to Dynamics 365 and is called v9. This is a major change from not only functionality perspective but also from a visual perspective as well. And one such part of the visual upgrade is the refreshed web client UI. This is a major change since it’s 2013 Online version! What has changed: The traditional UI has been redesigned to appear more intuitive and eliminate issues with the previous UI. Some of the changes are: Removal of White Spaces: They’ve removed all the extra white spaces from the current version making the UI look more occupied and tightly bound. As you can see in the screenshot above. Boxes have been added to house the sections on the form. This makes the white spaces disappear making the UI look more occupied. In the previous UI, the short length of fields and unexpanded subgrids used to leave a lot of white space causing a disjoint in the UI. That has been taken care of here. Word Wrap Fields: With the new refreshed UI, the lengthy field names are taken care of. In the previous version, the lengthy field labels used to disappear behind the field making it a hassle to hover over the label and read the name of the field. With the new UI, the field labels are not wrapped and if you have lengthy field labels, the entire text is seen as below: Color Coded Subgrid on Form: Further, they’ve enhanced on how sub-grids should appear on the form. Example, if you have a  lot of sub-grids on the form and you need to read to know which sub-grid is where. Now, you can have colored Sub-grid headers that give you a visual feedback of what entity sub-grid it is. See sample screenshot below: As seen above, I can have a uniform color for Contact across all forms where I have Contact subg-grid. This is available only on the form level. The color can be modified from the Sub-grid properties on the Form as shown below: Other Improvements: Along with these, there are other significant improvements that can be seen across the new UI: Improved Form tab formatting. Standardise fonts. The new UI looks promising and will provide an easier visual feel.

Share Story :

CRM Tip: Automatically Creating document from Word Template and attaching to Record

Background: In Dynamics CRM, one of the common requirement customer have is to Run a report and save the copy of the report (PDF/ Word/ Excel) as notes/ attachment on the record or send the created document as email attachment to customer. Sounds an innocent requirement, right? With CRM online, it is NOT. What we do to achieve this till now We do one of the following when the customer asks this request: Ask user to manually run report, download PDF and create email record or attach to record notes. Use some paid 3rd party tool. Tell the customer it is not possible For CRM Online. 😀 For On-prem CRM, developers would tweak the Report Viewer and somehow manage to achieve this with lot of effort and custom plugins. Alternative: With Dynamics 365, you have one alternative which does not exactly give you the above solution but is very close or may be acceptable adjustment to client. We all know CRM 2016 also introduced word templates. But with D365, CRM has inbuilt Action to Run a word template and attach that to document without user action. Since it is an action, it can be used in Workflows, Plugins, other actions and even in JavaScript using Web API. Example: I have created a workflow on Account Credit limit update, such that when credit limit is more than 10,000 an Account summary will be created using the Account Summary template and attached to the record. See screenshots below of the workflow and generated document. All this without user intervention. Limitations: We cannot create PDF documents using this approach This is limited to Word templates and they are not yet as powerful as SSRS reports Next Steps: We can extend this functionality by may be having plugin on notes creation to send an email to customer or any other thing? Please post your comments/ suggestions below. Happy CRM’ing

Share Story :

Business Process Flow enhancements- Dynamics 365 v9.0

Introduction: In this blog, we will have a look on new updates on Business Process flow. Previous Release Updates: Business Process Type Run process as a task flow (Mobile) Run process as a business flow (Other clients) New Designer New Toolbar introduced with edit buttons, connector, new snapshot button to take screenshots of your business process flow design which can be used in technical documentations Security Note:  Your process will not show up in this tab until you Activate the process.  If you Deactivate it after updating security roles, the process will remain in the available in this tab so you will NOT need to go back and update your security roles again.  It’ll only be removed from the security role tab once you delete the process. Action Workflows Stages can execute workflows with a trigger of Stage Entry, or Stage Exit. Example: You can have the completion of a specific Business Process on an opportunity kick off a workflow that creates a Case, and activates a Business Process on that newly created Case. Stage Active Duration Out of Box feature, to see duration details in BPF- Total time for the BPF being in active state Additional Status Reasons available – Abandon, Finish Maximum number of processes, stages, and steps To ensure acceptable performance and the usability of the user interface, there are some limitations you need to be aware of when you plan to use business process flows: There can be no more than 10 activated business process flow processes per entity. Each process can contain no more than 30 stages. Multi-entity processes can contain no more than five entities. New Release Dynamics 365 July 2017 Update: Business Process Flow entities are now available on Site Maps, Views, Charts: Now the BPF are available in the form of entities and personalized views can be created and we do not need to write any code for getting the BPF in particular stage. Sales BPF will be visible in Sales area and Service BPF will be available in Service area. Site Maps Views Charts Action Steps: Calling an on-demand workflow or a process action from within the Business Process. Action will appear on the UI in the form of a button Business Process Flow in Unified Interface: Different stages of Business Process Flow When you click on pin the stage, the stage is pinned on the right side of the screen and we can see for how much duration the stage was in active stage as shown below The activity duration of the stages is visible even on the Business Process Flow Hope you like the new feature of Business Process flows with some new required functionalities.

Share Story :

Creating Learning Path for Dynamics 365

Posted On September 22, 2017 by Admin Posted in

Introduction: This blog explains how to add learning path to your solution. Prerequisites: Dynamics 365 (online – latest version, or Dec 2016 update installed). Steps to be followed: Steps for enabling learning path Steps for adding users to Learning Path Authors Creating Learning Path content Stpes to create Guided Task Steps to create Sidebar 1. Steps for enabling learning path: Opt-in to Learning path by going to Settings->Administration->System settings (under General tab). Select Yes for Enable Learning Path and Enable Learning Path Authoring. Confirm that Use Custom Help for customizable entities and Append parameters to URL are set to No. OK. 2. Steps for adding users to Learning Path Authors: Go to Admin Portal. In Admin center Groups->Learning Path Authors security group. Click Edit in the Owner row to add owner of the group. Click + Add Owner, and then select the user from list or search for the user(s). Click Edit in the Members row to add users to the group. Click + Add members, and then select the user from list or search for the user(s) you want to add to the group. Save and close. 3. Steps for Creating Learning Path content: Go to help. Click on content library button Content Library will open. There are two types of learning path content: Guided Task: Interactive “bubbles” which form a sequence to provide help or guide users on specific tasks. Sidebar: Vertically formatted help content, which is initially shown as a “table of content” with items that the user can expand, revealing relevant webpages, videos, or links to existing guided paths content in Dynamics 365. 4. Steps to create Guided Task: Click on + Guided Task to create a new Guided Task. Fill Details. Save. Click on + Add New Steps to add steps to your Guided Task. Step with Next Button: This step has a Next button that can be used to navigate to the next step in the flow. Step with User action: This step does not have a Next button. The user is prompted to click the UI element on which the step is pinned. User action with Next Button: This step does have a Next button. Clicking the Next button has the same effect as clicking the UI element on which the step is pinned. Learning Step: This step can only be at the end of a guided task flow. Drag and drop the step where you want. Give step title. Click on content type to add content it can be text or video. Save. Repeat step number 5 until all steps are added. Click on Preview to see how it will work before publishing. Click on publish select your publishing environment. Output of Guided Task:   5. Steps to create Sidebar Click on + Sidebar to create a new Sidebar. Fill Details. Save. Select the section and add what type of content you want to add in that. Repeat step number 4 to add more sections to sidebar. Click on Preview to see how it will look. Click on publish select your publishing environment. Output of Sidebar: Conclusion: Using learning path newly created  users can easily navigate through the system with ease. It provides basic guidance to the users.

Share Story :

Access Teams

Introduction: In this blog, I will be giving an overview about access teams and a quick demonstration of the same. Brief Description : Access teams provides a way to share records between different functional teams without having to change or update the base security rule in Security roles. Access teams does not mean ownership of the record. The record is only shared so that other users can work on it. Scenario: There are two sales teams “Sales India” and “Sales US” in different business units.The users of both the teams can read the whole organizations data but can write/edit data to only those users data who are in the same business unit.Here if one team member of “Sales US” wants to write/edit a record of “Sales India” it is not possible. This is where access teams comes in the picture. Some users from “Sales US” can be given access to write/edit records of “Sales India” Steps: Step 1: There are two business units “Sales India”  and “Sales US” Step 2: Tom is a part of “Sales India Team” and Harry is a part of  “Sales US Team”. Step 3: Assigned both the users a custom role in which they can do the following as shown below: Read account records of the whole organization Create records at user level Write/edit records at business unit level Step 4: Now to enable access team we must navigate to entity for which access teams needs to be enabled as shown in figure below Here we go to Accounts entity and enable Access Teams then to save the changes made publish all the customization. Step 5: To use access teams we first create an access team template by navigating to Setting > Security > Access Team Templates Step 6: Here create a new template with an appropriate name and select the Access Rights and the Entity as shown in the figure below. Note:The entities field on which Acess Teams are enabled only those entities will be shown in the Entity field dropdown. By adding users, you are granting them the access rights to that record that are defined within the access team template, even if their base security role does NOT grant them those rights. Note, the access rights are ONLY being granted for that specific record. Step 7: Now we add a Sub grid on the Accounts main form so that the users can be added to the access team on the fly. Here in the Team Template field select the template made for the access team. After setting up the subgrid Save and Publish all the Customizations. Step 8: Harry is the owner of two records(Crook Motor Company & Lamborghini) as shown below. Tom is the owner of one record(Tata Motors) as shown below Step 9: Harry can view every record in the organization but cannot write/edit. As seen below harry can only read record created by Tom. Step 10: Now as harry wants to write/edit this particular record, the admin has to add him in the access team sub-grid to give him access to write to this record. Step 11: Now Harry can write/edit to that particular record as shown below. Conclusion: Using this technique we can easily make different user access teams and assign specific records to work on without having to deal with their base security roles.

Share Story :

SEARCH BLOGS:

FOLLOW CLOUDFRONTS BLOG :


Secured By miniOrange