Skip to main content
Solved

FORMS > Long Text > Numbered List

  • August 15, 2025
  • 4 replies
  • 54 views

Forum|alt.badge.img+3

Anyone else have issues with numbered lists in long text boxes in their forms?

For a numbered list I would expect:

 

But I’m getting this:

 

 

Best answer by trichardson

I just received this email from support. Looks like it’s an “unsupported feature” which seems wild? How do you support numbered lists but not sublevels?

FWIW I’m not deeply concerned; it’s just an oddity to me.
 

Hi Troy,

Guillermo from Airtable Support.

Thank you so much for the clarification and for sharing the structure you're aiming for — I can see the level of detail you're trying to convey, and I really appreciate the effort you've put into formatting your content.

At the moment, long text fields in Airtable with rich text enabled support basic formatting like bold, italics, bullet points, and numbered lists. However, nested or multi-level lists (like 1. a. b.) aren’t currently supported, so what you're trying to do won't render as intended within the field.

That said, there are a couple of workarounds that might help:

  • You can manually simulate sublevels using dashes or arrows, like:
    1. Test
    - a. Subtest
    - b. Subtest

  • Or visually separate your levels using spacing or consistent symbols to preserve structure.

I'd love to pass this feedback along to my team as a way we could improve the product further—thanks for surfacing it! I'll share this with our engineering/product teams, hoping we can make improvements along these lines at some point in the future. We apologize for the present inconvenience and appreciate you sticking with us in the interim!

Best,
Guillermo-Airtable Support Specialist

 

Also ​@TheTimeSavingCo, here’s a onedrive link. I don’t think I can embed a whole video.

 

Airtable.mp4

4 replies

ScottWorld
Forum|alt.badge.img+35
  • Genius
  • 9808 replies
  • August 15, 2025

That might be a bug. You may want to open a support ticket with support@airtable.com about this.

- ScottWorld, Expert Airtable Consultant 


TheTimeSavingCo
Forum|alt.badge.img+31

Interesting!  As a datapoint this seems to be working fine for me:

 

Any chance you could do a screen recording of how you’re entering the data?  I tried to delete lines, insert lines, etc, but it all seemed to work!


Forum|alt.badge.img+3
  • Author
  • New Participant
  • 1 reply
  • Answer
  • August 18, 2025

I just received this email from support. Looks like it’s an “unsupported feature” which seems wild? How do you support numbered lists but not sublevels?

FWIW I’m not deeply concerned; it’s just an oddity to me.
 

Hi Troy,

Guillermo from Airtable Support.

Thank you so much for the clarification and for sharing the structure you're aiming for — I can see the level of detail you're trying to convey, and I really appreciate the effort you've put into formatting your content.

At the moment, long text fields in Airtable with rich text enabled support basic formatting like bold, italics, bullet points, and numbered lists. However, nested or multi-level lists (like 1. a. b.) aren’t currently supported, so what you're trying to do won't render as intended within the field.

That said, there are a couple of workarounds that might help:

  • You can manually simulate sublevels using dashes or arrows, like:
    1. Test
    - a. Subtest
    - b. Subtest

  • Or visually separate your levels using spacing or consistent symbols to preserve structure.

I'd love to pass this feedback along to my team as a way we could improve the product further—thanks for surfacing it! I'll share this with our engineering/product teams, hoping we can make improvements along these lines at some point in the future. We apologize for the present inconvenience and appreciate you sticking with us in the interim!

Best,
Guillermo-Airtable Support Specialist

 

Also ​@TheTimeSavingCo, here’s a onedrive link. I don’t think I can embed a whole video.

 

Airtable.mp4


TheTimeSavingCo
Forum|alt.badge.img+31

Thanks for the link!  I tried doing exactly what you were doing and it worked fine for me:

I was using Firefox for this, and so on a whim I went to test it on Brave and I managed to replicate it!

This definitely doesn’t count as a workaround given we can’t control what browser the form submitters are using though, so this really isn’t that useful heh