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
Author: Pietro Garmatter (IP address: 2001:1284:f01c:18d0:8da:187d:8b95:3119, 2001:1284:f01c:18d0:8da:187d:8b95:3119)
Email: pietrogarmatter@hotmail.com
URL:
Comment:
I am using OpenSolver with google sheets.
I works very well. However, if the cell name contains spaces, the solver tab doesn't update cell references correctly.
example: my first sheet was called 'ex1 - p1', second 'ex1 - p2' and so on. When trying to update variables, objetive etc for the second sheet, nothing happened. I went back to the first and ran its solver again. It worked OK, because references weren't lost.
Tried updating values from the first sheet (now renamed with the spaces) and it didn't work.
I did, however, manage to use it by renaming sheets from 'ex1 - p1' to 'e1p1'.
This issue is not with spaces in sheet names, specifically the issue comes from where the sheet name contains a segment of the form "x-{}" where:
x is a number, and {} is a string containing a letter, number, underscore or question mark. (Note may apply for other non-alphanumeric characters but the ones listed are the only ones I found through my testing).
Edit: If the tailing string (the section denoted by {}) contains only letters, the solver will still work provided there are no letters before the number denoted by x. Also updating the fact that the space between the x and - is not actually required for the bug to occur.
Activity
LabJared commentedon Nov 20, 2022
This issue is not with spaces in sheet names, specifically the issue comes from where the sheet name contains a segment of the form "x-{}" where:
x is a number, and {} is a string containing a letter, number, underscore or question mark. (Note may apply for other non-alphanumeric characters but the ones listed are the only ones I found through my testing).
Edit: If the tailing string (the section denoted by {}) contains only letters, the solver will still work provided there are no letters before the number denoted by x. Also updating the fact that the space between the x and - is not actually required for the bug to occur.