...
| Info | ||
|---|---|---|
| ||
The refresh scheme is not used to mention on which tables to refresh the data, actually the tables present in refresh schemes represent a list of listeners for the changes that will occur in the mentioned tables, which means that if an update / add / delete is done on one of the tables specified in the refresh schemes then the refresh will be done on the DSO table, not the other way around. |
Starting with the SWAT 2019.23 release, also SkipRefresh parameters are available.
- AddSkipRefresh
- UpdateSkipRefresh
- RemoveSkipRefresh
These params are a comma separated list of table names which will be ignored/skipped upon refresh. Wildcards still work for the skipRefresh lists. If the developer want's to skip all, he/she can add * (star/asterisk).
| Code Block | ||
|---|---|---|
| ||
{
"Tables": "Table1*,Table2*",
"AddRepositionTo": "#NewRecord,#KeepSelection", //default reposition to newly created record
"UpdateRepositionTo":"#KeepSelection,#KeepSelection", // default keeps selection of the selected record
"RemoveRepositionTo": "#NextRow,#KeepSelection" // default reposition to next available record using #NextRow
"AddSkipRefresh": "*", // all tables are skipped for refresh on add action
"UpdateSkipRefresh": "Table2" // Table2 will not be refreshed on update action
} |