Scribd
Upload
216 views

Understanding Dynamic Syntax

Dynamic syntax is inspired by the SAP formatted search syntax. It 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. There are basically 2 syntaxes; the item syntax and the table syntax.

Uploaded by

Victoria Sokolinsky
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
216 views

Understanding Dynamic Syntax

Dynamic syntax is inspired by the SAP formatted search syntax. It 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. There are basically 2 syntaxes; the item syntax and the table syntax.

Uploaded by

Victoria Sokolinsky
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

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 2011 Boyum IT A/S

Page 1/7

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. String values (Customer Name) Its item UID is 54 and the type is a string. Copyright 2011 Boyum IT A/S Page 2/7

B1 Usability Package Guide

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:

SELECT $[$8.0.DATE] = SELECT '2007-10-20'

Copyright 2011 Boyum IT A/S

Page 3/7

B1 Usability Package Guide

(2007-10-20) 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 500.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 2011 Boyum IT A/S

Page 4/7

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 495.01

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 2011 Boyum IT A/S

Page 5/7

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]
If we used this in an SQL-sentence:

Copyright 2011 Boyum IT A/S

Page 6/7

B1 Usability Package Guide

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. 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

$[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] 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

Copyright 2011 Boyum IT A/S

Page 7/7

You might also like