It is possible to define customised user defined fields, added to Sage 200 in ObjectStore Builder, in the PostTrans templates:

• Sage200asset - Asset
• Sage200cust - Customer
• Sage200custCont - Customer Contact
• Sage200custDel - Customer Delivery Address
• Sage200supp - Supplier
  Sage200suppCont - Supplier Contact
• Sage200stk - Stock
• Sage200nom - Nominal Accounts
• Sage200manLab - Resource Labour
• Sage200manTool - Resource Tools
• Sage200manMac - Resource Machine
• Sage200TransNom - Nominal Journals Header/Lines
• Nominal Journal - PendingNominalBatchEntry Table
• Reversing/Recurring – PendingNominalBatchEntry Table
• Sage200Trans - Purchase/Sales Orders Header/Lines
• Separate definitions for Standard, Free Text, Comment and Additional Charge line types
• Sage200Trans - Purchase/Sales Invoices Header/Lines

The tag window gives access to 10 user defined fields in these areas, which can be added to a PostTrans template in the same way as any other PostTrans Tag.

How to map a ObjectStore Builder field

In order for PostTrans to extract, and import into a customised field, we first have to map the desired PostTrans Tag to the customised field added in Sage 200 using ObjectStore Builder.

To do this we go to your online account, from the Setup window:

Next go to the settings adjacent to the PostTrans Sage 200 License:

This gives access to:

Shown is the example below.

How to alter PostTrans Schema

The PostTrans schema defines the tags and Sage 200 field mappings.   10 user defined fields are available in the areas listed above, which can be easily mapped in the XML <customTags> section:

<customTags>

Data

</customTags>

When this section changes PostTrans rolls back any existing changes and applies all customised settings again.

Force PostTrans to read new settings

in Setup, press the Refresh Registration button to download the latest settings.  Other copies of PostTrans, you may be using, will download this file when first used at the start of the day.

Example – Extended the Customer Record

We have added 3 extra data fields in the Customer Table (PostTrans Tag Sage200cust) in Sage 200:

Sage Data Name	Data Type	Length	Short Name	Note
CustGrade	Text	2	Grade	Customer Grade
CustGradeNote	Text	150	Note	A note on the customer
CustSize	Integer	0	Size	Size of Customer

We can define one of the CuUser1-10 tags as our Sage 200 customised fields:

<customTags>

edit|all|Sage200cust|CuUser1|text|2|CustGrade|Grade|Customer Grade|||

edit|all|Sage200cust|CuUser2|text|150|CustGradeNote|Note|A note on the customer|||

edit|all|Sage200cust|CuUser3|integer|0|CustSize|Size|Size of Customer|||

</customTags>

Syntax:

edit|Company|PostTransType|PostTransTag|DataType|Size|Sage200FieldName|ShortName|Description|Options|LookupID|LookupString

Where:

Company – Is the Company Code to apply this change to, or “all” for all companies

PostTransType – PostTrans Template Type e.g. Sage200cust,Sage200supp,Sage200TransNom or Sage200stk

PostTransTag – PostTrans tag name to edit

DataType – date, double, integer, text, yes/no, memo

Size – Length of string

Sage200FieldName – The name in Sage 200

ShortName – Title shown in sheet when added by PostTrans

Description – Description used in cell comment (Optional)

Options – future options

LookupID and Lookup String – Enable In Cell Searching

In Cell Searching

If LookupID is set to 2, then PostTrans will provide a lookup based on text values.   The Lookup String should then be in the format of:

Window Title,OPTION1,Option 1 Desc,OPTION2,Option 2 Desc,OPTION3,Option 3 Desc

For example:

Area Codes,EAST,East region,WEST,West Region,NORTH,North Region,SOUTH,South Region

How to add to the PostTrans Schema

If 10 fields are not enough we can copy existing fields. For example, if presume we have used all CuUser1-10 tags, we can add 3 more and define them:

<customTags>

copy|all|Sage200cust|CuUser1|CuUserZ11

copy|all|Sage200cust|CuUser1|CuUserZ12

copy|all|Sage200cust|CuUser1|CuUserZ13

rem …edit 10 definitions already defined…

rem now edit copied definitions

edit|all|Sage200cust|CuUserZ11|text|2|CustGrade|Grade|Customer Grade|||

edit|all|Sage200cust|CuUserZ12|text|150|CustGradeNote|Note|A note on the customer|||

edit|all|Sage200cust|CuUserZ13|integer|0|CustSize|Size|Size of Customer|||

</customTags>

Syntax:

copy||PostTransType|PostTransTag|NewTagName

Where:

Company – Is the Company Code to apply this change to, or “all” for all companies

PostTransType – PostTrans Template Type e.g. Sage200cust,Sage200supp,Sage200TransNom or Sage200stk

PostTransTag – PostTrans tag name to copy.  This must be one of the xxUserX fields

NewTagName – new name to use.  Must not already exist, so we suggest adding “Z” thus ensure uniqueness

Comments

To add comments without causing errors, prefix the line with “rem”

Transaction Header and Lines Schema

When importing Nominal and Invoice Transactions, we have 10 user definables for the header (THUser1-10), and 10 user definables for the lines (TLUser1-10).

Sales Orders have potentially 4 different line types, and thus have 4 sets of 10 definables for each line type:

• Standard (TLUser1-10)
• Free Text (TLUser11-20)
• Additional Charge (TLUser21-30)
• Comment (TLUser31-40)

Checking Process was successful

These changes are applied when PostTrans reads the tags for the open sheet.  If an error occurs during applying changes, PostTrans will display a log file, listing detailed error messages and take the user to this page to aid them.

Once setup, no error should ever be displayed.

The log can also be accessed from PostTrans Setup window, under the “View >> serverSettings log”.