Introduction: In this blog article, I will demonstrate how to enable ArcGIS in PowerBI, its features and how to use it to display data. The ArcGIS Visual, created by Esri, displays data in a unique and immensely customisable way. The Visual allows the User to select the type of map, various ways to represent data points and additional features like distance mapping and reference layers to make the visual interactive and informative. In order to enable ArcGIS, the User must agree to Esri’s terms and conditions. Enabling the ArcGIS Visual: To do this in PowerBI Service, go to the ‘Settings’ menu. Select ‘ArcGIS Maps For PowerBI’ and select the checkbox next to ‘Use ArcGIS Maps for PowerBI’. Click Apply. Now you can go to the ‘Editing View’ and select the ArcGIS icon from the Visualisations Pane. To enable it in PowerBI Desktop, select ‘Options and Settings’ in the File menu. Select ArcGIS Maps for PowerBI in the Preview Features section. Now, select the ArcGIS icon in the Visualisations Pane to get started. Using the Visual: After loading the data into PowerBI, drag your data in the appropriate fields in the Fields pane. Now here is where the fun begins! Click on the ellipses and select the ‘Edit’ option to start customising your visual. A task pane appears at the top of your visual. The first option is ‘Basemap’. In this option, you can select the type of map you would like to use and that would best showcase your data. The next option is Location Type. Here, you can select how you want your location data represented. Points will show you data points and Boundaries will display data by state boundaries. Map Theme, the next option, will let you select different visual ways to display trends in your data. ‘Size’ displays points variating by size based on your data, while ‘Heat Map’ shows where the values are high, medium and low by color. Symbol Style allows you to select which symbol you want to use to represent the data and customise the symbol by style and size. Pins allow you to highlight locations in your map that you want to showcase other than what your data is displaying. Just type the location in the search bar and select the correct location to add a pin there. You can also change the color of the pins if required.   The Drive Time option allows you to show which data points are within a given distance or driving time from a pin. This feature can also be customised by selecting color, transparency and outline preferences. Reference Layer is a feature that allows you to add data to the map based on common statistics like the country’s population, gender ratio and various other demographics like age and diversity. This allows the user to add more information to their map that could be of significance to the data being represented. One can also hover over states to see the reference data of that state. Conclusion: As you can see, the ArcGIS Visual is designed to make your data easy to understand and interactive while providing additional relevant data. Its customisability combined with its power-packed features makes this one visual that could really add immense value to any report or dashboard.  

Introduction: In this article, we are going to learn how to embed Power BI Tiles in your Dynamics 365 / CRM Dashboards. Steps: Sign-in to Microsoft Dynamics 365 as a user with the system administrator security role Go to Settings > Administration > System Settings. On the Reporting tab in the Allow Power BI visualization embedding option, select Yes to enable or No to disable. Click OK. Create Dashboards in Power BI and publish it. Then Create or edit a Dashboard in CRM. And insert Power BI Tile in TAB. Select a Power BI dashboard and a tile. Complete the dashboard, Save, and close. You are all set!

Introduction: In this article, we will see how we can generate Excel Report in SSIS without doing Physical mapping. Steps: 1.    Create Excel file with one data connection in the Excel Sheet. 2.    Create a sheet in Excel pointing to the data connection. This will lead to point the connection to the data source, and help create a table in Sheet. As soon as ok is pressed, the data from the connection is pulled. We can save this Excel as a template and next time we just need to refresh the connection and the data will be refreshed in the Excel Sheet. This is the day to day process which requires manual effort, WHAT IF WE CAN AUTOMATE THE REFRESH. It is possible through SSIS services, and Microsoft Interop libraries. Steps: 1. Create a SSIS package with a Script task with C#. Edit the script and include the following code in the Script task Use below script to refresh the data in the Excel. We need to include the reference for the Interop libraries. using Excels = Microsoft.Office.Interop.Excel; string filepath = @”D:\Excel Files\Employee Files.xlsx”; Excels.Application xlApp; Excels.Workbook xlWorkBook; Excels.Worksheet xlWorkSheet; object misValue = System.Reflection.Missing.Value; xlApp = new Excels.Application(); xlWorkBook = xlApp.Workbooks.Open(filepath); xlWorkSheet = (Excels.Worksheet)xlWorkBook.Worksheets.get_Item(1); xlWorkBook.RefreshAll(); xlApp.ErrorCheckingOptions.NumberAsText = true; xlApp.DisplayAlerts = false; xlWorkBook.Save(); xlWorkBook.Close(true, misValue, misValue); xlApp.Quit(); releaseObject(xlWorkSheet); releaseObject(xlWorkBook); releaseObject(xlApp); Benefits: 1. This process is used if we need to generate custom reports. 2. We can use the existing data in excel sheet to create pivot table, and create custom data formats. Feel free to contact us if there is any issue.  

Introduction: This document contains the steps on how the TIBCO Cloud Integration Agent with custom connector for Dynamics GP can be deployed on server. Install a TIBCO Cloud Integration on-premise agent A TIBCO Cloud Integration agent needs to be installed on the server where the target data store resides. Download TIBCO Cloud Integration agent You can download and setup an agent from https://app.scribesoft.com Once logged in to TIBCO Cloud Integration portal in the server where the target data store resides, navigate to ‘More’ and then ‘Agents’ and then click on ‘+’ and ‘On-Premise Agent’ to create a new agent. Please refer the screenshot below: A new window will open where you can click on Install On-premise Agent to download the agent as shown below: On clicking Install On-premise Agent, TIBCO Cloud Integration will provide you to download the agent. You need to save the same to your local system. Copy the Agent Key in your clipboard; it will be used during Installation of Agent. Navigate to the location where the ScribeInstaller was downloaded and start the installation Make sure pre-requisites are setup to be able to successfully continue with the installation and click Next:   The wizard will start. Click Next until you see the screen where Agent Key is asked by the installer. Enter the same key which appeared on the screen where new agent was provided to be downloaded. And click next. Select where you want to install the TIBCO Cloud Integration agent. Finally click Install Agent. Let the setup continue. Click Finish once the setup completes.   Turning TIBCO Cloud Integration Agent on and off TIBCO Cloud Integration Agent on your system is a Windows Service which can be stopped, started and restarted. View Services application on your Windows machine to locate the TIBCO Cloud Integrationweb service Locate Scribe Online Agent in the Services. This is where you can start and stop service in the event of updating the DLLs for the Scribe Online connector. Deploying Scribe Online connector on the target system Deploying the Scribe Connector to the target system consists of copying the required DLLs and PDBs to the following folder in the Scribe Online Agent directory located on the target machine: Locate Connectors folder in the Scribe Online Agent directory. Folder named “DynAD Connector” contains DLLs and PDBs required to be available in the Scribe Online’s Connector folder. This folder needs to be copied in the Scribe Connector’s Connector folder. The address for Scribe Online Connector is: C:\Program Files (x86)\Scribe Software\Scribe Online Agent\Connectors Once the folder is pasted to the Connector folder, the agent needs to be started again. Navigate to View Local Services on the machine and locate Scribe Online Agent and start the same as shown below. For the Custom GP Connector developed for AKA, the following files are required to be copied in the “DynAD Connector” folder. Note: Since the project is divided into 2 DLLs across a Visual Studio solution, CFS.Connector.GPConnector.dll and CFS.GPClient.dll are the 2 DLLs and their respective PDDs are required. Required Files: Connector.GPConnector.dll and CFS.Connector.GPConnectorA part of the GP connector (.dll) and its PDD file GPClient and CFS.GPClientA part of the GP connector (.dll) and its PDD file Core.ConnectorApi.dllThis .dll file is required by the ScribeOnline agent to be able to access the Scribe API provided by ScribeOnline. Json.dll and Newtonsoft.Json These .dll files are required by the connector to be able to JSON file stream where the fields of the target connector are retrieved. JSON files – 5.1 DynADCampaignHeader.json 5.2 DynADCampaignLineItem.json 5.3 DynADSalesCommission.json 5.4. DynADCampaignErrorLog.jsonThe above files are the JSON files which contain the fields required by Dynamics GP entities. These files need to reside in the folder as the .dll require these. Important: These files also need to be present in the C:\Windows\System32 of the system. Updating Solutions with newly installed Scribe Online Agent Login to Scribe Online Portal through https://app.scribesoft.com Open a Solution and resign the Solution with newly installed Agent. Repeat this for all the Solutions. Conclusion: By following the mentioned steps, you can deploy the Scribe Online Agent with custom connector for Dynamics GP on server.

Microsoft power BI is a collection of features and online services that enables you to share your findings, analyse and visualise data in the form of dashboard and reports and the whole process is termed as power bi analytics. Utilizing the Microsoft Power BI Integrations, you can import information that is huge from different sources into the Power BI work area. You can alter the information or plan on changing it in the wake of bringing in to your framework.  The Microsoft Power BI Service now and then is alluded to as Power BI or app.powerbi.com. You can keep awake to date with all the fundamental data that truly matters to you. Force BI arrangement will assist you with conquering the greater part of the issues you are looking for effortlessly.  Introduction: In this article, we will see how to embed Power BI in Microsoft Dynamics 365 Operations. Steps: Register your Dynamics 365 Operations as a web app on Azure AD. Open link: http://dev.powerbi.com/apps Login to your Power BI account Fill the required details: App Name App Type: Select as ‘Server-Side Web app’ Enter a redirect URL: Your instance URL with /oauth at the end Enter a homepage URL: Your instance URL Choose API access you need. Click Register App. Once the app is registered, you will get Client ID and Client Secret. Copy these 2 keys, you will need it later. Navigate to Power BI settings in Operations which is under System Administration section.  Enter the details in Power BI configuration: Client ID: Paste the Client ID Key from Power BI registration Application Key: Paste the Client Secret key from Power BI registration Redirect URL: Your instance URL with /outh at the end Enable the Power BI Navigate to Reservation Management for instance and you will see a Power BI column. Click on Get Started. Authorize Power BI by clicking on ‘Click here to provide authorization to Power BI’ You will be redirected to the new window with authorization success message Now, you can select reports and dashboards from Power BI and pin them to your workspace.

We do have many different development and deployment Environment and we do have different configurations with respective to the environments. These configurations may be tricky but it provides ease to user to deploy to different environment without changing configurations again and again. Below are the screen shots that will help to setup these configurations. Let’s create one more environment, let’s call that QA. Now you can see QA also in the environment. Let’s now create project parameters and configure it against environments. After creating few project parameter, we can configure it. Then you assign values to parameter with respect to environment. Then Click OK. When you click ok you can see the values assigned to the parameter. Let’s change the environment to QA, and you can see the change in the parameter. This kind of parameter we can use in the expression in different package, so we just need to change at one place.

In this blog article, I will explain you how to deploy the  SSRS Report on SQL Server. Now you have your report done and it’s time to get them on your reporting server from visual Studio. Within Visual Studio, you can deploy your any individual report or entire project full of reports. In Solution Explorer -> right-click on your project -> Properties. Enter the Target Server URL. If you don’t know what your TargetServerURL is, Start instance of Reporting Services Configuration Manager  -> click the Web Service URL tab. The URL you need is in the Report Server Web Service URLs section. Return to the Property Pages box, enter the above URL as the TargetServerURL, and click OK. Now you can right-click on either your project or any single report and click Deploy. Now we have to verify that our report made it to the server and that we can execute them. To get the URL for previewing the reports, open the Reporting Services Configuration Manager, click the Report Manager URL tab and copy the Report Manager URL. Open that URL using Internet Explorer with administration permission(Right click on internet explorer -> run as administrator). Navigate to the SSSR Reports folder, click on your report name, and you should be able to execute it right there in the browser.

In this article, we see AX hotfix deployed by Scribe which resolves the issue for Update Patch in Dynamics AX Connector. Error Details: We have Integration build between Dynamics 365 and Dynamics AX. One of the Integration package integrates CustomerPostalAddress from AX to Address in Dynamics 365. In this package, we wanted to store AddressNumber of Dynamics 365 back in Dynamics AX. So, for updating the CustomerPostalAddress with AddressNumber we used UpdatePatch with AddresslocationId as the matching criteria. Unfortunately, we were getting an error as “Error in calling Operation Update Patch: Operation returned no results. Label: Update Patch CustomerPostalAddresses, Name: CustomerPostalAddressesUpdatePatch” Strangely, we could Query, Fetch and lookup using the same criteria of AddresslocationId to retrieve records from CustomerPostalAddress. Solution: Scribe recently deployed an AX hotfix which resolved this issue. Turns out, if any DateTime field is a primary key for a entity then in matching criteria we have pass all the primary keys. Here, we are using CustomerPostalAddress entity. Primary fields of this entity are: AddressLocationId (String) dataAreaId (String) Effective (DateTime) CustomerLegalEntityId (String) CustomerAccountNumber (String) So, in the Update Patch for CustomerPostalAddress we have to pass all these 5 fields for it successfully run the Update Operation.

Package configurations is very important to achieve flexibility SSIS package, easy configurations allow used to changes and reuse the solutions in different environment with them customize settings and rules. SSIS package supports different types of configurations, these package configurations is also depended on deployment model. In this blog we will discuss about the Project Parameter configuration using the Project Deployment model. Let’s make the SSIS package Solution to Project Deployment model. Right Click on the SSISProject Solution Name, Click Project Deployment Model. Follow the Wizard: Click Next: This will provide you list of packages that you need to convert, then click next. Next will be setting up the protection Layer for the Package: Then Click on Next and then it will convert your Solution to Project Deployment model. Project Deployment Model allows you to configure the package at project level, it groups the Package configurations together that allows user to easily configure Parameter.

In this blog article, I will explain about the new updates of Power BI related to Data bars for new table & matrix (preview). These are the new type conditional formatting to the table and matrix visual called as data bars. Data bars are a quick way to format data and to make it easier to compare. There are two ways two ways to turn on data bars.   1) From the Field itself and   2) From Menu Select Data bars on any numeric measure from your matrix or table. This launches a dialog for customizing the data bars. We can set the properties for data bars like we can set the bar color , min and max value. See below screen captured: Once you confirm with settings, you’ll see the data bars applied to the visual. You can also turn on color scales and data bars from the formatting pane by selecting Conditional formatting. Set Color scales or Data bars to On to apply the default settings or, to customize the settings, select Advanced controls.