Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello, Qlik Compose community. I just discovered (after months of interacting with type 2 dimensions in our data warehouse) that the FromDate and ToDate timestamps are in UTC, not server time.
Stumbled upon a record with a FromDate that looked like it had a timestamp a few hours in the future, thus uncovering the issue. Didn't see anything in the documentation clarifying this, so figured y'all would want to know.
Hello @JacobTews
Check whether the "Current Time Convention" in Project Setting set to UTC or Server time?
In User guide it mentioned that
For existing objects, Compose will not be able to determine a source record's timestamp if both of the following are true:
Check this if it's related to your issue.
Regards,
Suresh
Thanks, @sureshkumar, that's helpful information! I do see that the project setting is to insert UTC time, because all the FromDate columns are unmapped (there are no timestamps in the original source DB2 tables). However, I'm a little confused about where that timestamp actually originates: wouldn't the inserted or updated record receive a header__timestamp in the [table]__ct table when Replicate writes it? Or does Compose own the __ct tables? Somehow I've lost my clear picture of the process flow.
Hello @JacobTews
Please check the Landing zone (Qlik Replicate Target), CT table has some built-in columns, one of this is header_timestamp.
You can check in the Qlik Replicate UI as well, go to Task settings--> Change Processing --> Store changes-->Change Table Header Columns.
Regards,
Suresh