Welcome to the community, @Maureen_Holland! :grinning_face_with_big_eyes: You didn’t provide details on what these images are tied to conceptually, so this might not work, but I’m going to share it anyway.
Make a separate table for images, with one image per record, each with its own alt text in a single {Alt Text}
field. Then link to these image records from your main table as needed, with one or more images linked per primary record. Add a lookup field to see the images all in one place (the primary record in the oImages]
table can’t be an attachment, so they’ll need to be attached in another field), and another lookup/rollup to collect the alt tags. The API can access the images and their respective alt tags by using the links.
Welcome to the community, @Maureen_Holland! :grinning_face_with_big_eyes: You didn’t provide details on what these images are tied to conceptually, so this might not work, but I’m going to share it anyway.
Make a separate table for images, with one image per record, each with its own alt text in a single {Alt Text}
field. Then link to these image records from your main table as needed, with one or more images linked per primary record. Add a lookup field to see the images all in one place (the primary record in the oImages]
table can’t be an attachment, so they’ll need to be attached in another field), and another lookup/rollup to collect the alt tags. The API can access the images and their respective alt tags by using the links.
Thanks for the response! I think this could work. I have to check on how the current table is populated. The table with multiple images is a synced view from a base I don’t have access to at the moment.