Problems with CustomDocumentProperties

[Administrator]

Hello!

I generate an excel file with some custom document properties. I attached the file as an example.

Now process the following steps:
1. Make a copy of the Export01.xls
2. Open the copy
3. Change the value of a cell
4. Save the file

--> The file loose its custom document properties

Thanks for your efforts
Marcus


ExcelExport0.zip

[Administrator]

Hi Marcus

I was able to reproduce the problem. I have created a bug report regarding this and I will let you know as soon as possible. you can refer to the following link. Sorry for the inconvenience. Let me know any if have any more quires.

http://www.syncfusion.com/support/issues/xlsio/Default.aspx?ToDo=view&questId=2970

With Regards,
Chella.


>Hello!

I generate an excel file with some custom document properties. I attached the file as an example.

Now process the following steps:
1. Make a copy of the Export01.xls
2. Open the copy
3. Change the value of a cell
4. Save the file

--> The file loose its custom document properties

Thanks for your efforts
Marcus


ExcelExport0.zip

[Chella Pandian B]

Hi Marcus

Our team is still investigating the problem can you provide us with the sample through which you are generating custom document properties. It will help us in solving the problem.

With Regards,
Chella.

[Administrator]

With m_obj_WorkBook.CustomDocumentProperties
.Item("FDFChangeDate").Value = m_dte_ChangeDate
.Item("ShowStatus").Value = m_bool_ShowStatus
.Item("ShowComment").Value = m_bool_ShowComment
.Item("ShowDataSource").Value = m_bool_ShowDataSource
.Item("ShowChangeUser").Value = m_bool_ShowChangeInfo
End With

[Chella Pandian B]

Hi Marcus

Thanks for you help. Our team is still investigating the problem can you tell me which version you are using It will help us more.

With regards,
Chella

[Administrator]

Our Excel Version: MS Excel 2000 (9.0.6926 SP-3)
Our XlsIO Version: 4.2.0.37

[Chella Pandian B]

Hi Marcus

After discussing with our team this is what the explanation they gave me.

They investigated it a little bit deeper. And here are some results:

Each document property has it's type (possible types are defined in some enum), and there are several types that allow to write integer value in the file: VT_INT and VT_I4 both of them writes int32 value into file, however when MS Excel meets VT_INT in custom properties it fails and shows no properties at all. XlsIO supports both of this types one by IDocumentProperty.Integer and another by IDocumentProperty.Int32. So we recommend to use IDocumentProperty.Int32. I've wrote simple code that opens one of those files, then

ICustomDocumentProperties properties = book.CustomDocumentProperties;
IDocumentProperty property = properties[ "LastHeaderRow" ];
property.Int32 = property.Integer;
property = properties[ "InternalFileID" ];
property.Int32 = property.Integer;

and then saves that file. After that MS Excel shows all properties correctly.
It is either incorrect usage of XlsIO (or some other application) or bug in MS Excel

Marcus we are really sorry for the inconvenience. We will try to rectify this as soon as possible.

Thanks for using XlsIO

With regards,
Chella.

[Mischa Spelt]

Hi Chella,

Thanks for investigating this issue.
I just ran into it as well, apparently the problem is still present in XlsIO 9.1.0.20 with Excel 2000.
Using .Int32 instead of .Integer is the correct workaround.

[John Bowlin Bosco K]

Hi Mischa,

Thank you very much for using Syncfusion Products.

We were able to see the issue at our end. We have logged an issue report for the reported issue and we suspect this issue could be a defect.

Could you please report this issue through Direct Trac Developer Support System? So that we can provide you with the patch for this issue as well as you can take the advantage of the expertise of a dedicated support engineer and a guaranteed response time and we hope you will take advantage of this system as well.

Direct Trac Link:
https://www.syncfusion.com/account/login?ReturnUrl=%2fsupport%2fdirecttrac%2fincidents

Please let us know if you need any further assistance.

Thanks,
Pauline Bosco.