Starting from sales until delivery, Microsoft Dynamics 365 offers successful deployment of various business processes. The partners of Microsoft Dynamics 365 list the apps in the app source developed for a specific business need or for a particular business vertical hence showing their expertise. The dynamics 365 application development team has experts who are specialized in developing sophisticated business apps for their partners. The entire lifecycle of the business is supported through Microsoft Dynamics 365 right from developing the apps to listing them in the AppSource and giving support which lets you focus on the core business strategies instead of things which are less important. The qualified team of experts understand your requirements initially and then further work on improving each and every aspect of your business Introduction: This blog explains how to Filter records in PowerApps based on the current user of Dynamics CRM. Steps to be followed: Step 1: Add user entity. For that go to View –> Data sources –> Select Dynamics 365 connection. Select user entity –> click on connect. Step 2:  Now select Browse Screen and add Label control on Browse screen. Set its visible property to false. Set Text property to: LookUp(Users,internalemailaddress=User().Email,systemuserid) Step 3:  Select Browse Gallery and set its Items Property to : Search(Filter(Cases,_ownerid_value = Label1.Text), TextSearchBox1.Text, “description”) (Here Label1 is the name of Label which we have added in previous step && _ownerid_value stores the owner of that particular case record) I have selected _ownerid_values because owner field stores the user value according to which we want to filter the case records. By following above steps you will be able to filter records based on current user.

Introduction: In this article, we will learn how the Filter changes its default values during Parameter selection in SSRS Reports with Examples. Scenario: I have 4 parameters in my report: Start Date: Default is today’s Date End Date: Default is today’s Date + 60 Days Department: No Default value. Project: Dependent Filter on Department. Once the Department is selected, default all projects will be selected. Filter Working: Below listed is various test cases which shows how the Select ALL in Project Filter changes according to other 3 parameters. Default Filter: Start Date: Current Week Start Date End Date: Today’s Date+ 60 days Department: Select all manually Project: Disabled Results: All projects will be automatically displayed and selected based on dates and Department. Selecting wide range of Dates after Initial run (After Step 1): Start Date: less than Current Week Start Date or Current Week Start Date End Date: Greater than Today’s Date+ 60 days Department: Select one manually Project: Not all the Projects will be selectedResults: All projects between the date range will be displayed but the projects after today’s date + 60 will be un-selected. Selecting more Department (After Step 2): Start Date: Any End Date: Any Department: Select two department Project: Not all the Projects will be selected Result: All projects between the date range and department will be displayed but the projects in newly selected department will be un-selected. In this example, projects in Assurance Department will not be selected. Conclusion: Dependent filter (Project Filter) will be disabled initially. Dependent Filter will be displayed and open once all the other filters are selected. Dependent Filter will change based on the other Filters change. After initial run, any change in other filter will control the behavior of Dependent Filter. Selecting Wide Range initially and then reducing the Range will keep the Dependent Filter as Select All. E.g.: Decreasing the Date Range or Selecting less number of department selected initially. Selecting a range initially and then increasing the range will remove Select All in Dependent Filter (Only the initial range Project will be selected). This the default SSRS behavior. E.g. Increasing the Date Range or Selecting more departments selected initially. EXCEPTION: If you increase the Date Range and then Reduce the Department Selected, All Projects will be selected by default.

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.

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 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!

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.

Introduction: This blog explains how to Pause SLA in Dynamics 365. Steps to be followed: Only Enhanced SLA can be Paused. Go to Settings –> Administration  –> System Settings –> Service Select the Entity for which SLA is Created. (I have Created SLA for Word Order so I will select Word Order from that list). Now from Available Values select that Status that will Pause SLA. For Work Order entity we will create new Status as “On Hold”. (because it does not have any status which we can use to Pause SLA) Save and Publish. Now Select “On Hold”. Go to Work Order entity and select the Status = ‘On hold’ and Save. SLA is Paused now.

Introduction: In latest Power BI update, Microsoft introduced new feature as Multi-select data elements on visuals. In Power BI Desktop, we can highlight a data point on visuals by simply clicking on the data point in the visual. Means, if we have an important bar chart, and we want other visuals on the report page to highlight data based on our selection, we can click the data element in one visual and see results reflected in other visuals on the page. This is basic. Till now we are only able to filter the data on single-select highlighting. See below screen capture: New feature: But by using the new feature of the Power BI we can multi-select data element on visuals, we can now select more than one data point in Power BI Desktop report page, and highlight the results across the visuals on the page. To multi-select data points in visuals, simply use CTRL+Click to select multiple data points. See below screen capture for multiple data points select on visual(multi-select):

Introduction: Recently, we came across an issue where we were integrating Customer and Sales Order from Dynamics 365 CRM and GP. Customers and Sales Orders were successfully integrated except when Sales Order was created using the Integrated Customers; an error regarding Credit Limit would occur. The TIBCO Cloud Integration GP connector does not support the ability to set a customer credit limit, which in turn will not allow you to use that Customer for creating a Sales Order. Resolution: In GP Web Service Security Console, under Create Customer Policy: Change the Behaviour of Customer Class Defaulting from “Do Not Use Customer Class” to “Use Customer Class”. In the Scribe Mapping, pass a ClassKey_Id. For ClassKey_Id, setup a Customer Class with no Shipping Method or Tax schedule ID and specify the credit Limit properties.