In templates, you have the possibility to use keywords. These keywords allow you to create a pattern to fill in a field.
 |
Keywords can only be used in text fields. |
|
Keywords can be used in combination with fixed text. |
1 Date formats
Day = d
Month = M
Year = y
Hour = H
Minutes = m
End of month: EOM
Begin of month: BOM
2 List of keywords
On several objects, keywords can be used on all the fields in the system.
| Keyword function
|
Fieldcode
|
Parameter 1
|
Parameter 2
|
Example input
|
Example output
|
| HEADERFIELD
|
SUPPCODE
|
CODE
|
|
#{HEADERFIELD(SUPPCODE,CODE)}
|
6
|
|
|
SUPPCODE
|
NAME
|
|
#{HEADERFIELD(SUPPCODE,NAME)}
|
Belgacom
|
|
|
SUPPVATID
|
|
|
#{HEADERFIELD(SUPPVATID)}
|
BE0202239951
|
|
|
CUSTCODE
|
CODE
|
|
#{HEADERFIELD(CUSTCODE,CODE)}
|
6
|
|
|
CUSTCODE
|
NAME
|
|
#{HEADERFIELD(CUSTCODE,NAME)}
|
Belgacom
|
|
|
CUSTVATID
|
|
|
#{HEADERFIELD(CUSTVATID)}
|
BE0202239951
|
|
|
JOURNAL
|
CODE
|
|
#{HEADERFIELD(JOURNAL,CODE)}
|
600
|
|
|
JOURNAL
|
NAME
|
|
#{HEADERFIELD(JOURNAL,NAME)}
|
Purchase
|
|
|
INVOICENR
|
|
|
#{HEADERFIELD(INVOICENR)}
|
001201600424
|
|
|
INVDATE
|
dateformat
|
calculation
|
#{HEADERFIELD(INVDATE,yyyy,+1y)}
|
05/09/2014 becomes 2015
|
|
|
COMMENT1
|
|
|
#{HEADERFIELD(COMMENT1)}
|
Comment
|
|
|
OGM
|
|
|
#{HEADERFIELD(OGM)}
|
002637611771
|
|
|
NETAMNT
|
|
|
#{HEADERFIELD(NETAMNT)}
|
100.00
|
|
|
VATAMNT
|
|
|
#{HEADERFIELD(VATAMNT)}
|
21.00
|
|
|
TOTAMNT
|
|
|
#{HEADERFIELD(TOTAMNT)}
|
121.00
|
|
|
CURRENCY
|
CODE
|
|
#{HEADERFIELD(CURRENCY,CODE)}
|
EUR
|
|
|
CURRENCY
|
NAME
|
|
#{HEADERFIELD(CURRENCY,NAME)}
|
Euro
|
|
|
YEAR
|
CODE
|
|
VIS: #{HEADERFIELD(YEAR,CODE)}
|
2016
|
|
|
YEAR
|
NAME
|
|
VIS: #{HEADERFIELD(YEAR,NAME)}
|
2016
|
|
|
PERIOD
|
CODE
|
|
EIS & OIS: #{HEADERFIELD(PERIOD,CODE)}
|
2016-7
|
|
|
PERIOD
|
NAME
|
|
EIS & OIS: #{HEADERFIELD(PERIOD,NAME)}
|
2016-7
|
| TECHNICALFIELD
|
SCANBATCH
|
|
|
#{TECHNICALFIELD(SCANBATCH)}
|
04/05/16 13:47:29
|
|
|
SCANUSER
|
|
|
#{TECHNICALFIELD(SCANUSER)}
|
ONEA
|
|
|
SCANNINGDATE
|
dateformat
|
calculation
|
#{TECHNICALFIELD(SCANNINGDATE,yyyyMMdd,EOM)}
|
05/09/2014 becomes 20140930
|
|
|
INCOMINGDATE
|
dateformat
|
calculation
|
#{TECHNICALFIELD(INCOMINGDATE,yyyyMMdd,BOM)}
|
05/09/2014 becomes 20140901
|
| COMPANYNAME()
|
|
|
|
#{COMPANYNAME()}
|
Onea
|
| USERNAME()
|
|
|
|
#{USERNAME()}
|
ONEA
|
| USERREALNAME()
|
|
|
|
#{USERREALNAME()}
|
Onea
|
| CURRENTDATE()
|
|
dateformat
|
calculation
|
#{CURRENTDATE(yyyyMMdd)}
|
system date
|
3 Examples
| Keyword
|
Example output
|
| Consumption #{HEADERFIELD(SUPPCODE,NAME)} #HEADERFIELD{(INVDATE,yyyy)} |
Consumption Belgacom 2016
|
| #{HEADERFIELD(INVDATE,yyyy,-1y)} |
2015
|
| #{HEADERFIELD(INVDATE,MM,+1M)} |
04
|
| Scanned: #{TECHNICALFIELD(SCANNINGDATE)} |
Scanned: 20160504150913
|
Scanned: #{TECHNICALFIELD(SCANNINGDATE,yyyy)}-#{TECHNICALFIELD(SCANNINGDATE,MM)}-#{TECHNICALFIELD(SCANNINGDATE,dd)}
#{TECHNICALFIELD(SCANNINGDATE,HH)}:#{TECHNICALFIELD(SCANNINGDATE,mm)}:#{TECHNICALFIELD(SCANNINGDATE,ss)} |
Scanned: 2016-05-04 15:09:13
|
 |
When an incorrect keyword is given, an error will occur when the template is applied. |
|
The keywords are case sensitive, you have to enter the upper case code of the field (not the name!) |
