-
Notifications
You must be signed in to change notification settings - Fork 392
-
Star 2.4k
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
Property value evaluated as invalid formula requires repair #1292
Property value evaluated as invalid formula requires repair #1292
Comments
dfinke
commented
Oct 25, 2022
No, there is no way for designate as text vs formula. You can add a single quote at the start. [pscustomobject]@{Description = "'=====TEST====" } | export-excel .\test.xlsx -WorksheetName 'test' -ClearSheet -Show |
msftrncs
commented
Oct 25, 2022
•
edited
Loading
edited
Adding a single quote doesn't work correctly. Excel then displays this single quote, and reimporting the sheet also exposes this single quote. :(
|
stahler
commented
Oct 25, 2022
You would have a similar issue if you did this directly in Excel. After entering the cell and hitting F2 (you have probably seen this with Hyperlinks as well), Excel sees it as you want it to and re-consuming it shows it as text. |
msftrncs
commented
Oct 26, 2022
If you mean entering I would think that there should be a means to signal that a column/property is strictly text (at least if it is Alternately the automatic formula assumption could be disabled if the |
dfinke
commented
Oct 26, 2022
This is an edge case. Need to think about it more. |
stale
bot
commented
Dec 24, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This creates a damanged xlsx file.
Is there a method/parameter to indicate that a property is strictly text and not to even be interpreted as a formula?
-NoNumberConversion
handles only strictly the case when the value could be interpreted as a number.Reading the file back in with
Open-ExcelPackage
I can confirm the value was taken as a formula:The text was updated successfully, but these errors were encountered: