HTML allowed in v2 Table template fields ?

  • 4
  • Question
  • Updated 17 hours ago
  • In Progress
Currently rebuilding in v2 (as there currently isn't a streamlined process to convert).

When creating a template field within an Ink Table component, I noticed that the 'Allow HTML' option is no longer there. (present in v1).

This causes the HTML inputted in the template to appear as text:


Is there a way to enable HTML for an Ink Table template field in v2? There is no HTML option in the Ink Table properties.

Although support documentation mentions that you can use HTML alongside table field data, I am not seeing the option in v2. Perhaps it is inherently enabled in the new v2 component?

The Ink Text component is essentially the new Template component (has HTML enabling), however, I need the Ink Table template for this particular function.

Let me know if I am missing something here. Any input appreciated, thanks.
Photo of Jon A.

Jon A.

  • 172 Points 100 badge 2x thumb

Posted 3 months ago

  • 4
Photo of Luzie Baumgart

Luzie Baumgart, Official Rep

  • 2,240 Points 2k badge 2x thumb
Thank you Jon for reporting this. We will check in with our product engineers and the responsible team for the documentation.
I'm afraid I don't see a "Allow HTML" option either.
Photo of Kasey Arnold-Ince

Kasey Arnold-Ince

  • 130 Points 100 badge 2x thumb
Hi, Jon, and Luzie, thanks for bringing this to the attention of documentation. The inclusion of the Allow HTML property in the Ink Table component's template feature was my error, and has been removed from the topic.

Note that in Ink, HTML is not currently supported for template fields.  

My apologies for any inconvenience this has caused ...
Photo of Jon A.

Jon A.

  • 172 Points 100 badge 2x thumb
This is somewhat concerning. This should be added to the Ink Table component as soon as possible. 

The v2 Table component currently cannot allow HTML - which was possible in its v1 version. Which makes the conversion of any v1 pages built out with this specific function extremely difficult to impossible (I am not seeing any alternatives here).

In my case, this limitation is affecting the v2 rebuild of a Master page, which makes an API conversion for any Child pages basically impossible at this time.
Photo of Kasey Arnold-Ince

Kasey Arnold-Ince

  • 130 Points 100 badge 2x thumb
Jon, I hear your concerns. To quote our director of product experience, it's not our desire to remove this functionality.  We simply didn't have time to include it--with the specific application requirements we have for Spark--in time for the current release. 

Further work to include selected HTML options in Tables is already on the roadmap. 
(Edited)
Photo of Paul

Paul

  • 666 Points 500 badge 2x thumb
any updates on this?  Expected timeline?
Photo of John Dahlberg

John Dahlberg, Champion

  • 2,716 Points 2k badge 2x thumb
Second, Third, Fourth and Fifth on this item.  This is a pretty big deal
Photo of Chandra V

Chandra V, Champion

  • 7,270 Points 5k badge 2x thumb
Sixth.  Is the roadmap specific to tables or template fields in general?  I'm not even able to to display an image on a page in V2 that I used to refer to via html.