If a user has the Write Back to Database
privilege, then the write-back fields in their analyses can display as editable
fields if properly configured. If the user does not have this privilege, then
the write-back fields display as normal fields.
If the user types a value in an editable
field and clicks the appropriate write-back button, then the application reads
the write-back template to get the appropriate insert or update SQL command. It
then issues the insert or update command. If the command succeeds, then it
reads the record and updates the analysis. If there is an error in either
reading the template or in executing the SQL command, then an error message is
displayed.
The insert command runs when a record does
not yet exist and the user enters new data into the table. In this case, a user
has typed in a table record whose value was originally null.
The update command runs when a user
modifies existing data. To display a record that does not yet exist in the
physical table to which a user is writing back, you can create another similar
table. Use this similar table to display placeholder records that a user can
modify in dashboards.
No comments:
Post a Comment