The main interaction between Ignition and the database is by stored procedures and stored procedure transaction groups so as to minimize SQL code written outside of MSSQL. Thus far I have become unsuccessful developing a method to return a “Success” or “Fail” to the user based on interaction between Ignition and the database.
Furthermore, I have found that occasionally upon an unsuccessful insert, update, or query, the “trigger tag” is not reset to its inactive state. Beyond this, the “handshake failure” option is not written to the assigned tag. Under these circumstances, there is an unsuccessful interaction with the database, the user is not made aware of the failure, and he cannot use the stored procedure again until the “trigger tag” is reset.
I have been unable to use the “store quality code” option on the transaction group screen - the group errors at every execution. I assume this is because SQL tags do not have the property option where one can choose “quality.”
I am at a loss to find a sure-fire method to maintain quality assurance.
Is there a way to provide a success or failure signal to the user on execution of a stored procedure transaction group? Would it be more efficient to utilize the return codes built into sql?