Introduction This log error will help us to understand and fix an issue as quickly. There are three main phases in an SSIS ETL execution life-cycle to catch errors: When data is being extracted from source systems When data is being transformed When data is loaded to the target systems Customized Error Handling also avoids the failure of Package during Runtime. It allows the package to be executed successfully and the Errors can be checked later from the Customized Error Log Table which you create to know what problem exactly occurred. Our Scenario For demonstration purpose, we will consider a Units Integration Map for Integration of Units from SQL to Dynamics CRM. In this Blog, we will Create a Customized Error Log Table in SQL and Catch the Errors from SQL (Source Block) and Dynamics CRM (Destination block). The Map for Unit Integration is as follows: Customized Error Handling in SSIS Execute the following query and create a customized Error Log Table in SSIS: CREATE TABLE [dbo].[ErrorLog]( [ErrorID][uniqueidentifier] NOT NULL default newid() primary key, [Entity] [varchar](250) NULL, [Record_Id] [int] NULL, [RecordName] [varchar](250) NULL, [ErrorDescription] [varchar](500) NULL, [DateTime] [datetime] NULL ) ON [PRIMARY] The structure of Table is as follows: ErrorID Entity Record_Id Record Name ErrorDescription DateTime Primary Key of Error Log Table. (System Generated) Unit UnitId Unit Name  Error Message  Error Log Date Error Handling at OLEDB Source Block: Step 1: Add a Script Component to catch the Error Description, Error Log Date and Entity. Select Transformation and click on Ok. Step 2: Connect the Error Output (Red Arrow) from OLDEB Source to the Script Component. Select “Redirect row” for all columns in the Error and Truncation Columns to redirect Error Output to Script Component. Step 3: Configure the Script Component as following: In Input Columns section Select Error Code and Error Column. In Inputs and Outputs section Add following Columns Column Name Data Type Length ErrorDescription Unicode string [DT_WSTR] 500 ErrorLogDate database timestamp [DT_DBTIMESTAMP] —- Entity string [DT_STR] 50 In the Connection Managers Section add a new connection and select your SQL connection In the Script Section click on Edit Script. After a minute a New Editor Window will Open. Here you have to copy and paste the following Script inside the “public override void Input0_ProcessInputRow(Input0Buffer Row)” section. Code Snippet: try { Row.Entity = “Unit”; Row.ErrorDescription = this.ComponentMetaData.GetErrorDescription(Row.ErrorCode); Row.ErrorLogDate = DateTime.Now; //If an error occurred due to Check Constraint, the ErrorColumn would be 0, and that error affects the entire row. Hence there is no specific column for that error   if (Row.ErrorColumn == 0) { Row.ErrorDescription = “An error that affects the entire row”; }   //If an error occurred due to Data type, then errorcolumn name would be updated.   else { var componentMetaData130 = this.ComponentMetaData as IDTSComponentMetaData130; if (componentMetaData130 != null) { Row.ErrorDescription = componentMetaData130.GetIdentificationStringByID(Row.ErrorColumn).Replace (“Customer Target.Inputs[OLE DB Destination Input].Columns[“, “”).Replace(“]”, “”); } } }   catch (Exception ex) { Row.ErrorDescription = “Unable to get Error Column Name”; } Click on Save and then Close the Window. Step 4: Add a Data Conversion Block to avoid any Truncation Errors because of Data Type Conversion between NVarchar and Varchar Data Types of the Error Description Column. Select ErrorDecription Column and select Data Type as String. Click on OK. Step 5: Add an OLEDB destination block. Configure your OLEDB Connection Manager and Select the Error Log Table which you had created in SQL Server. In the Mapping section do the following Mappings and click on Ok. Error Handling at Dynamics Destination Block: Step 1: Perform the Steps 1 and 2 as specified above in Error Handling at OLEDB Source Block. Step 2: Configure the Script Component as following: In Input Columns section Select Error Code, Error Column and CrmErrorMessage. In Inputs and Outputs section Add following Columns Column Name Data Type Length ErrorLogDate database timestamp [DT_DBTIMESTAMP] —- Entity string [DT_STR] 50 In the Connection Managers Section add a new connection and select your CRM connection: In the Script Section click on Edit Script. You have to copy and paste the following Script inside the “public override void Input0_ProcessInputRow(Input0Buffer Row)” section. Code Snippet: Row.Entity = “Unit”; Row.ErrorLogDate = DateTime.Now;\ Click on Save and then Close the Window. Step 3: Add a Data Conversion Block to avoid any Truncation Errors because of Data Type Conversion between NVarchar and Varchar Data Types of the Error Description Column. Select CrmErrorMessage Column and select Data Type as String and length as 500 i.e. according to the length of columns SQL. Click on OK. Step 4: Add an OLEDB destination block. Configure your OLEDB Connection Manager and Select the Error Log Table which you had created in SQL Server. In the Mapping section do the following Mappings and click on Ok. Checking the Error Occurred during Integration You can see the Error rows passing through the Error Output and being logged in our Error Log Table. Open the Error Log Table to check the Errors Occurred. Now you can easily identify the errors occurred during Integration process from your Custom Error Log Table and solve them to have successful Integration results.  

Error: You may face an issue in Scribe where the Scribe Services are not starting or are stuck in the Start state and an error pops up after a while as follows: Without the Scribe Services we cannot use either the Console or the Workbench to develop integration maps. Following is the Solution to resolve the above issue. Solution: Right click on the Scribe AdminServer service and select Properties. Select the Log On Tab and click on This account. Browse and select that Windows account which has been setup as the Scribe Service Account. This is generally the same account with which Scribe has been installed on your machine. Follow steps 1, 2 and 3 for the remaining Scribe services as well. Restart your machine. Conclusion: After restarting you should be able to start your services. Make sure you start your Scribe services in a sequential order and you should be able to open your Scribe Console now.

Introduction: It is possible to Fetch images from CRM’s entity records using Fetch XML.  This can be done using Notes attachment in CRM and the steps to display the Image in your report are pretty simple as well. Steps: Attach your image to a note under your respective entity in CRM In your Visual Studio copy paste the following code in your Query Designer <fetch mapping=”logical” output-format=”xml-platform” version=”1.0″> <entity name=”annotation”> <attribute name=”subject”/> <attribute name=”notetext”/> <attribute name=”filename”/> <attribute name=”filesize”/> <attribute name=”documentbody”/> <attribute name=”annotationid”/> <attribute name=”mimetype”/> <attribute name=”objectid”/> <filter type=”and”> <condition attribute=”mimetype” value=”%image%” operator=”like”/> </filter> <order descending=”false” attribute=”subject”/> </entity> </fetch> Add an Image Control in your Report. If you want to generate multiple images then you can add the Image Control under a Table Go to Image properties and select the image source as Database. Under field select documentbody and select your MIME type to whichever image format you want it to be  Click on preview and your image should be rendered in your report Conclusion: Thus you can store images in your CRM and generate dynamic SSRS reports with these images easily.

Introduction: There may arise a scenario where after creating a connection to Salesforce, a field that exists in Salesforce isn’t visible in your Scribe Insight DTS. This can happen because of multiple reasons. In this article I have listed down 3 of the most likely reasons why your SFDC field is not visible in Scribe Insight. Three Probable Reasons: Reason 1 The first reason can be that a custom field was created in your SFDC after you had created your SFDC connection in Scribe Insight. To fix this follow the steps mentioned below: Go to Connections in your DTS Select your SFDC connection Select Edit -> DTS Connection Settings -> Adapter Settings and click on Refresh Metadata. Your custom field should now be visible. Reason 2 The second reason can be that the field-level security has the visibility disabled for that field. To fix this follow the steps mentioned below: Log into SFDC classic and select Setup Go to Build -> Customize -> Object (Eg. Accounts, Asset) -> Fields Click on the field that isn’t visible in Scribe Insight and select Set Field-Level Security Make sure the field is visible for your Profile Reason 3 The third reason can be that you are just using an old API of Salesforce and that field did not exist for that version of SFDC. For example the Asset RecordTypeId field was added in the later versions of Salesforce. To fix this follow the steps mentioned below: Go to Connections Select your SFDC connection and click on Edit Select Change Connection Update the version of the Salesforce URL to the latest version that your SFDC supports

In this article, we highlight the key cloud-based IT and business systems that a Small and Medium Enterprise in India could use to improve efficiency while keeping costs low. These are also systems that we use to run our day to day operations. 1. Office 365 Business Premium – Email, Microsoft Office, Document Management, Security and Microsoft Teams. 2. QuickBooks Online Accounting Platform 3. PayBooks – India Payroll with integration to QuickBooks Online and optional biometric attendance integration. 4. Zoho Recruit – Recruitment Platform 5. Zoho People – HR Management Platform 6. Exotel – Cloud EPBAX business phone system 7. QuickHeal firewall for our network. Additional systems (once you grow to a certain size and need more processes and reporting. We use all of the below systems)– 1. Microsoft Dynamics 365 – Dynamics 365 Sales with lead integration with your website (typically WordPress). Dynamics 365 for Customer Support. Dynamics 365 Customer Support Portal for customer self service. Dynamics 365 Project Service Automation for Project Management. MailChimp for Marketing Automation or ClickDimensions. 2. PowerBI Analytics Platform. 3. GoToMeeting and GoToWebinar for Meetings and Webinars. Connect with us!

Introduction: In this blog, we will have a look on how IIS can be enabled for Web Service Deployment Steps to be followed: 1) Search for Windows features in your PC. 2) Check the box for Internet Information Services and click OK. A confirmation screen appears. Sometimes there are cases after the above procedure that it does not works. At such times, check all the options in windows features under IIS.

