# Move item from one data table to another? **URL:** \ **Category:** Ask for Help\ **Created:** [July 25, 2025, 12:10am UTC](https://community.glideapps.com/t/move-item-from-one-data-table-to-another/83429 "2025-07-25T00:10:53Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![gwheat](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gwheat/32/90693_2.png) [@gwheat](https://community.glideapps.com/u/gwheat)\ **Post date:** [July 25, 2025, 12:10am UTC](https://community.glideapps.com/t/move-item-from-one-data-table-to-another/83429/1 "2025-07-25T00:10:53Z")
Essentially, I have a page with a data table setup to act as a mini blog of sorts. When the publish date of the post [is before today] in the workflow, I would like to move that post to a different data table. Is this possible? I tried to “add row” and “set column values” with no luck. ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [July 25, 2025, 12:20am UTC](https://community.glideapps.com/t/move-item-from-one-data-table-to-another/83429/2 "2025-07-25T00:20:54Z")
Before making an advice, I would suggest you just using something like an If-Then-Else column based on your publish date. Then you can structure things around that If-Then-Else column. If you still need to move that post to a different table, you can have a Scheduled Workflow to: - Loop through your posts table and filter by rows that have a publish date before today. - Add a row to the new table with the same info from the posts row that is being looked at. - Delete the original row. ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [July 25, 2025, 12:23am UTC](https://community.glideapps.com/t/move-item-from-one-data-table-to-another/83429/3 "2025-07-25T00:23:52Z")
Agree with @ThinhDinh. This smells. Wanting to move data from one table to another is almost always an indicator of bad design. Can you explain why it’s necessary to do this? ---
**Author:** ![gwheat](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gwheat/32/90693_2.png) [@gwheat](https://community.glideapps.com/u/gwheat)\ **Post date:** [July 25, 2025, 12:30am UTC](https://community.glideapps.com/t/move-item-from-one-data-table-to-another/83429/4 "2025-07-25T00:30:36Z")
Appreciate the quick responses! I have a blog post tab with dates of puclication for each post. On my homepage, I want to show the most recent post only (I have it limited to 1), but I can’t figure out how to show [today’s post] if there is one for yesterday in the same table. I am okay keeping everything in the same table if I can make just the most recent post show. ---
**Author:** ![gwheat](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gwheat/32/90693_2.png) [@gwheat](https://community.glideapps.com/u/gwheat)\ **Post date:** [July 25, 2025, 12:34am UTC](https://community.glideapps.com/t/move-item-from-one-data-table-to-another/83429/5 "2025-07-25T00:34:55Z")
To add to that, on my data table with the scheduled to post items, I don’t want them showing up on the other data board either. So I thought having two data tables would be a good way to do this. ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [July 25, 2025, 12:36am UTC](https://community.glideapps.com/t/move-item-from-one-data-table-to-another/83429/6 "2025-07-25T00:36:03Z")
Several ways you could do that. Here is one option: - Create a Query column, target it at the table, sort by Publish Date in descending order, and apply a limit of 1 - Use the Query column as the source of your collection ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [July 25, 2025, 12:37am UTC](https://community.glideapps.com/t/move-item-from-one-data-table-to-another/83429/7 "2025-07-25T00:37:27Z")
> [@gwheat](#): > > To add to that, on my data table with the scheduled to post items, I don’t want them showing up on the other data board either. To deal with that, just add a filter to the Query column that I suggested: “Publish Date is on or before Today” > [@gwheat](#): > > So I thought having two data tables would be a good way to do this. Nope 😉 ---
**Author:** ![gwheat](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gwheat/32/90693_2.png) [@gwheat](https://community.glideapps.com/u/gwheat)\ **Post date:** [July 25, 2025, 2:04am UTC](https://community.glideapps.com/t/move-item-from-one-data-table-to-another/83429/8 "2025-07-25T02:04:42Z")
I’m unable to see the Query column as a source when I add a collection. It only shows the data tables. ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [July 25, 2025, 2:19am UTC](https://community.glideapps.com/t/move-item-from-one-data-table-to-another/83429/9 "2025-07-25T02:19:07Z")
That sounds like you may have created the column in a table that the current screen cannot access. It must be either in the table the screen is attached to, or in the User Profile row. ---
**Author:** ![gwheat](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gwheat/32/90693_2.png) [@gwheat](https://community.glideapps.com/u/gwheat)\ **Post date:** [December 31, 2025, 4:17pm UTC](https://community.glideapps.com/t/move-item-from-one-data-table-to-another/83429/10 "2025-12-31T16:17:12Z")
Just to follow up. I was able to get it working, thanks! A mix of view permissions and filtering.