VALUETOTEXT

Microsoft publishes =VALUETOTEXT(A2, 0) = TRUE for A2 = TRUE. Format 0 is documented as "Concise format that is easy to read. The text returned will be the same as the text rendered in a cell that has general formatting applied." Microsoft's page was read live on 2026-08-31 at https://support.microsoft.com/en-us/excel/functions/valuetotext-function. FETCH NOTE FOR THIS BATCH: batch F recorded every /en-us/office/<name>-function-<guid> URL returning Microsoft's 'Sorry, the page you're looking for can't be found' body; today BOTH paths serve the article again -- the GUID form redirects to /en-us/excel/functions/<slug>-function -- and every page cited in this batch came back complete (217-223 KB) in one or two attempts, with no 87 KB stub responses. Nothing here is sourced from a search snippet or a mirror.

Microsoft publishes =VALUETOTEXT(A3, 0) = 1234.01234. The published Strict row for the same cell is ALSO 1234.01234, because the page documents strict format as encapsulating "returned strings in quotes except for Booleans, Numbers and Errors" -- numbers are one of the three exceptions.

Microsoft publishes =VALUETOTEXT(A4, 0) = Hello, with no quotation marks. This is the concise half of the pair that defines the format argument.

Microsoft publishes =VALUETOTEXT(A4, 1) = "Hello" WITH the quotation marks, against the unquoted Hello from format 0 on the identical cell. THIS PAIR IS THE ONLY THING IN THE PUBLISHED TABLE THAT DISTINGUISHES THE TWO FORMATS: rows A2, A3, A5 and A7 (a Boolean, two numbers and an error) print identically under both formats, so an engine that ignored the format argument entirely would pass four of the six documented rows. The expected value here contains literal double-quote characters as part of the string.

Microsoft publishes =VALUETOTEXT(A6, 1) = "Seattle". Asserted alongside the Hello pair so the quoting behaviour rests on two independent strings rather than one.

The Remarks publish: "If format is anything other than 0 or 1, VALUETOTEXT returns the #VALUE! error value."

DELIBERATELY ASSERTS NOTHING, FOR A READ-BACK REASON RATHER THAN A DOCUMENTATION ONE. Microsoft publishes =VALUETOTEXT(A5, 0) = #VALUE! for a cell A5 holding the ERROR VALUE #VALUE!, i.e. the function is documented to return the error's TEXT, "#VALUE!", as a string. Two problems make that unassertable here. First, setup_cells can only place a literal, so A5 in this workbook holds the six-character STRING "#VALUE!" rather than a genuine error value, and a string round-trips through the concise format unchanged -- the right answer for the wrong reason. Second, and decisively, harness/corpus.py classifies a read-back value of "#VALUE!" as an ERROR (it is in KNOWN_ERROR_STRINGS), so a correct engine returning the text "#VALUE!" and a broken engine actually erroring are INDISTINGUISHABLE in the results file. Rather than assert a value the harness cannot verify, the case records what each engine returns and says why it is not scored.

Microsoft publishes =VALUETOTEXT(A2, 0) = TRUE for A2 = TRUE. Format 0 is documented as "Concise format that is easy to read. The text returned will be the same as the text rendered in a cell that has general formatting applied." Microsoft's page was read live on 2026-08-31 at https://support.microsoft.com/en-us/excel/functions/valuetotext-function. FETCH NOTE FOR THIS BATCH: batch F recorded every /en-us/office/<name>-function-<guid> URL returning Microsoft's 'Sorry, the page you're looking for can't be found' body; today BOTH paths serve the article again -- the GUID form redirects to /en-us/excel/functions/<slug>-function -- and every page cited in this batch came back complete (217-223 KB) in one or two attempts, with no 87 KB stub responses. Nothing here is sourced from a search snippet or a mirror.

Microsoft publishes =VALUETOTEXT(A3, 0) = 1234.01234. The published Strict row for the same cell is ALSO 1234.01234, because the page documents strict format as encapsulating "returned strings in quotes except for Booleans, Numbers and Errors" -- numbers are one of the three exceptions.

Microsoft publishes =VALUETOTEXT(A4, 0) = Hello, with no quotation marks. This is the concise half of the pair that defines the format argument.

Microsoft publishes =VALUETOTEXT(A4, 1) = "Hello" WITH the quotation marks, against the unquoted Hello from format 0 on the identical cell. THIS PAIR IS THE ONLY THING IN THE PUBLISHED TABLE THAT DISTINGUISHES THE TWO FORMATS: rows A2, A3, A5 and A7 (a Boolean, two numbers and an error) print identically under both formats, so an engine that ignored the format argument entirely would pass four of the six documented rows. The expected value here contains literal double-quote characters as part of the string.

Microsoft publishes =VALUETOTEXT(A6, 1) = "Seattle". Asserted alongside the Hello pair so the quoting behaviour rests on two independent strings rather than one.

The Remarks publish: "If format is anything other than 0 or 1, VALUETOTEXT returns the #VALUE! error value."

DELIBERATELY ASSERTS NOTHING, FOR A READ-BACK REASON RATHER THAN A DOCUMENTATION ONE. Microsoft publishes =VALUETOTEXT(A5, 0) = #VALUE! for a cell A5 holding the ERROR VALUE #VALUE!, i.e. the function is documented to return the error's TEXT, "#VALUE!", as a string. Two problems make that unassertable here. First, setup_cells can only place a literal, so A5 in this workbook holds the six-character STRING "#VALUE!" rather than a genuine error value, and a string round-trips through the concise format unchanged -- the right answer for the wrong reason. Second, and decisively, harness/corpus.py classifies a read-back value of "#VALUE!" as an ERROR (it is in KNOWN_ERROR_STRINGS), so a correct engine returning the text "#VALUE!" and a broken engine actually erroring are INDISTINGUISHABLE in the results file. Rather than assert a value the harness cannot verify, the case records what each engine returns and says why it is not scored.

Microsoft publishes =VALUETOTEXT(A2, 0) = TRUE for A2 = TRUE. Format 0 is documented as "Concise format that is easy to read. The text returned will be the same as the text rendered in a cell that has general formatting applied." Microsoft's page was read live on 2026-08-31 at https://support.microsoft.com/en-us/excel/functions/valuetotext-function. FETCH NOTE FOR THIS BATCH: batch F recorded every /en-us/office/<name>-function-<guid> URL returning Microsoft's 'Sorry, the page you're looking for can't be found' body; today BOTH paths serve the article again -- the GUID form redirects to /en-us/excel/functions/<slug>-function -- and every page cited in this batch came back complete (217-223 KB) in one or two attempts, with no 87 KB stub responses. Nothing here is sourced from a search snippet or a mirror.

Microsoft publishes =VALUETOTEXT(A3, 0) = 1234.01234. The published Strict row for the same cell is ALSO 1234.01234, because the page documents strict format as encapsulating "returned strings in quotes except for Booleans, Numbers and Errors" -- numbers are one of the three exceptions.

Microsoft publishes =VALUETOTEXT(A4, 0) = Hello, with no quotation marks. This is the concise half of the pair that defines the format argument.

Microsoft publishes =VALUETOTEXT(A4, 1) = "Hello" WITH the quotation marks, against the unquoted Hello from format 0 on the identical cell. THIS PAIR IS THE ONLY THING IN THE PUBLISHED TABLE THAT DISTINGUISHES THE TWO FORMATS: rows A2, A3, A5 and A7 (a Boolean, two numbers and an error) print identically under both formats, so an engine that ignored the format argument entirely would pass four of the six documented rows. The expected value here contains literal double-quote characters as part of the string.

Microsoft publishes =VALUETOTEXT(A6, 1) = "Seattle". Asserted alongside the Hello pair so the quoting behaviour rests on two independent strings rather than one.

The Remarks publish: "If format is anything other than 0 or 1, VALUETOTEXT returns the #VALUE! error value."

DELIBERATELY ASSERTS NOTHING, FOR A READ-BACK REASON RATHER THAN A DOCUMENTATION ONE. Microsoft publishes =VALUETOTEXT(A5, 0) = #VALUE! for a cell A5 holding the ERROR VALUE #VALUE!, i.e. the function is documented to return the error's TEXT, "#VALUE!", as a string. Two problems make that unassertable here. First, setup_cells can only place a literal, so A5 in this workbook holds the six-character STRING "#VALUE!" rather than a genuine error value, and a string round-trips through the concise format unchanged -- the right answer for the wrong reason. Second, and decisively, harness/corpus.py classifies a read-back value of "#VALUE!" as an ERROR (it is in KNOWN_ERROR_STRINGS), so a correct engine returning the text "#VALUE!" and a broken engine actually erroring are INDISTINGUISHABLE in the results file. Rather than assert a value the harness cannot verify, the case records what each engine returns and says why it is not scored.