Configuration of Publisher Timestamp format now only in Load Script?

[Peter_Cammaert]

Hi Tyler,

since a while I keep getting Trace messages in the GD (currently at v2.0.5) about "the chosen Publisher timestamp format not matching the actual Publisher (QDS) timestamp format". We're using variable vInputPublisherTimestampFormat in a User Configuration Script to assign a custom format.

The suggested solution is to make the configuration value equal to the format of the StartTimeStamp entry in the TaskExecutionHistory xml logs. Which it apprently is for a number of years now...

At long last I jumped into the QVGD load script to figure out what exactly I was doing wrong. I could discern a spot where this value is loaded (somewhere on the Config tab), but no location where this variable or its value are actually used. For example, on the TaskExecutionHistory tab, QVGD does a few timestamp guesses using the default format, TimeStampFormat1 and TimeStampFormat2 (both are hard-coded at the front of the script) but not using [vInputPublisherTimestampFormat]... Is this by design and should we forget about that configuration variable? Have I been looking in the wrong place?

I see only one solution: change the value of TimeStampFormat2 whose current value corresponds closely to the one we need. But I don't like patching tools that may require upgrades and will come with me forgetting to apply those necessary changes

Peter

[olivierrobin]

hello

before installing v12, i didn't use QVGD, and when i encoutered the problem, i modified Timestampformat1/2

[Tyler_Waterfall]

Unfortunately, we have not come up with a robust solution for this timestamp format issue with the Governance Dashboard. So you might be stuck with setting that timestamp variable in the script. I am sorry we don't have something better in place yet.