@Zephyrus In @Qiu 's workflow, he's replaced the newline character (\n) with a line break (<br />). The table tool uses html, and html doesn't display/repsect \n; instead, you need to use a <br />. For what it's worth, here's the table tool's html when you just use a newline character:
I saw this "Table (Bad Field Type)" error while replicating @Qiu's workflow. See Exhibit C.
When I opened @Qiu's workflow, the Render tool gave the same error. See Exhibit D.
I understand that the workflow could run regardless and the final render appears just the same as desired output, but am wondering what is causing this error to show? Is it some HTML-related parsing malfuntion associated with the Render tool?
@Zephyrus Great question! Alteryx knows we're changing the html behind the scenes, and so the render tool throw errors (even though you see that it still works). You can "trick" alteryx with the attached macro that I created for this particular use case right before the render tool. It uses a report text tool to fool alteryx into thinking that your html is coming from a reporting tool.