When migrating large text files with many columns in Microsoft Dynamics CRM using Scribe Insight, sometimes it’s more efficient to manually edit the QETXT.ini file. A good example of this would be when migrating from text file exports from Salesforce.com to Microsoft Dynamics CRM.
How many times have you set up a connection to a text file using a sample file only to later get the full data set and realize all of your columns are too small or of the wrong data type? You can save yourself time and energy by manually editing the QETXT.ini file. The QETXT.ini is a text file that is created automatically when using the Scribe Text Wizard to create a connection to a text file.
To see an example of the QETXT.ini, you can navigate to the TextData samples that get installed with Scribe Insight.
In this example, we will be using the sample Company.dts that Scribe provides to illustrate how to change the QETXT.ini. When using the Scribe connection wizard to define text connections, it will define the length of any characters fields by default to the longest value in the current file. We want to change all character columns to a length of 100.
- First let’s look at the column definitions prior to editing. Notice the column lengths vary and were likely set automatically by the column lengths at time of first connection.
- Now open up the QETXT.ini and edit the column lengths. Notice each new text connection is started with the connection name in brackets [ ].
- For each VARCHAR field, change the length to 100 in two locations.
- Repeat until all VARCHAR fields have been updated.
- That’s it! Once you re-open the Scribe job, you will see that all of the column lengths have been updated.
As you can see, editing the QETXT.ini file manually can save you time while importing data into Microsoft CRM using Scribe. Try it out for editing columns lengths, data types or even data masks.