HomeAppeon Web | Appeon Mobile | Appeon PowerBuilderAppeon Online Help Center

Functions of DataStore object

Supported

There are some limitations or differences for calling functions marked with the "*" symbol. Refer to the Limitations and Differences for Calling Functions.

Table 270. 

AcceptText

ClassName

ClearValues

Create

DeletedCount

DeleteRow

Describe

FindGroupChange

Filter

FilteredCount

Find

FindRequired

GenerateHTMLForm

GetChanges

GetChild

GetColumn

GetColumnName

GetFormat

GetFullState

GetItemDate

GetItemDateTime

GetItemDecimal

GetItemNumber

GetItemStatus

GetItemString

GetItemTime

GetNextModified

GetParent

GetRow

GetRowFromRowId

GetRowIdFromRow

GetSelectedRow

GetSQLSelect*

GetText

GetValidate

GetValue*

GroupCalc

ImportClipboard*

ImportFile*

ImportString*

InsertRow

IsSelected

ModifiedCount

Modify*

PostEvent

Print

Reset

ResetUpdate

Retrieve

RowCount

RowsCopy

RowsDiscard

RowsMove*

SaveAs*

SaveAsAscii

SetDetailHeight

SelectRow

SetChanges

SetColumn

SetFilter

SetFormat

SetFullState

SetItem

SetItemStatus

SetPosition

SetRow

SetSort*

SetSQLPreview

SetSQLSelect*

SetText

SetTransObject

SetValidate

SetValue*

SetWSObject*

ShareData

ShareDataOff

Sort

TriggerEvent*

TypeOf

Update

  

Unsupported

Table 271. 

CategoryCount

CategoryName

Clipboard

CopyRTF

CreateFrom

DataCount

DBCancel

ExportJson

FindCategory

FindSeries

GenerateResultSet

GetBorderStyle

GetContextService

GetClickedColumn

GetClickedRow

GetData

GetDataPieExplode

GetDataStyle

GetDateValue

GetSeriesStyle

GetStateStatus

GetTrans

ImportJson

ImportJsonByKey

InsertDocument

PasteRTF

PrintCancel

ReselectRow

ResetDataColors

ResetTransObject

SaveAsFormattedText

SaveNativePDFToBlob

SeriesCount

SeriesName

SetBorderStyle

SetDataPieExplode

SetDataStyle

SetHTMLAction

SetSeriesStyle

SetTrans

Limitations and Differences for Calling Functions

  • GetValue

    The column argument works only if the edit style of the column is CheckBox, DropDownListBox, Edit, or RadioButton.

  • GetSQLSelect

    If the syntax in DataWindow is PBSELECT statement, when calling the GetSQLSelect function, it will still return the PBSELECT statement but not the SQL SELECT statement, which is different from that in PowerBuilder.

  • ImportFile, ImportString, ImportClipboard

    1. The filename argument of ImportFile function must be a tab-separated file (TXT) or a comma-separated file (CSV).

    2. The string argument of ImportString function must be a tab-separated string (text).

    3. The importtype arguments (e.g. Text!, CSV! and XML!) of ImportString function are unsupported.

      The importtype arguments (e.g. Text!, CSV!, XML!, DBase2!, DBase3!) of ImportFile function are unsupported.

    4. When using the three functions, you should ensure that the data type imported matches the data type that you specified in a DataWindow control, DataStore object or graph control. Otherwise the output on the Web may be different from that in PowerBuilder. For example, if the date type specified in a DataWindow is string, when you import a file with date number (eg, 2006-08-01), on the Web the date data will be recognized as a string (2006), however in PowerBuilder, it will be recognized as a date data (2006-08-01).

  • Modify

    If the Modify function is used to modify the WHERE clause of the DataWindow object's SQL SELECT statement, please make sure that the new SQL SELECT statement is correct in syntax. Otherwise, syntax errors can occur on the Web because PowerBuilder does not validate the statement whereas JavaScript does.

    When executing Modify function to change the dddw.property on the Web, properties must be separated with spaces when they are concatenated into one value. For example,

    Unsupported code:

    dw_1.Modify = "emp_id.BackGround.Color=" + String(RGB(192,192,192)) + "emp_id.Protect=1"

    Supported code:

    dw_1.Modify = "emp_id.BackGround.Color=" + String(RGB(192,192,192)) + " emp_id.Protect=1"

    In PowerServer Web, the Modify function cannot be used to modify the database information.

  • RowsMove

    Events cannot be triggered while the application moves data within the primary buffer of one DataWindow.

  • SaveAs

    1. The saveastype argument can be TEXT, HTMLTable, XML, PDF*, EXCEL, or EXCEL5. For the EXCEL format, only up to 256 characters are supported and anything larger will be automatically truncated.

    2. The supported SaveAs syntax:

      ll_testvalue = ds_test.SaveAs(filename, saveastype, colheading, encoding)

      SaveAs PDF cannot support the colheading argument, for example, the following syntax is unsupported: 

      integer ds_test.SaveAs ({string filename, saveastype saveastype, boolean colheading {, encoding encoding}})

      The unsupported SaveAs syntax:

      ds_test.SaveAs ([filename, ]graphcontrol[, saveastype, colheading])

    3. On the Web, Nillable attribute is unsupported in an XML schema.

    4. If the DataStore without any data is saved as an HTML file or XML file, on Web the header will not be saved, whereas it will be saved on PB.

    5. The generated file is automatically saved to the "plugin" folder under the current application directory. See "plugin" folder in Workarounds & APIs Guide for more.

  • SaveAsAscii

    Retainnewlinechar argument is unsupported.

  • SetValue

    The column argument works only if the edit style of the column is DropdownListBox.

  • SetSort

    Using "desc" or "asc" as the Order will not have any effect. Please use the standard Order value A for ascending or D for descending order.

  • TriggerEvent

    The following TriggerEvent syntax is unsupported:

    object1.TriggerEvent (object2, event)
Prev  Up  Next
Events of DataStore object  Home  DataWindowChild object