Introduction: Email can fill your Outlook Inbox quickly – new messages, replies, and forwards. Before you know it, you could have thousands of messages. Keep your Outlook inbox and its folders under control by moving older items you want to keep to an archive. Email archiving helps in saving and preserving data contained in email messages so it can be searched and accessed later. An archive mailbox is a specialized mailbox that appears alongside the users’ primary mailbox folders in Outlook or Outlook Web App. Users can access the archive in the same way that they access their primary mailboxes. Enabling In-Place Archive: For moving the mailbox items to Archive, firstly we need to enable In-place archive for that mailbox. Go to Exchange Admin Center > Recipients > Mailboxes. Select user for whom you want to enable In-place archive. You will be getting the option to enable archiving as shown in below image. After In-place archive is enabled, in the mailbox type you can see Archive in brackets (as shown in below image). Within 15 minutes, user will be able to see In-place archive folder in their mailbox which is a secondary mailbox and can be accessed as primary mailbox is accessed. Creating Retention Tag and Retention Policy: Retention Tag – Retention tags define and apply retention settings to messages and folders in a user’s mailbox. Retention tags specify how long a message is kept and the action taken when the message reaches the specified retention age. After enabling In-Place Archive, we need to move the items to archive. We can move the items by – 1. Moving the mailbox items manually. 2. Move messages using Inbox rules. 3. Move messages using retention policies. Here, we will see how to create retention tag and policy so that the mailbox items will be moved to Archive. Go to Exchange Admin Center > Compliance Management. To create a Retention Policy, firstly we need to create Retention tag and then attach that tag with a policy which is called retention policy. You will be getting 3 options to create a Retention tag – a. Default policy tag which will be applied to entire mailbox. Note – DPT will be applied to all items in the mailbox that don’t have a retention tag already applied to it. b. Retention policy tags which will be applied to a default folder, such as Inbox (Does not support Archive action). c. Personal tags which can be applied by users to items and folders. Select default policy tag. Provide a name to tag and choose the retention action which will be taken after the items reaches retention age which also needs to be mentioned in no. of days (see below image). In this case I have created a retention tag so that when the items will reach 90 days it will be moved to archive. After creating Retention tag, we need to create retention policy, provide a name to the policy and add the retention tag. After the Retention Policy is created, it needs to be assigned to the users. For the same, go to Recipients > Mailboxes. Select User and click on edit. Go to Mailbox features and apply  Retention Policy to user. It may take some time for the retention tag to appear in the mail settings > retention policies (see below image). After the Retention Policy is applied to the mailbox, the items which has reached their retention age of 90 days will start moving to In-place Archive. Note – It can take up to 7 days for the items to be moved in to In-Place Archive depending upon the number of items. Conclusion: In this way we can create Retention tag and policy for Email Archiving which will keep Outlook inbox and its folders managed by moving the older items to archive.

