After HFix-30178, Use last update as start option not respected
Business Intelligence Exchange (BIX) extract, with the output format as a database schema, does not work initially when the source and destination tables are in different databases.
After installing HFix-30178 and HFix-45698 with its dependent hotfixes, the data is pushed to the destination database. Despite selecting the 'Use last updated time as start' checkbox in the 'Filter Criteria' tab in the Extract rule, the extract does not run on the recently updated work objects. The extract runs on all the work objects and pushes them to the destination database (each run extracting all work object).
The second run continues to ignore the filter criteria and pushes all resolved work objects, thus creating duplicate data.
[PegaRULES-Batch-19] [ ] [your_WS:01.01.03] (internal.access.ExtractImpl) ERROR ad70304 - SQL Exception could not get last update time.
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'PEGA_DATA.PR_EXTRACT_TIME'.
Steps to Reproduce
- Install HFix-30178, and HFix-45698 with its dependent hotfixes.
- Set the 'Use last updated time as start' option.
- Run the extract.
- Rerun the extract.
A defect in Pegasystems’ code or rules.
Pega searched for the PR_EXTRACT_TIME table in the external database when the source and the destination were in the external database.
0% found this useful