TRUE - Has a border
FALSE - Does not have a border

Field names from result and field names in Datawindow must be the same

dw_1.bsl.get=WareHouseStock("BW")?$select=ItemCode,IVersionId,Batch,SysNumber,UoMCode,BinCode,RFID,OnHand,Details,Status

setvar=ls_columns=
for ll_loop=1 to <dw_1.columncount>
   addvar=ls_columns=<dw_1.columnname:[ll_loop]>,
next
messagebox=Columns: <ls_columns>

With CTRL+double-click you can modify column properties (default).

Disable this functionality by setting it to false.

Example

dw_2.crtldoubleclick=false

This is the file name of the datawindow formula (PSR-File name).

For set datawindow, use the init command dw_1.init=<psr-filename>

HTML/XLS

(only read)

Other form gets all object values from a datawindow object.

There is full access to all objects inside this datawindow object. For more information, see the PowerBuilder documentation.

messagebox=<dw_1.describe=itemcode.x>

The command defines, whether it is a list, edit window, or some other object.

The following properties are allowed:

beas sets the correct style, for example underlined, border around fields, and so on.

Example:

dw_2.design=edit

With the "<dw_2.type>"  property you can check the current design in 2 areas: browse or edit

dw_x.is_type

dw_1.drag.auto=true  activates the auto-drag function

dw_1.drag.begin

dw_1.drag.end

dw_1.drag.cancel

See

setdynamicgridcols

setupcolumn

Default names for a dynamic columns are the data window name. This setting can change this default behavior.

See

setdynamicgridcols

setupcolumn

This is the id and name from the window, which usually is the psr file name of first datawindow dw_1 inside current window without folder name and postfix .psr

messagebox=<dw_1.dwname>

Dynamic browse window (columns defined with Crtl+NS)

With this variable you can define, which fields unvisible. In this case you can't see it and you can't activate this in the window settings

dw_1.unvisiblefields=field1;field2;field3...

see

dw_x.editablefields

Dynamic browse window (columns defined with Crtl+NS)

With this setting you can define, which fields editable.

If you define this, all fields, which not defined, are not editable

In window settings only fields editable, which defined in this setting or the setting is empty

dw_x.editablefields=field1;field2;field3...

see

dw_x.unvisiblefields

true=allowed, false=not allowed. Default=true

Example: Structureview - set xls export to false because you cannot use this.

dw_4.setfilter=itemcode>'a'

dw_4.filter

messagebox=Current filtered: <filtercount>, current visible: <rowcount>

A right-click on a title presents a pop-up window with the definition of the the filter/sort of the list.

This command can deactivate this behavior.

dw_4.filtersort=false

If the value is not found, value=0. If the search syntax is not correct, the value is -1.

dw_2.find=itemcode='sofa' or itemcode='table'

setvar=ll_row=<value>

if <ll_row> n> 0 then

 messagebox=Description from <dw_2.itemcode:[ll_row].value>: &

            <dw_2.itemname:[ll_row].value>

end if

Example: Returns all columns from the stamm_stl_header window.

(only if the form is active)

setvar=ls_window=stamm_stlheader_edit

setvar=ls_dw=dw_1

setvar=ls_test=<system.window.[ls_window].form.[ls_dw].getcolumns>

messagebox=<ls_test>

Window.PSR-SQL

select OITM.ItemCode+'' || ItemCode FROM OITM inner join OITW where OITW.ItemCode = OITM.ItemCode

// you have one entry per Warehouse, 6 Entries for Item A if A is linked to 6 warehouses

dw_1=grouping=itemname

// now you have one line per Itemcode

dw_2.hscrollbar=true

dw_2.hsplitscroll=true

dw_2.horizontalscrollposition2=500

Load the psr-file and initialize is:
dw_2=init=myfile.psr

No retrieve is triggerd.

An initcols is automatically performed.

dw_2.init=myfile.psr

dw_2.design=liste

// retrieve:

dw_2.retrieve

// or only connect to database

dw_2.settrans

// List window: load column definitions

dw_2.setdynamicgridcols

Example:

<dw_1.isselect> returns true/false for the current row

<dw_1.isselect:5> returns true/false for row 5

<dw_1.isselect:[ll_loop]> returns true/false for row from Variable ll_loop

Example:

dw_1.multiselect=true
dw_1.selectrow=5
messagebox=<dw_1.isselectonerow>   returns true

you can change every datawindow directly with datawindow syntax

Example:

Change height of the detail window

dw_1=modify=DataWindow.Detail.Height=70

Color and other column properties allow to work with formula

"Default Value"+Tab+"if(formula,true-Value,false-Value)"

For Tab you must use "~t"

Example:

Change Color from a field related to a formula

dw_1.modify=bez.color="0~tif(ag_id='1111',rgb(255,0,200),0)"

Execute the script after opening the window , example form_loaded

global function form_loaded
dw_1.modify=bez.color="0~tif(ag_id='1111',rgb(255,0,0),0)"
end global