Introduction: In previous blog, we discussed some formatting for Markdown language. Some more display of text-stuff will be discussed in this blog. Blockquotes: A blockquote is a sentence or paragraph that’s been specially formatted to draw attention to the reader. To create a block quote, all you have to do is preface a line with the “greater than” caret (>). For example: Input: >Blockquote (You can mention your code here) Output: If your quote spans multiple paragraph, then you need to add caret on each line. Input: >Blockquote (You can mention your code here).   >Multiple quotes added Output: Lists: There are two types of lists, ordered and unordered To create an unordered list, you’ll want to preface each item in the list with an asterisk ( * ). Each list item also gets its own line. For example, a grocery list in Markdown might look like this: Input: * Milk * Eggs * Salmon * Butter   Output: An ordered list is prefaced with numbers, instead of asterisks Input: 1. Milk2. Eggs3. Salmon4. Butter   Output: List with one more depth: All you have to do is to remember to indent each asterisk one space more than the preceding item. Input: * Milk products * paneer * cheese * Barfi * Butter * Buttermilk Output: Paragraphs: We can forcefully insert a new line by clinking enter. You can accomplish soft breaking of lines by inserting two spaces after each new line. Sometimes there is need for formatting paragraphs in lists. This can be achieved as below Input: 1. Crack three eggs over a bowl. Now, you’re going to want to crack the eggs in such a way that you don’t make a mess. If you _do_ make a mess, use a towel to clean it up! 2. Pour a gallon of milk into the bowl. Basically, take the same guidance as above: don’t be messy, but if you are, clean it up! Output: Tables: Input: | Left align | Right align | Center align | |:———– |————:|:————:| | left       |        right|     center   | Output: Blocks: Blocks can be added by adding 2 spaces before line starts. Input: POST/GetOrderStatus Output: Highlighted text: Input: `renders` Output: Some online Markdown editor links listed below where you can try all the styling. http://markdownlivepreview.com/ https://dillinger.io/ Hope you find this helpful!

