The CreateTime- LastSavedTime for document is not in UTC format

Aspose.Words Product Family
1

Hi,

I work with doc, docx, rtf, xls and xlsx document formats.

I get all document attributes via BuiltInDocumentProperties.
The Aspose help indicates that we should get DateTime value in UTC but I have problem with RFT document. I got date value which is not in UTC. This date have DateTimeKind.Unspecified type.

Is it possible that I can receive such type values?

Tpolit.

2

Hi Taras,
Thanks for your inquiry. Could you please attach a document you are having a problem with? We will check the issue and provide you more information.
Best regards,

3

Hi Alexey,

Thanks for your quick response.
Please see attached file.

Taras

4

Hi Taras,
Thanks for your inquiry. If you need to get the date in UTC, you can easily achieve this by calling ToUniversalTime:

DateTime createdTime = doc.BuiltInDocumentProperties.CreatedTime.ToUniversalTime();

Hope this helps.
Best regards,

5

Thanks.
I used this workaround.
It is good solution when I really know this date time has Kind value - Local or Unspecified and date time in Local time value. It is according to this RTF file.

RTF file:
CreateTime attribute has
Kind = Unspecified
Date time Value = in local time zone
But there is one more issue.
I have attached new document(DOC type).
In this case I cannot use this workaround it is already UTC. See red text.

DOC file:

CreateTime attribute has
Kind = Unspecified
Date time Value = in UTC

Taras

6

Hi Taras,
Thank you for additional information. I managed to reproduce the problem on my side. Your request has been linked to the appropriate issue. We will notify you once the problem is resolved.
Best regards,

7

Hi Alexey,

Please let me know the progress of this issue.
When I will have the solution of this issue.

Thanks,
Taras

8

Hi Taras,
Thanks for your request. The issue is in the queue for analysis. Once our developers analyze the issue we will provide you more information. I apologize for inconvenience.
Best regards,

9

The issues you have found earlier (filed as WORDSNET-4873) have been fixed in this .NET update and this Java update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.