Introduction: If your organization uses forms to collect sensitive information, Document Fingerprint makes it easier for you to protect this information by identifying standard forms that are used throughout your organization. Document Fingerprint is a feature of Data Loss Prevention that converts a standard form into a sensitive information type which you can use to define DLP Policies. Working: Documents have unique word patterns. When you upload a file, the DLP agent identifies the unique word pattern in the document and creates a document fingerprint based on that pattern and uses that document fingerprint to detect outbound documents containing the same pattern. Limitation: Document Fingerprint DLP agent will not detect sensitive information in the following cases: Password protected files Files that contain only images Documents that don’t contain all the text from the original form used to create document fingerprint. To upload a blank form: Go to Exchange Admin Center > Compliance Management > Data Loss Prevention. Click Manage document fingerprints. Click + New, provide a Name and Description. The name you choose will appear in the sensitive information types list. Click Add + to upload a form. Choose a Form and click Open. Click Save. The Document Fingerprint is now part of your sensitive information types, and you can add it to a DLP policy . Creating a rule in DLP policy: Go to Compliance Management > Data Loss Prevention. Click + New, choose custom DLP policy. Provide a Name and Description for DLP policy, Enable the state of the DLP policy and Enforce the policy. Click Save. New created DLP policy will be shown. Click Edit and go to Rules > Create a new rule. Add a Condition, so that if this (Employee Information Form) sensitive info type is sent to the external Recipient. Depending upon your organization requirement add an Action, that it will block the message, but sender can override and can send the documents to external recipient if there is a business requirement. Fill out the other properties of this rule as per your requirements and Save. So, whenever a user will try to send a form which has been managed by Document Fingerprint to external contacts the results will be as below. Conclusion: In this way you can secure and monitor the sensitive information from leaking outside your organization.

Introduction: In this blog article, we will learn how to create entity Store in Dynamics 365 For Finance and Operations. Steps: 1. Add new Items 2. Under Dynamics 365 items –> Analytics –>Aggregate Measure. 3. Assign a table to the aggregate measure. 4. Add Measures to the aggregate Measure . Mention the field and Set appropriate properties of the measure. 5. Create a new dimension. 6. Assign a table or view to your Dimension. 7. Now from the solution explorer drag the newly created dimension to the aggregate measurement. The aggregate dimension will have system generated dimensions already present by default. Select the dimensional field and make appropriate relations. Save the Project. Clean and rebuild the project. Synchronize the database . This entity store will be available under entity store in Dynamics 365 for Finance and Operations.

Introduction: This blog demonstrates how to modify the non-key fields with respect to the key fields. Pre-requisites: NAV 2017 Demonstration: Generally, when modifying the records, the syntax used is Record.FieldName := New_Value; Record.MODIFY(TRUE); In order to do modify the Key fields of the table, we need to know the order in which the keys are assigned. To modify the primary key, the syntax used is Record.RENAME(Key1,Key2,Key3); Where, Key1 corresponds to value that is supposed to be assigned to ‘No.’ field. Key2 corresponds to value that is supposed to be assigned to ‘LineNo.’ field. Key3 corresponds to value that is supposed to be assigned to ‘Leased to Driver No.’ field. Even when the single key field is to be changed, all the key fields should be present in their sequential order. If there is any mismatch in the number of keys, NAV throws the following runtime error. Note: Renaming operation is a costly operation. Creating a New record and Deleting the old record is faster as compared to Rename. In case where the performance is the requirement, the second method is preferred.

Introduction: This blog explains how a Technician can register Payments done by Customer during visit of Field Service. Scenario: We often get enquiry from Clients do we have option to register Payments done by Customer in D365 Field Service this as can achived as explained below. Details: Technician should create a record of Payments on Work Order in Field Service Mobile App as detailed below. 1. Open Work Order. 2. Click “More” and select Tab of Payments as highlighted below. 3. Create a record of Payment and fill the details as shown below. Note: OOB Payment Type are Case, Check, Credit Cards and Other. Conclusion: This blog explains how Technicians can register Payments done by Customer for Work Order in Field Service Mobile App. Also Payments will be reflected in Invoice by creating records of Payment Details which will be explained in next blog.

Overview: Often you miss doing your time entries in PSA for the work done and go on a leave! You either then need to just struggle to find a system and do it yourself or raise some other kind of request to make sure billing is done right. But, you can delegate time entries to a colleague and it is all taken care of. Assigning Delegates in PSA: In Project Service, you can see the entity Delegates. In this entity, all you need to do is create a Delegate record as shown below You can either delegate a fellow resource for Time Entries or for the Expense entries. In this case, I’ll let Somesh make Time Entries on my behalf and hence make him my Delegate in PSA for a week on which I’m on PTO. Entering Time Entries as Delegates: Now, looking at Somesh’s angle, if he has needs to make time entries on my behalf. He would need to go to Time Entries, then he will need to look at the ribbon for his name and change the user to Priyesh Wagh. Once the other user is selected, their Timesheet appears and all the time entries by the other user appear. Here, Somesh can make time entries just as he would usually do for himself and they would actually be registered for the Resource Priyesh Wagh.

Introduction: In D365 Operations, when we create a workflow for Purchase Order we face a formatter error related to Time zone. This error is caused due to conflict as same time zone specified twice for a legal entity. First for the legal entity and second time for the address. In this blog, I will tell you how to resolve it. Solution: Go to Organization Administration -> Legal Entities In Address Tab, select More options -> Advanced In General Tab, Edit the Time zone to a different time zone.