if this is related to a template, you can write this in scripts from the template

More information see Appeon Powerbuilder documentation

https://docs.appeon.com/pb2019/datawindow_reference/ch05s01.html#XREF_78721_Using_DataWindow

Example:

Item List with Pictures

 
First we need the picture. We can use a template field in template definition

 
Then we must change the height of row and Picture

Follow syntax in template - Script:

dw_1.modify=DataWindow.Detail.Height=200
dw_1.modify=templatefield1_c.Height=200

You can select multiple lines with the mouse, keyboard or with commands.

Activate or deactivate multiselect: select row with Shift/Control + rowfocuschange. See selectrow, deselectrow.

Example:

dw_1.multiselect=true

To check the selected rows:

<dw_1.isselect> return true/false for current row

<dw_1.isselect:x> return true/false for row x

<dw_1.isselectonerow> return true, if min one row is marked

<dw_1.getselectentrydata> return selected data from binary field

<dw_1.getselectentryssql> return first primary field from all selected rows, all Data in ", example "value1","value2", ...

<dw_1.getselectentryrow> return all selected rows

Examples:

dw_1.multiselect=true

messagebox=<dw_1.getselectentrydata>

tools=isql=select * from "OITM" where "ItemCode" in (<dw_1.getselectentrysql>)

Examples for Work order structures

1=landscape

2=portrait

dw_2.orientation=2

global function dw_1_rightclick

// function

end global

Parameters must be separated with "="

The DataWindow must only have string arguments.

Arguments are passed 1:1. Only 10 parameters max are allowed.

dw_1.retrieve=<str_parm.belnr_id>=<str_parm.belpos_id>

Retrieves only the maximum defined rows using the general setting or this can be overwritten with maxrow.

dw_1.maxrow=999999

Example:

dw_2.setdatefilter=fromdate

It is not required to set this in dw_1, but it is required in any further data window, dw_2...7.

See

dynamiccol

dynamiccolname

dw_2.setfilter=itemcode=[myitem]

dw_2.filter

Should the user define the filter, the parameter would be "user":

dw_2.setfilter=user

dw_2.filter

or you have 2 columns (example):

dw_2.setfilter=whscode="01" and color_id=1

dw_2.filter

dw_1.setposition=behind

dw_1.setposition=tobottom

dw_1.setposition=totop

Do not use this command. Beas has its own "redraw" mode with the following order:

dw_master - dw_1 - dw_2 ... dw_7 - rtf object - html object

Sorts the current data window.

Use the datawindow syntax for arguments. Placeholders are not allowed.

Only sort data, which is loaded in current datastore.

Information:

If you load the item list, beas is loading the first 200 entries only.

If you define a setsort, beas make this setsort only for these 200 entries and not for the complete item list.

Use this function only, if all data is loaded.

Example:

dw_2.setsort=u_matgrp,itemcode

dw_2.sort

// Should the user define the sorting, the parameter would be "user":

dw_2.setsort=user

dw_2.sort

This command is required, if you do not use a retrieve command and if work with dw_2...dw_7

dw_2.init=myfile.psr

dw_2.settransaction

Alternative:

dw_2.settrans

If a connection to another database / table is required, use transaction method.

See

setdynamicgridcols

dynamiccolname

Creates a new DataWindow form:

sql2form=browse/edit=<sql command>

Up to 6 templates can be defined in template administration.

Templatefield 1-6 in lists can be set with template or with script. This is only running in user-Event.

windowevent predesign

dw_1.template.x.property=value

end event

template.x.sql	SQL-Sequence - always defined as a string, varchar(50).   Read the template information with: <template.sql.1>, ....<template.sql.6>
template.x.text	Title
template.x.format	Format   #.#  convert to number datecolor   convert to date, set to red, if date in the past date    convert to date time    convert to time bitmap  convert to bitmap (full path) sapbitmap   convert sap-picture (without path)
template.x.alignment	1=left
replacetemplatefields	Replace all space(50) as templatefieldX in the current datawindow with sql statements from current template definition   dw_2.replacetemplatefields() dw_2.retrieve

Address different data sources (only via ODBC) with the transaction system.

First, initialize the transaction system.

dw_1.transaktion.init

Example: Connection with external data source

<dw_2.type> returns the type of window

The available return values are:

browse

edit

Grid windows and multiline edit windows are "browse" windows, all other windows are edit windows.

Set this with:

dw_x.design=..

dw_x.is_type

define the link to udf name

Example for QC Sample:

dw_2.udf= qssudf

The system make the related udf1-4 fields visible and set all format properties automatically

Must be before form.opened event.

if name of target field is not "udf" then you must define this with udfcol

dw_2.udfcol=beas_qc_order_udf

True = 1/j/y/t ...

Example:

dw_2.visible=true

messagebox=<dw_2.visible>

Attention: Do not make dw_1 invisible.

Changes / reads the coordinate of data window

Special position

min: set the minimal position for x and y, example: dw_1.x=min

max: set the maximal value for width and height, example: dw_1.width=max