Home | Sign in | English EN
  • Use conditions
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Stored procedures
On a given row of a Looper control:
  • collapses a break (if it is expanded),
  • expands a break (if it is collapsed).
// Expands on user click
LooperCollapseExpand(<Looper control> [, <Row number> [, <Break name>]])
<Looper control>: Control name
Name of Looper control to use.
If this parameter is equal to an empty string (""), the current Looper control is used.
<Row number>: Optional integer
Number of the row to collapse or expand.
If this parameter is not specified, the current row is used.
<Break name>: Optional character string (with or without quotes)
Name of the break to modify. This parameter must be specified in case of nested breaks. It is used to define the break that will be handled. By default, no break is expanded or collapsed if the breaks are nested.

Use conditions

LooperCollapseExpand can be used on a browsing or memory Looper control.
WEBDEV - Browser code This function is not available for Linear Looper controls. This function is available for Looper controls in browser mode only.
WEBDEV - Server codePHP This function is available for Looper controls in Ajax mode, Looper controls in classic mode and Linear Looper controls.
Business / UI classification : UI Code
Component : wd260obj.dll
Minimum version required
  • Version 17
This page is also available for…
Working weird in Webdev 25
I followed the steps to create a Looper with breaks and collasable/expandable functionality (using both the Looper functions and the automatic funtionality by clicking in the background).

The CollapseAll and ExpandAll functions works great.
The other functions and the automatic management by clicking the background works WEIRD.

Sometimes the collapsable function or event does not collapse all the results, sometimes it does.
Sometimes the expand function collapse the other ones and other times does not affect the other set of results.

This is completely weird and impacts directly the UX. I hope you can solve this bug.
12 Jan. 2021