Jotform table: How to add line break in the column with advanced formula to display calculated result?

  • Profile Image
    siouxmaeb
    Asked on September 18, 2021 at 10:14 PM

    Hi

    I tried this for a new calculated column:

    ={25}&IF({75}=BLANK(),"","<br /><br />"&{75})&IF({42}=BLANK(),"","<br /><br />"&{42})

    .... but when displaying the record, it still shows like:

    1) Inside the PDF

    1632017574_61469ca6b91ef_

    2) in the display mode (where I tried with "\n")

    1632017631_61469cdf61db3_

    Martin



  • Profile Image
    Gaetan_B
    Answered on September 19, 2021 at 05:30 AM

    Hello,

    Thank you for reaching out.


    I have a made a few tests and it is not currently possible to do that in the Tables.

    I can ask our developers to implement the functionality, but I won't be able to give you an ETA on the implementation.


    Best regards

  • Profile Image
    siouxmaeb
    Answered on September 24, 2021 at 05:13 AM

    Hi

    I found a way to add linebreak as char into the field value:

    1632474621_614d95fd9d764_

    After EXCEL Export of that record I can see, that the linebreak is taken over. It would be very nice, if that also would be seen as a linebreak in the tables view. There it appears as a BLANK.

    Finally I would like to enable a user to copy & paste the value out of the table field and reuse it elsewhere (including the linebreak), but since it is handled only as BLANK in the table the copy & paste also reflects as blank. So the missing part would be the correct formating in the table...

  • Profile Image
    siouxmaeb
    Answered on September 24, 2021 at 05:25 AM

    The same happens in the generated PDF. There it is also only a single line text and the linebreak is shown as a blank.

  • Profile Image
    ashwin_d
    Answered on September 24, 2021 at 11:54 AM

    If I understand your question correctly, you want to add a line break in the calculated column of the table. Is that correct?

    I am creating a feature request ticket and escalating it to our backend team. Though we cannot provide any ETA on this but we will get back to you as soon as we have any update form them.