# Transpose data from records to fields **URL:** \ **Category:** Airtable Questions\ **Created:** [June 21, 2023, 6:42pm UTC](https://air.tableforums.com/t/transpose-data-from-records-to-fields/696 "2023-06-21T18:42:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Michael](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@Michael](https://air.tableforums.com/u/Michael)\ **Post date:** [June 21, 2023, 6:42pm UTC](https://air.tableforums.com/t/transpose-data-from-records-to-fields/696/1 "2023-06-21T18:42:21Z")
I have been scratching my head over this one and could use a nudge in the right direction. The simplified use case is: Table A has 1000 records. Field 1 = Category Field 2 = Label There are 100 categories hence 100 sets of 10 ‘Labels’ each. Some of the ‘Labels’ feature in multiple categories … there are ~150 ‘Labels’ rather than 1000. The goal is to create a different form for each of these 100 categories using one of the fields in Table A as the Field Name in the form. Essentially, the goal is to _transpose_ a **record** from Table A into a **field name** in Table B. The key is that: the data in Table A is not static and the field names in Table B need to reflect any changes. Some ideas: - One can update the field names using ‘updateNameAsync’ (I believe), but can I transpose the data as well? - Export (sync) from Airtable to Google Sheets and transpose the data there, then reimport to Airtable in a new table 150 fields (Labels) wide? - The pivot table extension **displays** what I’m after, but how to get that into a new table? Any thoughts? ---
**Author:** ![joshsorenson](https://avatars.discourse-cdn.com/v4/letter/j/8edcca/32.png) [@joshsorenson](https://air.tableforums.com/u/joshsorenson)\ **Post date:** [June 21, 2023, 9:38pm UTC](https://air.tableforums.com/t/transpose-data-from-records-to-fields/696/2 "2023-06-21T21:38:54Z")
Why are the field names needing to change in Table B? I’m not sure I understand that. Instead I’d make a form in Fillout and just Display the question differently and write to the same fields. That will get you a cleaner result. Then just load in the field names via url parameters that you can pull from Table 1. ---
**Author:** ![bfrench](https://yyz1.discourse-cdn.com/flex029/user_avatar/air.tableforums.com/bfrench/32/46_2.png) [@bfrench](https://air.tableforums.com/u/bfrench)\ **Post date:** [June 21, 2023, 10:12pm UTC](https://air.tableforums.com/t/transpose-data-from-records-to-fields/696/3 "2023-06-21T22:12:19Z")
> [@Michael](#): > > the goal is to _transpose_ a **record** from Table A into a **field name** in Table B. I get it, but that’s a bad goal. 😉 You need a new goal - like _make one [virtualized] form that acts like a hundred different forms_. ---
**Author:** ![Michael](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@Michael](https://air.tableforums.com/u/Michael)\ **Post date:** [June 22, 2023, 12:51pm UTC](https://air.tableforums.com/t/transpose-data-from-records-to-fields/696/4 "2023-06-22T12:51:58Z")
@joshsorenson - thank you! This is ideal. I see that I was unnecessarily overcomplicating a simple problem. The URL parameters do the trick nicely. ---
**Author:** ![Michael](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@Michael](https://air.tableforums.com/u/Michael)\ **Post date:** [June 22, 2023, 12:57pm UTC](https://air.tableforums.com/t/transpose-data-from-records-to-fields/696/5 "2023-06-22T12:57:33Z")
Hi @bfrench - yes, that sounds like a far better goal. I suspect that it’s beyond my scope for the time being. ---
**Author:** ![joshsorenson](https://avatars.discourse-cdn.com/v4/letter/j/8edcca/32.png) [@joshsorenson](https://air.tableforums.com/u/joshsorenson)\ **Post date:** [June 22, 2023, 2:09pm UTC](https://air.tableforums.com/t/transpose-data-from-records-to-fields/696/6 "2023-06-22T14:09:29Z")
What I described on [fillout.com](http://fillout.com) will achieve that very easily.