Lycia LowCode Methods

Common information:

• A method is a function associated with an object (or a class);
• When a method belongs to a class, it defines behavior that instances (objects) of that class can exhibit;
• If you access a method through an object, it acts as if it is "bound" to that specific instance, meaning it can access the object's data (properties or attributes) via the this keyword.

Calling a method from the InteractForm object:

• FUNCTION (this InteractForm) DoesTableRowExist(view STRING, vals REFERENCE) RETURNS BOOL

Calling a method from the View:

• FUNCTION (this View) DoesTableRowExist(vals REFERENCE) RETURNS BOOL

Method	Purpose
DoesTableRowExist()	Used for querying the database about whether a row with a given primary key(s) value(s) exists
GetCurrentDialog()	Returns the dialog object (ui.Dialog) of the InteractForm object
GetCurrentEvent()	Returns the raw event name that was currently running
GetEventSubInteraction()	Returns the name of the sub-interaction in which the event is currently running
GetEventView()	Returns the name of the view in which the event is currently running
GetViewArray()	Used to get the array data of the View
GetViewCurrentRecord()	Used to get the current record data of the View
Refresh()	Used to reset data in the View
SaveChanges()	Used to store changes in the database
SetEmbeddedData()	Allows a LowCode data source View to use data of a variable (array of records) handled / managed by your 4GL code instead of a database table
SetViewArray()	Used to set the array data of the View
SetViewCurrentRecord()	Used to modify the current record data of the View

 

Rules of Usage

DISPLAY ARRAY:

• The SetViewCurrentRecord() and SetViewArray() methods show modified / input data in the appropriate View;
• The Save action will not commit modified data. You have to call the SaveChanges() method to commit new data to the database;
• Scrolling doesn’t update the displayed data in the unbuffered mode. You have to call the SaveChanges() method to save data in the database, or call the Refresh() method of the View to reset data to the original (saved) data;
• If case of using the buffered mode, scrolling will reset the displayed data to the original (saved) data;
• If the SetViewCurrentRecord() and SetViewArray() methods were called when the DISPLAY ARRAY is in the Edit or Insert state (one row is currently in INPUT), then the new data will be displayed in this INPUT and can be stored / committed with the Save or Apply actions.

INPUT ARRAY:

• The SetViewCurrentRecord() and SetViewArray() methods show modified / input data in the appropriate View;
• The Save action will commit modified data;
• Scrolling doesn’t update the displayed data in the unbuffered mode. You have to call the SaveChanges() method to save data in the database, or call the Refresh() method of the View to reset data to the original (saved) data;
• If case of using the buffered mode, scrolling will reset the displayed data to the original (saved) data.

Additional Information

• Lycia does not update the displayed data on scrolling to not cause a heavy load on performance. Yet, in the buffered mode, Lycia executes the ON BUFFER action, and the buffer data is reset and loaded from the database again;
• To simulate resetting the original data on scrolling, you can bind the AFTER ROW action and call the Refresh() method of the appropriate View in it.