-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Erroneous parsing of defined names #18
Comments
@rjplevin Thank you for finding this bug! I'll take a look at it shortly. |
@rjplevin If you use this formula in a Cell: |
Oddly, no. I can email you the workbook; I'd rather not attach it here for all of eternity. :~) Email me at plevin@berkeley.edu... |
Sure! Just sent you an email. |
Cool! After looking in the internet for examples like these, I see 3 Workbook features not covered by XLSX.jl. I'll work on them ASAP:
The fact that it is a hidden name it just means that it doesn't show in the Insert -> Name -> Define Name menu. To change them you have to use VBA. But it works just like any other defined named, and you can reference them from formulas. I guess it was created by an Add-in that is an optimizer in your case. Just give me some time and I'll fix this in the package. Thanks! |
Support for local worksheet names and constants (#18)
@rjplevin, you're all set. You can read this file using the latest master version. Just use Thanks for finding this bug! |
I have a workbook that has traveled through many hands, so I don't know the origins of these "hidden" defined names, but they're breaking XLSX.jl. I replaced the
error()
at the end ofparse_workbook!
withprintln("Could not parse named range '$(ref_or_range_str)' in $defined_name_node.")
, yielding this:I don't know the meaning of "hidden" defined names, but the parser seems to be interpreting the value incorrectly as the name of the range.
The text was updated successfully, but these errors were encountered: