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.

Introduction: Zapier is an Integration tool which allows users to connect various Web Apps.  Zapier is used for simple small scale integration purpose. In this article, we will learn how to create a basic Zap (Integration Process) for Integrating Accounts from Salesforce to Microsoft Dynamics CRM. Pre-requisite: Salesforce Microsoft Dynamics 365 CRM Zapier Steps: Login in to your Zapier. First Step is to create connection for your Source and Target Systems. Click on ‘Connected Accounts’ Tab for creating Source and Target Connections. After selecting the connector, you will be prompted to enter credentials to connect to the systems.List of all the Connected systems/ Apps will be displayed under My Connected Accounts. You can Test, Reconnect or Disconnect the Connections.  Now Click on ‘Make Zap’ to create your new Zap i.e. Integration process definition. Choose the Trigger App. i.e. your Source. Here, we are using Salesforce as our Source. Choose Trigger. i.e. Select an event, based on which you want your Zap to execute. Here, Creation of new Account in Salesforce should execute the Zap; so, we have selected ‘New Account’ Select your Salesforce Connection. You Test your connection by clicking on ‘Fetch & Continue’. If the test is Successful, you can even view the record which is fetched by clicking on ‘view your account’ After setting up the trigger, we have to setup Action. Now, we have to select our target system. Here, we are Microsoft Dynamics CRM as our target. Choose an Action. i.e. Create or Update operation you want to perform on target. Here, we will select ‘Create Account’ since we want to create an Account in CRM which is integrated from Salesforce. Choose your Microsoft Dynamics CRM Connection. Now we have to Map fields of Source fields to Target fields. Click on  target field to get drop for list of source fields. Map all the required fields. After Mapping all the fields, press continue to Save the mappings. Then you can test the Mapping by clicking on ‘Create & Continue’. This step will create the new record in target per the Mapping and data that is fetched from Source in step 7. You can view the record created by clicking on ‘view your account’. You can click on button add more actions or Click on ‘Finish’ button Name your Zap and Turn it on.You are all set for Integration!!

In this article, we are going to compare features of Microsoft Flow and Zapier. Real Time Integration: Microsoft Flow: Flow gets automatically triggered based on create/update/delete record defined in the workflow. Note: Triggers for Create, Delete and Update are available Zapier: Zap gets automatically triggered based on create record defined in the workflow. Note: Trigger for Create is available Scheduled Integration: Microsoft Flow: Flow can be scheduled by day, hour, minute, seconds. Recurrence action is used for the same. Zapier: Zap cannot be scheduled. It can only be triggered on Creation of new record. Triggers: Microsoft Flow: Triggers can be specified for any entity. Zapier: Triggers can be specified for limited entities. For example: For Dynamics CRM, the trigger can defined only for Contact, Opportunity, Lead and Account. Lookup Action: Microsoft Flow: Records can be looked up using GUID / Unique Identifier of the record. We can look up to any entity. Zapier: Lookup record i.e. Search in Zap is different for different Connections. Only few Entities is provisioned for Search Criteria for Search can be based on all fields or one field based on Connectors (Explained below with example) Search value can dynamic i.e. values can be retrieved through previous steps. For Example: Search for Salesforce can be based on any field For Dynamics CRM, condition for Search for Contact is based only on email address. Conditional Workflow: Microsoft Flow: Various flow control can be setup in Flow like if-else, switch-case, do-until, etc. Zapier: Logical conditions setup is currently not available in Zap. Filters: Microsoft Flow: Source records cannot be filtered. Zapier: Filter feature not available. Data Formatting: Microsoft Flow: Data fetched from Source cannot be formatted before sending to target. Flow supports simple one-to-one mappings. Zapier: Data fetched from Source cannot be formatted before sending to target. Zapier supports simple one-to-one mappings. Execution History: Microsoft Flow: Errors can be monitored in Activity section in Flow. Errors cannot be handled inside a Flow. Zapier: Errors can be monitored in Task History section in Zapier. Errors cannot be handled inside a Zap Debug: Microsoft Flow: Debug feature is not available for a Flow. Though, after execution you can get output of each step Zapier: Debug feature is not available for a Zap. Though, after execution you can get input and output of each step. Conclusion: Summary for the Integration Tools: Microsoft Flow vs Zapier. Features Microsoft Flow Zapier Real-Time Integration Yes Yes Scheduled Integration Yes No Execution History Yes Yes Error Handling No No Debug No Get output of each step after execution No Get output of each step after execution Triggers Create/Update/Delete Only for Create Lookup Action Immature Mature than Microsoft Flow Filters No No Conditional Workflow Yes No Data Formatting No No  

In this blog article, I will explain about the new updates of Power BI related to Relative Date Slicer. In this introduce a new feature in date as Relative Date Slicer. In this update they previewing a relative date slicer, which lets you filter based on the last 1 or more years, months, weeks, or days. This makes date slicers much more powerful, as you can always filter your report to the latest data. We can choose the Relative option from the list of available date slicer types. Once you select relative from the list, you will be able to specify the date to filter by. We have following seven options to display data: Days Weeks Weeks (Calendar) Months Months (Calendar) Years Years (Calendar) If you pick an option marked with (Calendar), the filter will be based on calendar periods. For example, if you filter to 2 years, data from the last 2 years from today’s date will show. If you filter 2 years (Calendar), data from the last 2 completed calendar years will show. We show the dates used for filtering under the slicer, so you always know what data you are looking at. You can also switch to filter to this period or the next period. By default, the date range includes current date i.e. today’s date, but we can override this in the formatting pane for the visual: This is useful if your data hasn’t refreshed today and you don’t want to include data from incomplete days. Turn on this feature through File > Options and settings > Options > Preview Features > Relative date slicer.

Introduction: This blog explains how to define relationship between Entities in Scribe Connector CDK. Problem Statement: We often get requirement from Client to define relationships between entities in custom Scribe Connector Solution: Below is code snippet which explains how to define relationship between Customer and Contact. Step 1: Define child enity (Contact) Object definintion and add to objectDefinitions Step 2: Define parent enity (Customer) Object definintion Step 3: Define relationship between entites, points to remember as below: ThisObjectDefinitionFullName property set parent entity name RelatedObjectDefinitionFullName property set child entity name RelationshipType property set direction as “RelationshipType.Child” ThisProperties & RelatedProperties property should be same in both Parent and child entity. Step 4: Add relationship to parent entity(Customer) and add parent entity(customer) to objectDefinitions. Conclusion: Hope above scenario of defining relationship between entities help in real scenario of development.  

This is an awesome feature, which helps to capture the signature on mobile and tablet devices. Display the signature on the report: We can create report which will display an image captured by Pen control. Before moving towards the solution, mentioned below are the steps to setup the environment/Pen control. We added one multi-line text field on order form and configured it to use a Pen Control on phone and tablet app. Data stored in base64 value: When we draw something using pen control on tablet and mobile device, it is stored in the background, in encoded characters in the same multiline text field, as shown below. “data:image/png;base64,iVBDLSJDFASSKSDLKSLKNSLD/SDFSF…” In order to show the actual image/signature in the report, we just need to perform a nifty trick. Add that multi-line text field in your dataset. Insert image control and setup image properties as shown below. Image Source: Select “Database”. Use this field: add expression as follow, “IIF(NOT IsNothing(Fields!new_customersignature.Value),Fields!new_customersignature.Value.ToString().Split(“,”).GetValue(1),””)” **** Here we are just taking the encoded characters by splitting the field by comma “,”. We are excluding “data:image/png;base64,”. Use this MIME type: Select “image/x-png”. This setting results in pen control image in the report,