Introduction: Formatting text in Markdown has a very gentle learning curve. It doesn’t do anything fancy like change the font size, colour, or type. All you have control over is the display of the text—stuff like making things bold, creating headers, and organizing lists. Styling: Bold and Italic: 1) To make a phrase italic in Markdown, you can surround words with an underscore (_ ). For example, _this_ word would become this 2) To make phrase bold in Markdown, you can surround words with two asterisks ( ** ). For example, **really** word would become really Headers: To make headers in Markdown, you preface the phrase with a hash mark (#). You place the same number of hash marks as the size of the header you want. For example, for a header one, you’d use one hash mark (# Header One), while for a header three, you’d use three (### Header Three). Input: #Header one ##Header two ###Header three ####Header four #####Header five ######Header six   Output: Header one Header two Header three Header four Header five Header six     Making links: There are two different link types in Markdown, but both render the exact same way. The first link style is called an inline link. To create an inline link, you wrap the link text in brackets ( [ ] ), and then you wrap the link in parenthesis ( ( ) ). For example, to create a hyperlink to www.github.com, with a link text that says, Visit GitHub!, you’d write this in Markdown: [Visit GitHub!](www.github.com). The other link type is called a reference link. As the name implies, the link is a reference to another place in the document. Here’s an example of what we mean: Input: Here’s [a link to something else][another place].   [another place]: www.github.com Output: Images: Images also have two styles, just like links, and both render the exact same way. The difference between links and images is that images are prefaced with an exclamation point ( ! ). The first image style is called an inline image link. To create an inline image link, enter an exclamation point ( ! ), wrap the alt text in brackets ( [ ] ), and then wrap the link in parenthesis ( ( ) ). (Alt text is a phrase or sentence that describes the image for the visually impaired.) For example, to create an inline image link to https://www.cloudfronts.com/wp-content/uploads/2018/03/PostmanDocumentation.png, with an alt text that says, Postman Documentation, you’d write this in Markdown: . For a reference image, you’ll follow the same pattern as a reference link. You’ll precede the Markdown with an exclamation point, then provide two brackets for the alt text, and then two more for the image tag. At the bottom of your Markdown page, you’ll define an image for the tag. Input: [Reference Link][Postman Documentation]   [Postman Documentation]:https://www.cloudfronts.com/wp-content/uploads/2018/03/PostmanDocumentation.png Output: Reference Link In the next blog, we will discuss some more styling related to MarkDown Language.

Introduction: Postman is the complete toolchain for API developers. It supports every stage of API Lifecycle and in this blog, we will have a look on how a beautiful web-viewable document can be created. Postman’s API documentation feature lets you share public and private API documentation. Pre-requisites: 1) Postman 2) Web service already created. Steps to be followed: Step 1: Create the documentation from the- New Button Launch Screen Step 2: Click on Documentation tab. Step 3: You can create new API request or you can create document for existing collections. In this example we will cover for existing collections. Step 4: Tab where you can enter the description will be visible. In this tab we can write in Markdown language. This editor support Markdown language only. The syntax for writing it is simple and non-developer can also write it. Markdown styling details can be found in below link. There are examples on styling with header, tables, links etc. Markdown Styling Step 5: When all the styling is done, documentation link will be provided. Step 6: When you click on the link, your documentation will be visible. When you click on Publish, the link will be available publicly and you can share with your team members. Anyone with this link will be able to view the document and run web service requests. When you click on Expand, complete request is visible. Same way responses can be added by saving an example You can also go through the documentation provided by Postman. The link is given below: https://www.getpostman.com/docs/v6/