Objective: In NAV 2017 Emailing the PDF by running the report using Report.SAVEASPDF is now not allowed in NAV 2018. The reason is that temporary server file as not allowed to be saved for some security reasons. Thus this blog demonstrates the workaround solution for this issue. Pre-requisite: NAV 2018 Demonstration: 1. Concept: With respect to NAV 2018, Microsoft says that Emailing the attachments should be done using Streams. Thus, we’ve to convert the PDF generated by running the report into a stream and pass the stream as an attachment (https://community.dynamics.com/nav/f/34/t/270046). Before running the report, the data needs to be passed appropriately to the Report. Report.RUNMODAL method cannot be used as running report requires XML Parameters. For this, we make use of XMLParameters that are sent to the report through either a request page or as XML Text which contains a list of parameters to be passed and then the report is run. 2. Procedure: Step1: Generate the XMLParameters(Text) using the RUNREQUESTPAGE method and copy the results. REQUESTPAGE is used to set the filters prior to running the report. The filters selected are passed to the report in XML format. Value in XMLParameter: Here, Rec.Contract No. is the primary filter to be passed to the report. Step2: Create the Instream and Outstream variables and a temporary table having BLOB field. Create the OutStream variable for the BLOB field of the Temporary Table. Save the data of OutStream variable using Report.SaveAs method. Copy the data of the BLOB field to Instream Step 3: Pass the attachment as a Stream using Instream Note: Perform the Step 1 only if there is any filter to be applied to the report. Conclusion: This workaround is to be used where the Report.SAVEASPDF cannot be used because this method is not allowed in AL.

Main cause of Performance Issues: Bandwidth and latency are the primary characteristics which affects the performance of Dynamics 365 client application on the web browser and other apps like D365 for Outlook It is also important to note that even if there is high bandwidth, the performance may be still slow because of latency issues. Let us define these two terms: Bandwidth is the width or capacity of a specific communications channel. Latency is the time required for a signal to travel from one point on a network to another, and is a fixed cost between two points. An application designed to send a request, wait for a reply, send another request, wait for another reply, and so on, will wait at least five seconds for each packet exchange, regardless of the speed of the server. How to Check Latency in D365 Online Applications: Dynamics 365 includes a basic diagnostic tool that analyzes the client-to-organization connectivity and produces a report. To run the Dynamics 365 Diagnostics tool, follow these steps. On the user’s computer or device, start a web browser, and sign in to a Dynamics 365 organization. Enter the following URL, https://myorg.crm.dynamics.com/tools/diagnostics/diag.aspx, where myorg.crm.dynamics.com is the URL of your Dynamics 365 (online) organization. Click Run You can see the results like below: What to make of this? The report displays a table with test and benchmark information. Of particular importance is the Latency Test row value. This value is an average of twenty individual test runs. Generally, the lower the number, the better the performance of the client. Although users may receive a satisfactory experience by using connections with more latency, for best application performance we recommend that the value be 150 ms (milliseconds) or less Other Notes: One of the reasons of high latency is that sometimes D365 tenant is setup in a region far from the home region. For e.g. Customers in USA using D365 which is setup in Australia. This will result in high latency for the end users. In these scenarios where most of the customers are in USA, you can contact Microsoft Support to help move your tenant to USA or nearby region. Best practices for improving application performance Maximize how quickly your forms load. More information: Optimize form performance Make sure you aren’t using legacy form rendering, which can make forms take significantly longer to load. More information: System Settings dialog box – General tab

Manual For closing Blind shift in POS: Blind shifts terminate the currently ongoing shift and when logged in a new shift opens. In this blog we shall see how to close the blind shift. Steps: 1. Login to the POS 2. Open a new shift or continue with the existing one. 3. Click on Show blind closed shifts. 4. Select the shift you want to close. 5. At the bottom click on declare. 6. Declare the starting amount and the tender amount. 7. Click on close shift. This is how blind shifts can be closed.

Introduction: The feature is finally release, and it is power BI has announced general availability of persistent filters in the Power BI service. All Power BI reports will now automatically retain the filters, slicers, and other data view changes that you have made. You no longer need to spend your valuable time slicing and dicing your report and repeating the same steps each time you return to the service. With this feature, you will be able to pick up right where you left off last time and quickly get to your insights! Also, if you want to reset all the filter to the state when the report was publishing, this feature will allow you to do that. Enabling Persistent Filter: To see persistent filters in action, simply head to any Power BI report that you have view or edit access to. You will notice a new button on the top bar that says, “Reset to default”. By default, this is disabled. It essentially means that you are viewing the author’s published view of the report and have not made any changes. Once you have modified the report to the view that you like, will activate the Result to default button, and will allow you to go back to default state when it was published. Click on reset to default And you are done.  Report will be reset to the default published state. Disabling persistent Filter for report: Persistent filter is turned on by default for all reports. If you want to disable the feature for the report, then you need to use the latest power BI desktop version that is released on Feb 2018. You need to navigate to : Power BI Desktop > Options > Report Settings > Persistent Filter. This is amazing feature that allows users to interact with report as they want. Try it out and let us know if there is any issue in comments below.

Issue: Microsoft Message Queuing (MSMQ) service running on Server might be unable to receive messages. Therefore, messages stay in “Waiting to connect” state in the outgoing queue of the sending computers. Cause: Issue occurs on 2 scenarios- During computer start, MSMQ service tries to bind to machine IP for listening which is still not acquired by DHCP. This might happen when DHCP takes some time acquiring IP due to any network latency or service start timing between DHCP and MSMQ. In this case MSMQ starts listening to the loopback address i.e. 127.0.0.1. DHCP acquired IP correctly and MSMQ listening on that IP as well. However, at some later point, DHCP IP renewal happens and now machine IP is different from the last one. In this case MSMQ is still listening on the older IP. So, when a new message comes for any old IP, it is never seen by MSMQ service. Verify Scenario: In Command Prompt, type following command and check the result netstat –abno | findstr 1801 If the system is facing this problem, output resembles the following in first scenario: TCP 127.0.0.1:1801 0.0.0.0:0 LISTENING xxxx TCP [::1]:1801 [::]:0 LISTENING xxxx Output resembles the following in second scenario: TCP y.y.y.y:1801 0.0.0.0:0 LISTENING xxxx where, y.y.y.y is the IP address which MSMQ port is listening to but this is different from the IP it should listen to. Resolution: Restart Message Queuing Service If Point 1 don’t resolve the issue, Install this Metadata hotfix.  https://support.microsoft.com/en-us/hotfix/kbhotfix?kbnum=2554746&kbln=en-US

Overview: Often, we wonder what could be wrong where we see a generic error on Documents in Dynamics 365. Something like this – That’s when you wonder if all the privileges in D365 Security Roles for SharePoint Site or Document entity are correct or not? In fact, it’s the SharePoint privileges that you must look into. Privileges On SharePoint: Even if the error indicates that you don’t have access in D365, it is actually the SharePoint site that’s missing permissions. Here’ where you need to check for the O365 User’s SharePoint privileges: Navigate to SharePoint Admin Center in the Office 365 Admin center Next, in any of the intended SharePoint sites, navigate to the Gear Icon and then Site Settings. In Site Settings, navigate to People and groups under Users and Permissions area. Check that you might not have the intended user in that list. You can then click on Add and add the user in the list. You can either add an individual user or ‘Everyone Except external users’. and confirm that you see them in the list now. Confirm Permissions: Now, you can ask the users to check and they should be good to go. Hope this helps!

Introduction: Html web resources are not loading properly on tablet version of Dynamics 365 sales. Description: We were working on custom html page which needs to be shown on tablet version of Dynamics 365. After the completion of development, we start testing. During testing some time html page was loading properly and sometime not. We thought this might be due to current changes in the customization. After, development was completed we start getting loading issue and we could not find why we are not able to load the form. We tried various approach to resolve this issue but we were not able to find the exact cause of not loading the html page on the tablet version. We noticed that this weird behaviours start coming when there is any customization done at CRM level. We also noticed that if you uninstall and reinstall the app it starts working fine but this is not a feasible solution to work every time to install and uninstall the app. Solution: We registered this case with Microsoft and we also tried every possible solution to work on this but this was still not resolving. Microsoft internally tried to replicate the issue and they said that- “Based on our investigation result, The root cause of this issue is that ‘this.LoadFinished();’ under CustomEventHandlersManager.cs is not being done when reproducing, hence the iframe would not be able to load. We have two ways you could try to resolve the issue: Option 1: Try to make form dirty and publish it again through form editor. The way we could make it dirty could be ‘Add a hidden field’, ‘Switch any two field like name and owner, then switch back’ Option 2: Other then way 1, user could visit any linked field on the form, like Owner, lookup field, then navigate back through top left navigation button If we go to option 2 and open another form, then it will hit loadFinished, when come back, the iframe loads well. The CustomScriptsContainerViewModel libraryNames not loaded are [“msdyn_/libraries/require/require.js”, “SystemUser_main_system_library.js”] Static names are [“/_static/_common/scripts/BusinessRulesExecution.js”,”_static/_common/scripts/BusinessRuleExecution.js”] So finally, 2nd approached work for me. This is still and open case with Microsoft. Conclusion: Hope this may help those who are facing the issue of HTML page loading on Tablet App on Android/iPad. I will update this post if I get a solution from Microsoft.

Introduction: This blog explains how to configure SLA to Work Order Entity. Scenario: Most clients demand SLA for Work Orders and Resource Bookings in Field Service. Steps of Implementation: We need to configure SLA for Work  Order as explained below. 1. Mark checked  for setting “Enable for SLA” on Work Order entity as highlighted below. 2. Create new Lookup Field with target record type as “SLA KPI Instance “as shown below. 3. Set the field on the form and insert the Quick View form as shown below also publish the cusotmizations. 4. Insert the “Quick View form” which shows time for First Response Lookup as shown below and pubish the Customizations. 5. Create a new record of SLA by navigating to Settings > Service Management > Service Level Agreements. 6. Create new record of SLA Details with below settings as shown below Select First Response In for SLA KPI field. Select criteria for SLA trigger time in “Applicable When”. Select criteria for SLA succerss in “Success Criteria”. Select criteria for SLA failure in “SLA Item Failure”. 7. Activate the SLA and “SET AS DEFAULT” button on the SLA ribbon form. Before enabling :- After enabling :- 8. Create a new record of Work Order and save it you will see SLA records shows the details. Conclusion: This blog explains how SLA can be configured to Field Service entities where it helps in tracking time by users on task.

Introduction: In this blog, I will outline how to migrate Email Attachments and update the status if an email. In my previous blogs, I have shown how to migrate the body of an Email and its Activity Parties from one CRM to another using Scribe. Email Attachments: Below, is the map used to migrate Email Attachments. As you can see, it is pretty straightforward, barring a few things to keep in mind while mapping. 1) Email Attachments are stored in the ‘activitymimeattachment’ entity. 2) I did not map the ‘attachmentid’ field as it produced an error as well as there is probably no reason one would need the GUID of the attachment. Not mapping attachmentid will create a new GUID for the attachments being migrated. 3) Most data regarding the Attachments migrated along with the first map migrating ‘Email’ activity. 4) That is why, in this map, we just migrate the subject, filename and body fields along with ‘objectid’ and ‘objecttypecode’. 5) The ‘objecttypecode’ tells which entity the attachment belongs to and its GUID. Once you run the map successfully, you will see the attachments displayed in the email. This includes image attachments as well. Target: Email Status Update: As for most Activity entities, while migrating, we migrate with an ‘Open’ status. This is done to ensure the record does not become read-only which would not allow us to migrate the corresponding Activity Parties and Attachments. This could lead to an inconsistency in data in Source and Target. Once the Activity Parties and Attachments have been migrated to the record, we can now update the Status of the Email to what it is in the Source environment. This is a basic but fundamental step to ensure no data inconsistency. Sample State Code & Status Code Values: In this map, all we have to map are the ‘Status Code’ and ‘State Code’ as it is in the Source Environment. This will update the status of the email. In the screenshot below, you can see that the Status has been updated to ‘Sent’. Conclusion: This completes the process of creating TIBCO Cloud Integration Maps for Email Migration from CRM to another. I hope this and my two preceding blogs provide a sufficient outline for the process of Email Migration.