...

√

...

√

...

√

...

The Advance Positional schema activity defines the procedure to read data from and write data to a multiple record format file. You can do this by specifying the names and positions of the fields from which you want to fetch the data from.
This feature is available in:

...

Enterprise

...

Premier

...

Professional

...

Express

Steps to create Advance Positional schema

1. On the Adeptia Suite homepage, go to Configure > Services > Schema and then click the Adv. Positional. The Manage Adv. Positional Schema screen is displayed (see Figure 221).

   

   Figure 221: Manage Advance Positional Schema

2. Click the Create New link. This action will show the Create Advance Positional Schema screen.
3. Enter the name and description for Advance Positional Schema in the Name and Description textboxes respectively.
4. You need to create the schema definition for the Advance Positional Schema. You can define the schema in three ways. These are outlined as:
    
   • Import Definition file
   • Use Data Dictionary
   • Enter the Fields Sequentially

5. Select the Import Definition File radio button, select the type of file from the dropdown list, and then click the Browse button to select the file that you want to use for defining the schema using[ the definition file .

   
    

6. To define the schema using a data dictionary, click the Use Data Dictionary radio button, select the name of the data dictionary from the dropdown list, and then click the Select Record button. This will display you the Select Record screen (see Figure 222).

   
   Figure 222: Select Data Dictionary

   Info
   To know, how to create Data Dictionary, refer to the Creating Data Dictionary section.

7. This screen will display you the name of the data dictionary and a list of all the records that are in the dictionary. Select the checkbox against the record that you want to display in the Advance Positional schema.

   Info
   To display all records, select the Select All checkbox.

8. Click OK. This closes the Select Record screen and displays the selected records under Record Definition on the Manage Advance Positional Schema screen (see Figure 223). You can view or delete a record from this screen by clicking the appropriate button for that record.

   

   Figure 223: Create Record Definition using Data Dictionary

9. To enter the fields manually, select the Enter the Fields Sequentially Using radio button and then click Record Definition. This action will further expand to display the Record Definition fields (see Figure 224). 

   

   Figure 224: Create Record Definition

10. Enter the name and description of the field in the FieldName and Description textboxes respectively.
11. Select the type of data from the Type dropdown list. For data type selection, please refer to Table 2.
12. If data type is Date, select the format of date and time from the DateFormat and TimeFormat dropdown lists respectively.
13. To define field position select one of the following options:
    
    • Field Length
    • Start & End Positions
14. To define the field position using field length, select the Field Length radio button and then enter the length of the field in the Length field.
15. To define the field position using start and end position, select the Start & End Position radio buttons.
16. Enter the start position of the field in the Start textbox.

17. Enter the end position of the field in the End textbox.

    Info
    The starting position of a row in a positional file is 1. In a positional file, the schema counts a tab as one position and not eight positions. By default, the schema creates these field positions in a sequence. You can also create a schema with fields that are not in sequence. For details, refer to the Defining Field Positions Non-Sequentially section.

18. Select the alignment of the field from the Align dropdown list.

    Info
    From Align select  L if the field is left aligned.  R if the field is right aligned.   To insert rows, specify the number and position of the rows that you want to add in the Number of Rows and at Position fields respectively and then click the Add Row button. You can add a maximum of 99 rows at a time.

19. Select the Skip checkbox if you want to skip some fields while generating the XML for your schema. For example, your source file has over 1500 fields, but you only need to use 1000 fields. This Skip checkbox will omit the 500 unrequired fields and it will not read them when it parses the data to XML. However the fields will be visible in the file. If you create the schema using an existing XSD, then the skipped fields will appear blank. However, when you will use the same schema in other activities such as Mapping, it will display all the fields of the file.

    Info

    The skipping of fields is useful in case where a standard XSD has a large number of fields. Skipping reduces the size of the XML which will now contain the fields that we require.   While editing an existing schema, the field file that you will download, the Adeptia Suite will represent the skipped fields by 'T' and the unskipped fields by 'F' (see Figure 225). This depiction will remain the same while viewing the Print-Friendly Page.

    
    
    Figure 225: Skipped and Unskipped Fields in the Data File

20. Enter the name of any field in the Record Identifier textbox and the value of the field in the Value textbox.

    Info
    Record Identifier is used to identify the records which will be parsed through this definiton. In Value you can also use regular expressions. To use regular expression enable Is Regex.

21. Click Add Record to define another set of data and repeat the steps from 6 to 20.
22. After defining records you need to define their hierarchy. This is mandatory for creating an Advance Positional schema.

23. Once you finish adding the records, defining the Record Identifiers, and their values, click the Refresh button under Hierarchy Definition. This populates the Record Identifiers of the defined records, in the Record ID field under Hierarchy Definition (see Figure 226).

    

    Figure 226: Create Record Hierarchy Definition

24. Select a record from the Record ID list box.
25. Select Y or N from the Required list box to indicate if a record will appear in the source file.
26. In the minoccur field, enter the minimum number of occurrences that you want a record to appear in the source file. If the Required field has the value as 'Y', then the minoccur field should at least have a minimum 1 occurrence in the source file. If the Required field has the value as 'N', then the minoccur field can be 0.
27. In the maxoccur field enter the maximum number of occurrences that you want a record to appear in the source file. The maximum allowable value that you can enter in the maxoccur field is 2147483647.

Using Hierarchy at Root Level

Steps to use a hierarchy at the Root Level

1. Click the Add RootRecord button. This creates a record at the same level as that of the previous root record as shown in the figure (see Figure 227).

   

   Figure 227: Create Root Record

2. Select a record from the Record ID field and enter all the related information.

3. Repeat step 24-27 to create another root record.

   Info
   Every record must have a unique Record ID. For example, if the first root record is John , then you need to select Stationary in the next root record.

   Using Record at Child Level

4. Steps to use a record at the Child Level

...

Anchor
_Toc87263848 _Toc87263848

Anchor
creatingdatabaseschema creatingdatabaseschema

Anchor
_Toc110927910 _Toc110927910

Anchor
_Toc112820652 _Toc112820652

Anchor
_Hlt113171631 _Hlt113171631

Anchor
_Hlt113171708 _Hlt113171708

Anchor
_Hlt113171786 _Hlt113171786

Anchor
_Toc114994111 _Toc114994111

Anchor
_Hlt114994286 _Hlt114994286

Anchor
_Toc134848072 _Toc134848072

Anchor
_Toc144314350 _Toc144314350

Anchor
_Hlt145312006 _Hlt145312006

Anchor
_Hlt145312018 _Hlt145312018

Anchor
_Hlt145312026 _Hlt145312026

Anchor
_Hlt147206877 _Hlt147206877

Anchor
_Hlt147206920 _Hlt147206920

Anchor
fieldpositionsnonsequential fieldpositionsnonsequential

Anchor
_Hlt185610898 _Hlt185610898

Anchor
_Hlt185787240 _Hlt185787240

Anchor
_Hlt186968181 _Hlt186968181

Anchor
_Hlt239858259 _Hlt239858259

Anchor
_Defining_Field_Positions _Defining_Field_Positions

Defining Field Positions Non-Sequentially

By default, XML creates the fields of a schema sequentially. At times, you may need to create a schema with field positions that are not in sequence. For example, there are 500 fields in the source file and you need to create a schema by using only 200 fields. But these 200 fields are not sequential. In such a case, you can create a schema by defining the start and end position of these fields in a non-sequential manner.

...

Info
You can also change the field positions non-sequentially, while editing the schema. This feature is available for Advance Positional and Positional Schemas only.

 

Anchor
_Viewing_Print-Friendly_Page _Viewing_Print-Friendly_Page

Anchor
_Ref156148053 _Ref156148053

Anchor
_Toc177977254 _Toc177977254

Anchor
_Toc226191154 _Toc226191154

Anchor
_Toc315524591 _Toc315524591

Anchor
_Toc317062177 _Toc317062177

Anchor
_Toc344890166 _Toc344890166

Anchor
_Toc385441474 _Toc385441474

Anchor
_Toc387747310 _Toc387747310

Anchor
_Toc387748581 _Toc387748581

Anchor
_Toc401308905 _Toc401308905

Viewing Print Page

You can view the summary, record definition, and hierarchies of a schema in edit mode.

...

Anchor
_Toc177977255 _Toc177977255

Anchor
_Toc226191155 _Toc226191155

Anchor
_Toc315524592 _Toc315524592

Anchor
_Toc317062178 _Toc317062178

Anchor
_Toc344890167 _Toc344890167

Anchor
_Toc385441475 _Toc385441475

Anchor
_Toc387747311 _Toc387747311

Anchor
_Toc387748582 _Toc387748582

Anchor
_Toc401308906 _Toc401308906

Special Usage Scenario

Anchor
_Toc226191156 _Toc226191156

Anchor
_Toc315524593 _Toc315524593

Anchor
_Toc317062179 _Toc317062179

Enable IsRemoveHeader Attribute
If you use Advance Positional schema as a target schema then, you can set the IsRemoveHeader attribute. This attribute will help you to skip the insertion/updation of a record from the source file to the target database. You only need to set the IsRemoveHeader attribute to 'True'. This attribute is set in the Data Mapper, while mapping source and target schemas.
 

Steps to set IsRemoveHeader attribute
In the Data Mapper, load the source and target schemas. In the target schema, there is an IsRemoveHeader attribute.

...