PSIcapture How-to: Adding Carriage Returns for Certain Migrations

Introduction

If you are using Migrations such as Text outputs or similar, you may encounter scenarios where you wish or need to have a carriage return.

 

Step-by-step Guide

In order to do this, you will need to configure the following:

  1. Create an Index Field and set the datatype to "Memo". Move this field to the bottom of the list, so it is the last Index Field in the list.

    field1.png

  2. You can also choose to "Hide" this field under "Field Options" so it is not displayed to the user and it cannot be modified as shown below:

    2.png

  3. Check "Use a Custom Validation Script" and click on the "Edit" button located on the bottom right of the window.

    3.png 
  4. Launch the script editor, and go to DocumentDataRecordInitialize
  5. Add the following into the script location:

    dataRecord
    ["newline"].Value = Environment.NewLine + Environment.NewLine;

    4.png 
  6. Click on "Build & Save" in the upper left corner of the window.
  7. Make sure that the Memo field is the last index field on the Field Settings tab in the Migration you are using.
  8. Under the Migration configuration > Field Settings, ensure that the "Carriage Return" field (or whatever the administrator has chosen to name the field) is the last in the list, as seen below:

    cr1.png

To recap, the Index Field must be configured as datatype "Memo", and it needs to be the last index field in the list of your "Indexing" fields section of the configuration. Use the custom validation script, and under the Migration Configuration, ensure that the Field Settings tab has the "Carriage Return" Index Field as the last field (all other user defined index fields must be above).

 


 

If you are still experiencing difficulties, please contact our Support team by:

 

 

 

Keywords: PSIcapture carriage return, setup carriage return PSIcapture, how to carriage PSIcapture return setup

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.