I would like to propose an idea for improving the mechanism that marks objects in a TimeXtender project as dirty. In the current version (20.10.xx) and probably in the new release as well, a couple of situations exist in which this mechanism fails to mark objects as dirty. As a result, these objects are not recognized when deploying the project and using the ‘review tasks’ option causing the next reload to fail.
SUBMITTED
Improve dirty marking mechanism of DWH objects
One of the examples in which this mechanism fails is when the name of a table is adjusted, accordingly any aggregate table that uses this table as input is not marked dirty. The next reload will fail with a message referring to the old name of that input table for the aggregate table, mentioning that it does not exist anymore. Concluding, the aggregate table should be marked dirty when the input table name is changed.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
