Skip to content

Bug/s1019 Inserting rows or Columns when named range is on MAX row or column resulted in nullref#2310

Open
OssianEPPlus wants to merge 2 commits intodevelop8from
bug/s1019
Open

Bug/s1019 Inserting rows or Columns when named range is on MAX row or column resulted in nullref#2310
OssianEPPlus wants to merge 2 commits intodevelop8from
bug/s1019

Conversation

@OssianEPPlus
Copy link
Contributor

When inserting rows or columns and having a namedRange on the maxRow or maxColumn Epplus crashed with a nullref exception.

This fix makes Epplus consistent with Excel for these cases. Specifically the behaviour is now:
Absolute References that are a singular cell on the maxRow/maxColumn become "#REF!" errors
Relative References are unaffected
Absolute ranges with a from row NOT on the max row/column but the toRow/toCol adress is now move the Absolute Reference of the fromRow by one as Excel does. for example:

We have a named range Sheet1!$XFB$3:$XFD$3
Insert column is performed on column XEU
the named range changes to Sheet1!$XFC$3:$XFD$3

Epplus is now consistent with Excel on this.

@OssianEPPlus OssianEPPlus requested a review from JanKallman March 13, 2026 15:53
@OssianEPPlus OssianEPPlus changed the title Bug/s1019 Bug/s1019 Inserting rows or Columns when named range is on MAX row or column resulted in nullref Mar 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant