Scribd
Upload
239 views

Guide - Understanding Dynamic Syntax

B1UP Dynamic Syntax

Uploaded by

Rudy Lee
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
239 views

Guide - Understanding Dynamic Syntax

B1UP Dynamic Syntax

Uploaded by

Rudy Lee
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

B1 Usability Package Guide

Guide Understanding Dynamic Syntax


Throughout B1 Usability Package you will encounter the use of the dynamic syntax. This is inspired by the
SAP formatted search syntax and allows you to do SQL and other arguments with syntax code that upon
execution will replace the dynamic syntax with the data from the current SAP Business One window.

The syntax
There are basically 2 syntaxes; the item syntax and the table syntax.

The Item Syntax


This is the most common syntax and allow you to inject a value of an SAP Window item into SQL and
arguments. The syntax is as follows:

$[$<ItemUID>.<ColumnUID>.<DataType>]
Where <ItemUID>, <ColumnUID> and <DataType> is the 3 things you need to provide.

Copyright 2014 Boyum IT A/S

Page 1/8

B1 Usability Package Guide

Lets look at a sample:

Here we have the Sales order were we have pointed out 6 fields that we will look at. They all represent the
different datatypes we will encounter in SAP Business One
1.
2.
3.
4.
5.
6.

String values (Customer Name)


Integer values (Document Number)
Dates (Posting Date)
Data on line level (Price After Discount)
Decimal values (Discount)
Decimal values mixed with currency codes (Document Total)

We will now look at each and determine how we translate into the dynamic syntax.

Copyright 2014 Boyum IT A/S

Page 2/8

B1 Usability Package Guide

String values (Customer Name)


Its item UID is 54 and the type is a string.
It is not on line level so there are no columnUid involved (we indicate this by setting it to 0)
The string data type in the syntax is either shown by to enter STRING or the more popular 0 (because it is
faster to write).
With this information our dynamic value will be:

= $[$54.0.STRING]
= $[$54.0.0]
If we used this in an SQL-sentence:

SELECT $[$54.0.0] = SELECT 'Parameter Technology'


Integer values (Document Number)
Its item UID is 8 and the type is a integer.
It is not on line level so there are no columnUid involved (we indicate this by setting it to 0)
The integer data type in the syntax is shown by to entering NUMBER.
With this information our dynamic value will be:

= $[$8.0.NUMBER]
If we used this in an SQL-sentence:

SELECT $[$8.0.NUMBER] = SELECT 13


Dates (Posting Date)
Its item UID is 10 and the type is a date.
It is not on line level so there are no columnUid involved (we indicate this by setting it to 0)
The date data type in the syntax is shown by to entering DATE.
With this information our dynamic value will be:

= $[$8.0.DATE]
If we used this in an SQL-sentence:
Copyright 2014 Boyum IT A/S

Page 3/8

B1 Usability Package Guide

SELECT $[$8.0.DATE] = SELECT '2006-03-30'


(2006-03-30) is an invariant standard of dates, so you wish to compare dates please use this format.
Data on line level (Price After Discount)
Its item UID is 38 and the type is a mix of decimals and currency.
This is on line level so we also need to set the ColumnUid which is 17
The decimal/currency data type in the syntax is either shown by to entering NUMBER or CURRENCY1.
With this information our dynamic value will be:

= $[$38.17.NUMBER]
= $[$38.17.CURRENCY]
If we used this in an SQL-sentence:

SELECT $[$38.17.NUMBER] = SELECT 4200.00


Decimal values (Discount)
Its item UID is 24 and the type is a decimal.
It is not on line level so there are no columnUid involved (we indicate this by setting it to 0)
The decimal data type in the syntax is shown by to entering NUMBER or CURRENCY.
With this information our dynamic value will be:

= $[$24.0.NUMBER]
= $[$24.0.CURRENCY]
If we used this in an SQL-sentence:

SELECT $[$24.0.NUMBER] = SELECT 10.500

Before version 2.740 you need to use CURRENCY as datatype here. After version 2.740 NUMBER and CURRENCY
work the same way. This was done to be closer to the Formatted Search Syntax

Copyright 2014 Boyum IT A/S

Page 4/8

B1 Usability Package Guide

Decimal values mixed with currency codes (Document Total)


Its item UID is 29 and the type is a mix of decimals and currency.
It is not on line level so there are no columnUid involved (we indicate this by setting it to 0)
The decimal/currency data type in the syntax is either shown by to entering NUMBER or CURRENCY2.
With this information our dynamic value will be:

= $[$29.0.NUMBER]
= $[$29.0.CURRENCY]
If we used this in an SQL-sentence:

SELECT $[$29.0.NUMBER] = SELECT 2173.18


Extensions to dynamic item syntax
Other than the normal $[$item.col.type] B1UP add a few additional features to the syntax
Feature
.row extension

ROWSHEADER

Description
This syntax extend .row (aka $[$item.col.type.row]) so you can target a
specific row. You can write a specific row number or the keywords .FIRST,
.LAST, .LAST-1, .SELECTED and .FOCUSED
For more on this syntax please see the following video:
http://youtu.be/SdCUS9IZF7Q
If you need to target a row header of a matrix it is done like this:

$[$<MatrixItemUid>.ROWSHEADER.0]

Before version 2.7.4.0 you need to use CURRENCY as datatype here. After version 2.7.4.0 NUMBER and CURRENCY
work the same way. This was done to be closer to the Formatted Search Syntax

Copyright 2014 Boyum IT A/S

Page 5/8

B1 Usability Package Guide

The Table Syntax


In a few cases like User defined Fields we have a window that behind have some data but the data is not
shown to the user. If that is the case we use the table syntax instead.

Here we have a user defined field called Kit Number but since it is only part of the side-bar and not part of
the main window we need to use the table syntax:

$[<TableName>.<FieldId>.<DataType>]
Working the same way as with the item-syntax we need to provide the 3 values needed.
The table the field is on is ORDR and the field is U_KitNo
The data type is string (STRING or 0)

= $[ORDR.U_KitNo.STRING]
= $[ORDR.U_KitNo.0]

Copyright 2014 Boyum IT A/S

Page 6/8

B1 Usability Package Guide

If we used this in an SQL-sentence:

SELECT $[ORDR.U_KitNo.0] = SELECT 'A1234'


Special keyword syntax
NB: THESE SPECIAL KEYWORDS ARE SUPPORTED FORM B1UP 2.910 AND ABOVE
Other than the two syntaxes above, SAP formatted searches contains two additional keywords that can be
used in B1UP as well.
Formatted Search keywords
Keyword
$[USER]

Description
Gives you the unique id of the user logged in.

$[PERIOD]

NB: PLEASE NOTE THAT THIS IS NOT THE USERNAME OF THE USER, BUT THE ID OF HIM/HER. YOU
CAN USE THE OUSR TABLE TO FIND WHAT USER HAVE WHAT ID OR USE THE B1UP SPECIFIC
KEYWORD $[USERNAME]
Gives you the id of the currently used posting period

B1UP specific keywords


To extend the formatted search syntax, the B1UP accepts the following keywords
Keyword
$[USERNAME]
$[DATABASENAME]
$[LOCALIZATION]
$[COMPANYNAME]
$[SERVERNAME]
$[SERVERDATE]
$[SERVERTIME]
$[SYSTEMID]
$[INSTALLATIONID]
$[CURRENT_PANE]
$[CURRENT_LANGUAGE]

Description
The username of the currently logged in user
The name of the database logged into
The Database country localization
The name of the company
The name of the server
The date of the server presented in the client format
The time of the server presented in the client format
The System Id of the company
The Installation Id of the company
The forms current pane
The current language of the B1 Client in a numeric form
1 = Hebrew, 2 = Spanish (Argentina), 3 = English (United States), 5 = Polish, 6 = English (Singapore), 7 =
Spanish (Panama), 8 = English (United Kingdom), 9 = German, 10 = Serbian, 11 = Danish, 12 = Norwegian, 13
= Italian, 14 = Hungarian, 15 = Chinese, 16 = Dutch, 17 = Finnish, 18 = Greek, 19 = Portuguese, 20 = Swedish,
22 = French, 23 = Spanish, 24 = Russian, 25 = Spanish (Latin America), 26 = Czech, 27 = Slovak, 28 = Korean,
29 = Portuguese (Brazil), 30 = Japanese, 31 = Turkish, 35 = Traditional Chinese (Hong Kong)

$[NEWID]

The Id of the currently added object (Example DocEntry of a newly added


Invoice). WARNING: THIS KEYWORD WILL ONLY BE REPLACED IF THE EVENT IS DATA ADD
AND DATA UPDATE EVENTS IN ACTIONSUCCESS (THE KEYWORD WILL NOT BE REPLACED IN
OTHER EVENT-TYPES)
$[ROW]
The row of the event
$[ATTACHMENT_FOLDER] The path to SAPs Attachment folder
$[BITMAP_FOLDER]
The path to SAPs Bitmap (picture) folder

Copyright 2014 Boyum IT A/S

Page 7/8

B1 Usability Package Guide

$[WORD_FOLDER]
$[EXTENSION_FOLDER]
$[EXCEL_FOLDER]
$[XML_FOLDER]

The path to SAPs Word folder


The path to SAPs Extension folder
The path to SAPs Excel folder
The path to SAPs XML folder

Copyright 2014 Boyum IT A/S

Page 8/8

You might also like