Qlik Community

QlikView App Development

Discussion Board for collaboration related to QlikView App Development.

anil_y_86
New Contributor II

Hi Community, My Question is --- Please suggest debugging steps to fix issues in dashboard

Hi Community,  My Question is --- Please suggest debugging steps to fix issues in dashboard.  I meant to ask how to attack a problem in QlikView

2 Replies
MVP
MVP

Re: Hi Community, My Question is --- Please suggest debugging steps to fix issues in dashboard

That's quite a general question.

What kind of issues?

Answering also in a general way: Break it down into pieces, simplify the problem domain.

(for example, test issues with a complex expression by creating expressions for each part of the complex one, e.g.each execution branch)

syukyo_zhu
Contributor III

Re: Hi Community, My Question is --- Please suggest debugging steps to fix issues in dashboard

Hi,

Where do you want to attack a bug? in Script ou IHM?

If in scrtipt you can check out below article, and hope helpful

Error Variables

The following variables can be used for error handling in the script:

  

ErrorMode
ScriptError
ScriptErrorDetails
ScriptErrorCount
ScriptErrorList

The values of all five variables will remain after script execution. The value of the last four variables, for error handling inside the script, is of course dependent on the use of ErrorMode=0.

ErrorMode

This variable determines what action is to be taken by QlikView when an error is encountered during script execution.

By default (ErrorMode=1) the script execution will halt and the user will be prompted for action (non-batch mode).

By setting ErrorMode =0 QlikView will suppress all error messages on failure to load. If script execution is halted due to failure, it will not continue.

By setting ErrorMode =2 QlikView will trigger an "Execution of script failed..." error message immediately on failure, without prompting the user for action beforehand.

Example:

set ErrorMode=0;

ScriptError

Returns the error code of the last executed script statement. This variable will be reset to 0 after each successfully executed script statement. If an error occurs it will be set to an internal QlikView error code. Error codes are dual values with a numeric and a text component. The following error codes exist:

   

0No error
1General error
2Syntax error
3General ODBC error
4General OLE DB error
5General custom database error
6General XML error
7General HTML error
8File not found
9Database not found
10Table not found
11Field not found
12File has wrong format
13BIFF error
14BIFF error encrypted
15BIFF error unsupported version
16Semantic error

Example:

set ErrorMode=0;

load * from abc.qvw;

if ScriptError=8 then

exit script;

//no file;

end if

ScriptErrorDetails

Returns a more detailed error description for some of the error codes above. Most importantly this variable will contain the error message returned by ODBC and OLE DB drivers for error codes 3 and 4.

ScriptErrorCount

Returns the total number of statements that have caused errors during the current script execution. This variable is always reset to 0 at the start of script execution.

ScriptErrorList

This variable will contain a concatenated list of all script errors that have occurred during the last script execution. Each error is separated by a line feed.