Rajesh - This is a known issue that has already been fixed in version 2.8. It is caused by opening files around the world using machines whose locales/clocks are set to different time zones.

While using version 2.7, you will need to either author IOK files in the timezone of the intended recipient, or employ formulas that will force a recalc TEXTTODATE on open to convert the shipping text-typed dates into a real date/time fields suitable for use in date arithmetic if required.

Thanks for your updates Thomas. Can you also give me some example formula on how to hard code the date/time fields?

Regards
Rajesh B

Rajesh - The most commonly used function to read text values and interpret/convert the text into the correponding continuous Date/Time value is:

TEXTTODATE(text_value, custom_format, lenient, time zone value)
In scripts:
textToDate(text_value, custom_format, lenient, time zone value)

If custom_format is specified, this is a custom date format pattern such as "dd/MM/yyyy HH:mm:ss". If not specified, the default format for the current data locale will be used.

If lenient parameter is omitted or is set to 'true', this controls whether non-existent dates/times are permitted, such as 29 February on a non-leap-year (corrected to 1 March). Times after midnight and before 1:00 am which should be skipped on the day the time zone changes to daylight savings time are also illegal in Java, but should be permitted if lenient is set to 'true'.

If time zone value is specified (as it always should be), this controls how Omniscope interprets time values. If not specified, the text being converted will be assumed to be a Date/Time from the same time zone as the system.

The DATETOTEXT and TEXTTODATE functions allow you to specify time zones. Valid formats are as follows:

"GMT-08:00" or "GMT-8".

Rajesh, please also see here: http://forums.visokio.com/discussion/1617/cross-regional-publishing-fix

Hi all,
Users from different locations are still facing the month shifting issue when I refresh the data from APAC. Can anyone please let me know what would be the fix for this issue?
Regards
Rajesh

Rajesh - all these users should update to version 2.8...

Thanks for your response...