Introduction: This blog explains how to open  report from custom ribbon button on entity form. Steps to be followed: 1. Add custom button on entity form using Ribbon Workbench. (If you don’t have ribbon workbench solution installed, you can install it from here. ) 2. Once button is added on form, navigate to the Quote entity and run the report. Take note of the URL, it should look something like this. (I am doing it for quote entity) URL: https://portals1.crm.dynamics.com/crmreports/viewer/viewer.aspx?action=run&context=records&helpID=Quote.rdl&id=%7b18c85c59-7d04-e711-80e6-00155db8652a%7d&records=%7bBD891D3F-C92C-E811-A831-000D3A37CC26%7d&recordstype=1084 Specifically note the items I’ve bolded, these are the report name, report unique identifier, and the entity type code of the main entity. 3. code to our new JavaScript web resource. function OpenQuoteReport() { debugger; var rdlName = “Quote.rdl”; //Replace with your report name var entityType = “1084”; //Replace var entityGuid = Xrm.Page.data.entity.getId(); var reportGuid = “18C85C59-7D04-E711-80E6-00155DB8652A”; //Replace with your report guid var url = Xrm.Page.context.getClientUrl() + “/crmreports/viewer/viewer.aspx?action=run&context=records&helpID=” + rdlName + “&id={” + reportGuid + “}&records=” + entityGuid + “&recordstype=” + entityType; window.open(url, null, 800, 600, true, false, null); } 4. Create Command i.e. add JavaScript web resource to the button using Ribbon Workbench. 5. Add command on button. 6. Publish. 7. Now go to Quote entity and click on the custom button which you have created, your report will get open.

Introduction: In this blog we will see how to create a marketing email in Dynamics 365 for marketing preview. Dynamics 365 for marketing provides an easy drag and drop tool to design marketing emails with dynamic personalized content. Implementation: Step 1: We navigate to Marketing Emails and Click on New. We can see there are a number of pre defined email templates The templates are also categorized by purpose Step 2:  At the top of the page we see three required fields Name, Subject and Form. The Name is the internal name for the designed email, Subject is the message that will be displayed in the emails subject and the From is the Dynamics 365 user who email recipients will see as the sender Step 3: In the toolbox we can see content blocks which can be used to design the email. We can add text, images , buttons etc as shown below. We can also add Surveys and Marketing Pages to the email which creates a button and on click the user is navigated to the Survey form and marketing page respectively. Step 4:  The assist-edit button </> can be used to add dynamic content to the email. Step 5: Once the email is designed as per the requirement in the HTML tab we can see the code is auto-generated. In the preview tab we can see how the email would look in different clients like Desktops, Tablets and mobiles Step 6: It is important point to note is that every email message must include both a subscription centre link and your organizations physical address. These are required by the law in many jurisdiction and Dynamics 365 wont let you publish any marketing email that doesn’t have them. Email templates include them already but when we are working with a blank template you must add them yourself. Step 7: Once the email designing is done we can check for error by clicking on the button in the navigation bar. We can also Test send the email.

Introduction: Free text invoice is useful to book sales without creating Sales order. It is used to sell a quantity of services and goods which are not inventory item. User cannot select Item in Free Text Invoice. It contains order lines that include ledger accounts, descriptions, and a sales amount. Steps: Below are the steps to create Free Text Invoice Click Accounts receivable> Invoices >  All free text invoices. On Action Pane, Click new button to create new Free text invoice. On header, select the customer account, Invoice date, currency. Other fields are non-mandatory fields. In the Invoice lines grid, enter a description, select the main account, Sales tax and enter the quantity and unit price for the invoice line. On the Line details FastTab, enter any additional information. Click on Total for check the total amount of invoice. After filling all the data, click on Post button to Post the Invoice. To check Posted Free text invoice, click on Invoice journal button. To check the ledger entry, click on view accounting button.

Introduction: In this blog, we try migrating Email Template records under Email Marketing module in ClickDimensions. ClickDimensions has many modules like Email Marketing, Analytics, Event Management etc. Under Email Marketing Module, we have entities like Email Template, Email Sends, Sent Emails, Unsubscribes and so on. While trying to migrate all the Email Templates from D365 v8.2 to v9 using TIBCO Cloud Integration, we encountered an issue. We could not find any field or entity that stored the HTML code which formed the body of the Email Template. The reason behind this issue is the HTML code is stored on the ClickDimensions side and not on ours. Therefore, in order to migrate Email Templates successfully, we need to use the Import/Export options in ClickDimensions Settings. Steps: 1. In your Source environment, go to Settings and click on ‘ClickDimensions Settings’. 2. Click on ‘Export’. 3. Select the entities you want to export and click on ‘Next’. 4. Click on ‘Export’. A .zip file will be downloaded. 5. Now, go to your Target Environment and click on Settings -> ‘ClickDimensions Settings’-> ‘Import’. 6. Click on the ‘Upload ZIP File’ button and select the file you just downloaded from the Source Environment. Click ‘Import’. Conclusion: The Email Templates will now be present in the Target System. This process did not change the GUID of the record, which is important to note as it may be required further on in the migration process. I hope this blog contributed to clearing things up when it comes to migrating Email Templates in ClickDimensions. I will be adding more blogs about migrating records in other entities of Click Dimensions soon. Stay tuned!