Introduction: In this blog, we will have a look on how a web service can be published on IIS and made publicly available. Description: Publishing is the process to make an Application code suitable to host on the Server by merging DLLs and keeping only the required UI code. The steps required for hosting a web Service to the Server are as follows: Steps to be followed: Step 1: Create the Application in Visual Studio. 1. Click on New Project → Go to Visual Studio Tab → Click on Web → Select ASP.NET Web Application → Change the name of the project and set the location for the project → Click OK. 2. Select Empty template as we will write the code by our self and not use the existing code → Select Web API and make sure Host in cloud is unchecked as we will be hosting the web service on IIS → Click OK. 3. When you click OK, project will be created and you can make modifications as per your requirement. Add a controller and write the HTTP methods you want to call. 4. We will create an empty controller and add the required methods. 5. Add the methods and add the routing action required so we can call it from anywhere. Step 2: 1. Right click on the project created and click Publish. b. Select the Publish Target. Select the option, where you want to save the published file. There are lot of options given by Visual Studio to save the published files, as shown below. In the above image, we have seen there are many options listed to publish the application: Microsoft Azure App Service: You need Azure subscription to use this option. Import: This option is used to publish applications which is based on the predefined configuration files given by hosting provider, which will directly publish the files in your hosting provider environment. Custom: Publish the application in your own machine location or FTF Server. Microsoft Azure API apps: This option is used to publish REST API’s Services in Cloud. Microsoft Azure virtual machine: This option is used to publish the Application in Microsoft virtual machine which requires an Azure subscription. 3. Create Custom profile and give the profile name as per your requirement and Click OK. 4. Choose Publish Method. Now configure the created profile, which decides where and how to publish the files and select the Target location of your local system in which you want to store the published files, as shown below. 5. Choose Publish code type: What type of code you want in production environment by choosing release or debug option, as shown below. Debug: Choose this option when you want to debug your application after the hosting. Release: Choose this option when you do not want to debug the Application after hosting and make the Application faster. Click Next. 6. Preview the configuration: Now click Publish option and watch the output Windows. You will get a message that your application is published successfully. 7. Now navigate to the target folder and see the published files, as shown below. Conclusion: We have seen our published code, which is used to host in IIS. I hope from all the preceding examples, we learned how to publish ASP.NET Web API Service in File system.