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
NOTE: This same code throws ClosedXML.Excel.CalcEngine.Exceptions.NameNotRecognizedException: 'The identifier variableA was not recognised.' on build from 'develop' branch. I think this was changed (is that now as designed?) in this commit: f2063a7
Do you want to request a feature or report a bug?
Bug
Feature
Question
Did you test against the latest CI build?
Yes
No
I used the latest officially released Nuget package v = 0.95.3
In the current released 0.95.3 version we have an issue that if formula has usage of named variable and we access .Value before this named variable is added to the worksheet and we try to access formulaCell.Value after we added named variable to worksheet we get .Value incorrectly as old value. Example
@igitur, this turned out to be trickier than I expected. First, we have to consider named ranges too when analyzing precedent cells. But this is not enough - our ExpressionCache caches evaluated expression and refuses to notice that the named range point to a different location than it used to. Do you think we can turn the expression caching off? Parsing has never been a performance bottleneck, as I recall.
@Pankraty , @igitur I will close this issue as with latest version on develop you can't use this case as when using variable that is not yet added code now throws NameNotRecognizedException and I think this should be expected behavior.
NOTE: This same code throws
ClosedXML.Excel.CalcEngine.Exceptions.NameNotRecognizedException: 'The identifier
variableAwas not recognised.'
on build from 'develop' branch. I think this was changed (is that now as designed?) in this commit:f2063a7
Do you want to request a feature or report a bug?
Did you test against the latest CI build?
I used the latest officially released Nuget package v =
0.95.3
If you answered
No
, please test with the latest development build first.Version of ClosedXML
Nuget package v =
0.95.3
What is the current behavior?
In the current released
0.95.3
version we have an issue that if formula has usage of named variable and we access.Value
before this named variable is added to the worksheet and we try to accessformulaCell.Value
after we added named variable toworksheet
we get.Value
incorrectly as old value. ExampleNote that this works fine if I comment out first
formulaCell.Value
access:What is the expected behavior or new feature?
formulaCell.Value
is correctly invalidated and results to25
at the last line.Is this a regression from the previous version?
No
Reproducibility
Code to reproduce problem:
cc: @igitur
The text was updated successfully, but these errors were encountered: