Introduction: Data migration can be a little challenging, especially when it comes to Emails. In this blog, I will outline the steps that need to be followed to successfully migrate Emails as well as important things to keep in mind during the process. Steps: There are four main steps to follow to successfully migrate an Email from Source to Target: Send the body of the Email. Send all the related Activity Parties. Send the details of the related Email Attachment(s). Update the Status of the Email. In this blog, we will be dealing with the first step i.e. creating the map in TIBCO Cloud Integration to send the Body of an Email. Migrating the body of the Email is straightforward compared to the next step but there are a few aspects to keep in mind: 1) Send the email as Open so that Activity Parties and Attachments can be migrated in the following steps. Not sending the email with an “Open” status could lead to Activity Parties and Attachments not being migrated to the corresponding email. 2) When an email is migrated, the owner of the email will be the User configured in the CRM Connection in Scribe. In order to maintain the same owner as in the Source, you can update the email with the correct owner after it is created. In the screenshot below, I am using a Lookup Table in Scribe to map the User GUID of the Target System. 3) If you want the GUID of the email to remain the same in Source and Target, do not forget to map the ‘activityid’ of the Email entity. Conclusion: I hope this blog provided some insight into the migration process for Email Activities. In the next blog ‘Email Migration from CRM v8.2 to CRM v9 using TIBCO Cloud Integration: Activity Parties‘, I will talk about migrating ‘Activity Parties’ which can be the most challenging part of Email Migration.

Problem: Need a way to roll-up multiple rows into one row and one column. There is a way we can roll-up multiple rows into one row using pivot, but we need all of the data concatenated into a single column in a single row. Solution: To achieve this we will use For XML Path Clause and STUFF Commands. STUFF() Function STUFF function is used to insert a string into another string. Basically, it deletes the characters from a source string and inserts another string at the specified position. Syntax: STUFF(Expression,Start, Length,Replacement_expression) Here, Expression is an expression of the character data to be modified. Start is an integer, which specifies start position in Expression to delete and insert another string (i.e. Replacement_expression) from here and length is an integer, which specifies the number of characters to be deleted. Replacement_expression is a character expression to be inserted at the start position. Example: Data in table like this: Query : Output :

Introduction: In this blog you will see how we you can use content pack for D365 in Power BI. Content package that are created are easy for your team to find — they are all in AppSource. Because they’re part of Power BI, they leverage all the features of Power BI, including interactive data exploration, new visuals, Q&A, integration with other data sources, data refresh, and more. Steps: Login to your Power BI Account > Click on Get Data. Click on Services. Select the proper content pack from the AppSource. Click on Sales Analytics for Dynamics 365 > and click on “Get it now”. It will as about the CRM account, and the Fiscal Year End Month Number, fill in the details and click next. By default, it will use OAuth with the current account that is logged in. After successfully login, dashboard will start with pumping up with data. Importing data will take some time, and after successful login you will get the ready content package Dashboards and report. You are set and good to go, try other content pack as well. Currently there are 21 Content pack available for different flavour of D365, try them there are superb.

Introduction: Recently, we faced an issue with integrating Unit Price to Dynamics GP through GP Web Services using TIBCO Cloud Integration. We were integrating the Unit Price from Dynamics 365 but the Unit Price in an Invoice was created with $0 Price. In this article, we will learn to resolve the issue for Dynamics GP Sales Invoice Unit Price always setting to $0 when creating through GP Web Services. Resolution: In Dynamics GP Web Service Policy Configuration for Update Sales Invoice Policy, you need to update the “Calculate Unit Price Behavior” to “Do Not Calculate”. Also, make Sure that you have selected the right Company and assigned proper roles for the policy. The role should not be Default. Note: The “Calculate Total Amount Behavior” should be “Calculate” otherwise the Unit Price will be always 0, even if you set the “Calculate Unit Price Behavior” to “Do not Calculate”.

Introduction: This blog will help you through connecting power BI to your D365 environment. Steps: Open Power BI Desktop, click on Get data connection, and click on More… Go to Online Services > then select Dynamics 365 (Online) > then click on connect. It will ask you about Web API URL, this is not the CRM URL, it is the API URL that will allow you to communicate to you D365. You can locate the Web API in your Dynamics 365: Go to Dynamics365 > Go to Settings > Customizations. Select Developer resource inside Customizations. Inside the Developer Resource you can locate your Web API URL. Copy the Service Root URL and paste it in your Power BI Desktop. After adding the URL click on and click on the Organizational Account and click on Sign-in. After successful sign in, click on connect, you will see list of entities available for the login. Select the tables and get going, you are good to go now.

Introduction: With the latest update of Power BI, you can now ask top-n type questions and get answers based on your dataset. Questions like ‘What are the top 3 products by sales?’ or ‘Top Manufacturer by country’ are examples. This is also valid for bottom-n type questions like ‘Least selling product in a country’. Steps: 1. Go to your PowerBI Workspace and select your report. 2. Click on the ‘Edit’ button. 3. Select ‘Ask a question’. 4. Type in your question and the visualization will form with the answer based on your dataset. 5. Make changes to your Axis, Legend and Value fields if required. Conclusion: This feature enables the User to obtain important information from the dataset quickly and easily using natural language thereby enhancing the capability of Power BI to provide self-serving business intelligence.

Introduction With the latest release of Power BI, new feature has been added to share the power BI reports as well. Yes, you heard it right, now we can share the Power BI Reports as well to teams and partners. How it works: Go to your workspace and open the report that needs to be shared. Click on the share option. Enter the email address and click on share, if the send email notification option is checked then notification will be send to users. Conclusion: This is a superb feature that is added to power bi, allowing organization to share reports as well with dashboards for detailed information.

Introduction: In this blog we will see how we can deploy SSIS integration package individually using file System Deployment. Steps: Convert the current project to package deployment model. After clicking the project deployment model, the screen will pop up with the compatibility check for all the packages with below screen, click ok if all is good. Below icon and name will be changes for the solution when you click Ok button from above screen. Create your package and test it in visual studio, save your package. Now we go for deployment of package: Capture the path for the package: “D:\PackageDeploy\Package.dtsx” Deploying Package to SQL Server and Configuring it to SQL Agent Job: Create New job Create the Steps in JOB Crete the Step. Select the Step type to SQL Server Integration Services Package Select the Package source type: File System as this is a package Deployment model. Provide the package path Note:  While providing the package path we need to make sure that SQL server can communicate to the path as this will be running inside the SQL server. Execute package and check the Job status: Conclusion: With the above steps you should be able to deploy the SSIS package using package deployment model, there are many more methods to deploy the package, like- by using manifest file, Project deployment models and so on, stay tuned for upcoming blogs.

With Power BI latest release, you can now hide the page in Power BI reports, this page is available while you are developing and when you hide it by right click on the package and selecting Hide Page, then that page will not be available in Reading mode. When you select the Hide page option then the option is checked as hide page. Page is marked as dull colour to show that it is hidden. When you publish this to your workspace then page will not be displayed in reading mode: So, you can technically hide page in your power bi report if you don’t want to use them, but if the user has rights to edit the report then he can change the settings.

TRIM Function has haunted SQL DBA for ages. If you have been using SQL Server for a while, you will totally agree with me over here. In this blog post we will see how the new feature TRIM of SQL Server 2017 works in few simple words. SQL Server DBAs and Developers have always dealt with SQL Strings and the leading and trailing spaces often makes them crazy. Data query may not be at it’s best if there are leading spaces around strings and which are not useful for data comparison and well as storage point of view. In the previous server versions developers used to two different functions LTRIM and RTRIM around the string to get necessary results. However now in SQL Server 2017 we have a new feature introduced which is TRIM(). This function works just like LTRIM and RTRIM together. When you run above script you can see that when we use function TRIM around the string it removes leading and trailing spaces. Trim function is combination for LTRIM & RTRIM, and only available in SQL server 2017. For earlier version, LTrim and RTrim is available.