# Copy data from Table A to Table B, creating rows in the process, then delete data from Table A

**URL:** <https://community.glideapps.com/t/copy-data-from-table-a-to-table-b-creating-rows-in-the-process-then-delete-data-from-table-a/86232>\
**Category:** Ask for Help\
**Created:** [February 2, 2026, 7:18pm UTC](https://community.glideapps.com/t/copy-data-from-table-a-to-table-b-creating-rows-in-the-process-then-delete-data-from-table-a/86232 "2026-02-02T19:18:40Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [February 6, 2026, 4:53pm UTC](https://community.glideapps.com/t/copy-data-from-table-a-to-table-b-creating-rows-in-the-process-then-delete-data-from-table-a/86232/21 "2026-02-06T16:53:38Z")

</div>

> [@MJolley](#):
>
> if there was a way to make an “upload student data” function where someone could import all of the data in step 1 through the app itself instead of through the Table backend

Only real solution I know of:

> [@outbox\_tray Allow User to Upload and Import CSV Files Tutorial](https://community.glideapps.com/t/allow-user-to-upload-and-import-csv-files-tutorial/82267):
>
> waving_hand Hey fellow Gliders! Allowing users to import CSV data is a feature not natively supported in Glide, but it can be achieved through clever workarounds. The video breaks down two primary methods for handling bulk data: one Method 1: Looping Workflow (for Smaller Imports) This approach involves creating a workflow that iterates through each row of a CSV file and adds it as a new record. white_check_mark Pros: Relatively straightforward to set up within Glide. prohibited Cons…

Deleting access rows through a relation wouldn’t use any updates with glide data sources. It’s a direct delete action without the need to loop.

> [@MJolley](#):
>
> another that pulls in the value from “Allow Students to Access App” based on whether or not they are a “Staff” or a “Student.” This is how I use a single toggle switch in the app to state whether or not each specific user should have access. But I don’t have a good way to then turn that into a workflow and revoke access yet.

If you want to use the toggle, I would still replace it with a button or custom AI component that just adds or removes the access row. But I don’t think you need that. When importing students, I would also import into the access table. When you are ready to remove access for the students, whether you rely on a toggle Boolean or not, use a relation or query to the access table to get only the students you want to delete and just delete through the relation/query. Delete can delete multiple browser through a relation without complex looping workflows.

Adding rows to the user and access table should be the only hard part. Removing rows from the access table is super easy as long as it has enough information in it to build your relation or query.

---

_[View the full topic](https://community.glideapps.com/t/copy-data-from-table-a-to-table-b-creating-rows-in-the-process-then-delete-data-from-table-a/86232)._