You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When saving, wb$dataValidationsLst is moved to ext. Upon loading it is not moved to dataValidationsLst but remains in extLst. Hence we need to check if creating another entry in dataValidationsLst and saving again properly merges or creates broken xlsx output. Preferably the list is not silently moved from one entry to another, but remains at a single spot. E.g. load it, move the node around and remove the node in the extLst.
This will be broken. Has one extLst, but two "<ext xmlns:x14 ...>" entries.
Certain data validation is an x14 extension. Previously, it was added to dataValdiationLst and moved to extLst when saving. When loading, it remained in extLst. This caused problems when a second dataValidationsLst entry was added. Now, dataValidationsLst is skipped completely. Instead, we write directly to extLst using the approach used with sparklines.
Certain data validation is an x14 extension. Previously, it was added to dataValdiationLst and moved to extLst when saving. When loading, it remained in extLst. This caused problems when a second dataValidationsLst entry was added. Now, dataValidationsLst is skipped completely. Instead, we write directly to extLst using the approach used with sparklines.
When saving,
wb$dataValidationsLst
is moved toext
. Upon loading it is not moved todataValidationsLst
but remains inextLst
. Hence we need to check if creating another entry indataValidationsLst
and saving again properly merges or creates broken xlsx output. Preferably the list is not silently moved from one entry to another, but remains at a single spot. E.g. load it, move the node around and remove the node in theextLst
.This will be broken. Has one extLst, but two "<ext xmlns:x14 ...>" entries.
The text was updated successfully, but these errors were encountered: