HTML allowed in v2 Table template fields ?

Jon A.Jon A. ✭✭
edited June 19, 2020 in Ideas
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.
9 votes

Awaiting Review · Last Updated


  • Luzie BaumgartLuzie Baumgart 🛠️ 
    edited December 19, 2018
    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.
  • edited December 19, 2018
    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 ...
  • Jon A.Jon A. ✭✭
    edited December 19, 2018
    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.
  • edited December 21, 2018
    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. 
  • PaulPaul ✭✭
    edited September 12, 2019
    any updates on this?  Expected timeline?
  • John DahlbergJohn Dahlberg ✭✭✭✭
    edited September 17, 2019
    Second, Third, Fourth and Fifth on this item.  This is a pretty big deal
  • edited September 17, 2019
    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.
  • John DahlbergJohn Dahlberg ✭✭✭✭
    edited March 22, 2019
    Can the page XML be edited to add this in the meantime?
  • edited September 17, 2019
    Any update on the timing of this?
  • BillBill 💎
    edited May 12, 2020
    Is there an update on this?
  • Eugene RinehartEugene Rinehart ✭✭✭
    edited September 17, 2019
    Bump. Would really like to see this built out. 
  • PaulPaul ✭✭
    edited September 17, 2019
    Any updates on this?  I have a lot of use-cases where we want to display images or iframes (gasp!) inside a table related to the row data.  Is there any way to do this in v2?
  • edited September 26, 2019
    Any updates? Lacking this and field renders via javascript is extremely limiting.
  • edited October 18, 2019
    Hey everyone. Really appreciate the feedback on this. We've got this one in our backlog. At this point it's not being worked on, but if/when that changes, we will let you know. 
  • Jackson AlexanderJackson Alexander Sr. Director, Product Experience Chattanooga, TN ✭✭✭
    edited October 21, 2019
    Hi everyone, we have been working on extensibility options for Ink components (v2), and we plan to have custom field renderers and HTML support options for Tables in the 12.3 release before the end of the year. We have also added Conditional Styling (conditionally apply a style variant) to the Display Logic for Ink components (12.2 release), and we're adding support for applying Conditional Styling to fields in Tables as well in 12.3.

    These upgrades will provide a lot of additional styling flexibility as well as help provide a viable migration path from v1 to v2 for pages with customized Tables.

    We greatly appreciate your patience and feedback.
  • edited January 2, 2020
    Hey there and Happy New Year! Has this feature been updated and included yet? This was a core item that we leverage in our V1 pages and is currently limiting our ability to create new pages.... It is the New Year and I don't see a 12.3 version release....
  • MansourMansour ✭✭✭✭
    edited April 22, 2020
    Any chance we can get this on Spark Update 3?  I saw that it still was not implemented.
  • Arne-Per HeurbergArne-Per Heurberg ✭✭✭✭
    edited April 24, 2020
    Was this added to 12.4.3? Can't seem to find it if so. 
  • Matt BrownMatt Brown ✭✭✭✭
    edited May 21, 2020
    Hi all, 

    Quick update - this feature is in active development for Spark Update 4. Thanks!

  • MansourMansour ✭✭✭✭
    edited May 18, 2020
    Wonderful news!  Thank you Matt
  • BillBill 💎
    edited June 19, 2020
    When is Spark Update 4 planned?
  • Jackson AlexanderJackson Alexander Sr. Director, Product Experience Chattanooga, TN ✭✭✭

    Hey BIll,

    Our next release which includes support for HTML in template fields is slated for the end of August.

  • Thank you Jason

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!