We have a problem with preserving conditional formatting when combining workbooks. For example, wb1.xlsm and wb2.xlsx:
wb2.xlsx has 3-Color Scale fromatting for A1 cell on "Tab2" worksheet;
wb1.Combine(wb2);
As a result, formatting for A1 on "Tab2" changed.
I tested the scenario against v7.3.2.0. It works fine in the new version. However, we use v6.0.1.7 in our production where the problem appears.We have a lot of complains from our customers. Please provide a workaround for v6.0.1.7 as we cannot migrate to the new version without comprehensive testing.
Well, we cannot provide any fix based on the older versions, it would be against our policy. We can only made/include fixes or enhancements based on the latest version. Since the new version e.g v7.3.2 works fine for your issue, so we recommend you to kindly use our latest version (we have now released our latest version i.e. v7.3.3 for the users in our Downloads section: http://www.aspose.com/community/files/51/.net-components/aspose.cells-for-.net/entry420470.aspx). Also do you find complaints from your clients about this issue with your older version (6.0.1.7) or you have complaints for v7.3.2? If you have issues with our latest versions, please provide us details and sample code/projects (you may start new threads too) to reproduce the issue on our end. We are bound to fix them asap in the latest version.
If you still persists with your older version(v6.0.1.7), I am afraid there is not any reliable workaround. By the way, you may try to copy individual worksheets from on workbook to other using Worksheet.Copy() method instead of combining workbooks in one go.
Yes, we will use a new version but putting it into production takes time while our customers have problems now. This is the reason we need a workaround. I think I understand why you said "there is no reliable workaround" as I tried to copy all conditional formattings manually property by property. But it did not work out as there was an exception when saving workbook output (to be specific, the exception appears when setting these two properties dest.ColorScale.MaxCfvo.Type = source.ColorScale.MaxCfvo.Type; dest.ColorScale.MaxCfvo.Value = source.ColorScale.MaxCfvo.Value;).
The Copy() method does not work for us as we would get #REF errors when there are cell references within several workbooks.
By the way, having tested the case on v7.3.2 with no problems found, please confirm that the issue has been fixed so that it actually tracked and will not appear again in the next versions - the issue number and the release it was fixed in.
Well, we enhanced the conditional formatting and other rendering Excel modules in the new versions (e.g v7.3.1, 7.3.2, 7.3.3(latest)). We also fixed some issues regarding conditional formatting and other rendering problems in the new versions. So, we recommend you to kindly use the new/latest versions which are stable.
Thank you.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
Enables storage, such as cookies, related to analytics.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.