I would like to know if there is some way to trigger the data-update for APPS that is usually triggered by “Datatable Save” or “Advanced Input Table-API” for a “database-view data table” (perhaps using some API-call?)
- External postgresql database (DB) with “Table_a”
- OD data table “DB__table_a” created from a “Connection” to the DB for the “Table_a”
- APP which displays DB__table_a and uses “saveToMicroservice” to trigger a workflow which will then modify “Table_a” in the DB directly.
- SaveToMicroservice-workflow will call some API / do some trick to trigger the data update in APPS for the view-datatable (instead of saving a copy as “real” datatable, see below)
Currently, we do not use a data-table view but save the changed table in the workflow again as “real” data-table to get the “pushed” update in APPS. But this approach has multiple problems (ineffective, type-casting-hell, python-processor-has-only-single-output-issue) and it would help us a lot if we could cut out this duplication of resources.