[Bug 171679] XLSX: Exporting as XLSX format, UDF in My Macro convert to Value
https://bugs.documentfoundation.org/show_bug.cgi?id=171679 --- Comment #14 from Karthik --- XLSX doesn't support macros, XLSM or XLSB should be used to export macros. It's still unclear to me whether the author is talking about UDF (User defined functions) or macros. LO can't natively create UDFs but UDFs created by EXCEL are preserved. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171679] XLSX: Exporting as XLSX format, UDF in My Macro convert to Value
https://bugs.documentfoundation.org/show_bug.cgi?id=171679 ady changed: What|Removed |Added CC||[email protected] --- Comment #13 from ady --- (In reply to bnhep from comment #12) > XLS -> XLSX: Skip writing macros in formulas So, is the change reported in this tdf 171679 intentional? Is this some negative unwanted outcome triggered by some other issue? Is the original author aware of this report? Is there something that can be done so as to improve the result? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171679] XLSX: Exporting as XLSX format, UDF in My Macro convert to Value
https://bugs.documentfoundation.org/show_bug.cgi?id=171679 Buovjaga changed: What|Removed |Added Keywords||bisected -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171679] XLSX: Exporting as XLSX format, UDF in My Macro convert to Value
https://bugs.documentfoundation.org/show_bug.cgi?id=171679 Roman Kuznetsov <[email protected]> changed: What|Removed |Added Regression By||Karthik Godha -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171679] XLSX: Exporting as XLSX format, UDF in My Macro convert to Value
https://bugs.documentfoundation.org/show_bug.cgi?id=171679 bnhep changed: What|Removed |Added Keywords|bibisectRequest |bibisected --- Comment #12 from bnhep --- Bibisected using raal's test file, repository Windows bibisect-win64-26.8. 605a3d7f52236fbd5663cc78ae52b4927fa40a32 is the first bad commit commit 605a3d7f52236fbd5663cc78ae52b4927fa40a32 Author: Jenkins Build User Date: Sat Feb 21 14:48:08 2026 +0100 source sha:f133be32071a6354c8ce9ac752198875fe97de28 XLS -> XLSX: Skip writing macros in formulas Additional Notes: Results found using the original reporter's reproduction steps in comment 6 source sha:12c5d81816339d5bc735fba1b973c5ba1fcf3345 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171679] XLSX: Exporting as XLSX format, UDF in My Macro convert to Value
https://bugs.documentfoundation.org/show_bug.cgi?id=171679 --- Comment #11 from ady --- Assuming that raal's attachment 206616 reflects exactly the OP's intention (at least in principle)... ATM this report is marked as a "regression" and a "bibisectRequest". FWIW, the only thing that could potentially be bisected is the change, from saving (to the xlsx file) the original UDF formula *in the cell* (that used to be available, for example in LO 7.3), to the current situation (LO Dev 26.8alpha as of 2026-04-10), in which the UDF formula *in the cell* is not saved; only the cell's result as of the time it was saved. Just to be clear, when saving as xlsx, older versions of LO could not export the actual LO BASIC code to the xlsx file, the same as current versions of LO. Exporting attachment 206616 to xlsx with older versions of LO, there is/was never a macro or UDF code actually available in the resulting xlsx file. So, in older versions of LO Calc, the content of the cell was '=TEST()' (without quotation marks) and the cell's result was displayed as the '#NAME?' error, just as an unknown function. In newer versions, the resulting value (at the time the xlsx was exported / initially saved in Calc) is seen as the content of the cell, instead of the UDF 'TEST()'. In both cases, the actual UDF is not saved / exported to the xlsx file from Calc. I understand that, in some cases, retaining the UDF's name could be potentially more beneficial than retaining the resulting value. The actual LO BASIC (UDF) code is not retained when saving / exporting as xlsx. Having said that, I have the impression (and I could be completely wrong) that the initial situation is not really about exporting a LO BASIC code to xlsx, but rather to use LO Calc while being able to keep using UDFs originally created with some other spreadsheet tool (i.e. _import_ UDFs, from xlsx files), and keep saving to xlsx file format. This is just an assumption / guess, and might not be relevant to this report, but perhaps it is relevant to the OP's goals. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171679] XLSX: Exporting as XLSX format, UDF in My Macro convert to Value
https://bugs.documentfoundation.org/show_bug.cgi?id=171679 --- Comment #10 from raal --- Tested with master and 7.3.7. Really =test() is missing in master, but even in old version the macro is deleted in xlsx. For example I cannot add =test() to new cell. I don't think it's a bug, LO's macro Basic doesn't works in excel. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171679] XLSX: Exporting as XLSX format, UDF in My Macro convert to Value
https://bugs.documentfoundation.org/show_bug.cgi?id=171679 raal changed: What|Removed |Added CC||[email protected] --- Comment #9 from raal --- Created attachment 206616 --> https://bugs.documentfoundation.org/attachment.cgi?id=206616&action=edit ODS file for testing -- You are receiving this mail because: You are the assignee for the bug.
[Bug 171679] XLSX: Exporting as XLSX format, UDF in My Macro convert to Value
https://bugs.documentfoundation.org/show_bug.cgi?id=171679 nobu changed: What|Removed |Added Status|UNCONFIRMED |NEW OS|Windows (All) |All Summary|XLSX: all UDF formulas |XLSX: Exporting as XLSX |became values |format, UDF in My Macro ||convert to Value Ever confirmed|0 |1 Keywords||bibisectRequest, regression -- You are receiving this mail because: You are the assignee for the bug.
