# Best way to handle transfers of gages from multiple locations

**URL:** <https://forum.cybermetrics.com/t/best-way-to-handle-transfers-of-gages-from-multiple-locations/127>\
**Category:** GAGEtrak\
**Tags:** gagetrak\
**Created:** [February 2, 2026, 7:15pm UTC](https://forum.cybermetrics.com/t/best-way-to-handle-transfers-of-gages-from-multiple-locations/127 "2026-02-02T19:15:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![colin.ful](https://avatars.discourse-cdn.com/v4/letter/c/91b2a8/32.png) [@colin.ful](https://forum.cybermetrics.com/u/colin.ful)\
**Post date:** [February 2, 2026, 7:15pm UTC](https://forum.cybermetrics.com/t/best-way-to-handle-transfers-of-gages-from-multiple-locations/127/1 "2026-02-02T19:15:23Z")

</div>

I’m trying to figure out how to set up my workflow for transfers. Very often we will collect 10 items from 10 different locations to return to the cal lab. I can do a separate transfer for each item, but that adds up quickly and takes a while, particularly with the bugs that happen when doing transfers from the Gages view. The problem is that if I do a group transfer, there is only one From Location I can list. I played with leaving it blank and was able to transfer multiple gages simultaneously, but I couldn’t then tell where each gage was coming from in the Transfers view and I couldn’t find any record. My current workaround is to list the last location in the Storage Location field for each gage, but I’m wondering if there’s a better way to do this?

---

<div class="post-metadata">

**Author:** ![DrewW](https://avatars.discourse-cdn.com/v4/letter/d/e99b99/32.png) [@DrewW](https://forum.cybermetrics.com/u/DrewW)\
**Post date:** [February 2, 2026, 9:02pm UTC](https://forum.cybermetrics.com/t/best-way-to-handle-transfers-of-gages-from-multiple-locations/127/2 "2026-02-02T21:02:57Z")

</div>

Hello Colin,

Unfortunately there is no way at this time to include multiple from locations on a transfer record. However, we do believe this could be a beneficial add-on, and I have forwarded this onto our development team as a feature suggestion.

---

<div class="post-metadata">

**Author:** ![colin.ful](https://avatars.discourse-cdn.com/v4/letter/c/91b2a8/32.png) [@colin.ful](https://forum.cybermetrics.com/u/colin.ful)\
**Post date:** [February 2, 2026, 9:24pm UTC](https://forum.cybermetrics.com/t/best-way-to-handle-transfers-of-gages-from-multiple-locations/127/3 "2026-02-02T21:24:23Z")

</div>

Okay, good to know, thank you Drew! Honestly, even just adding a From Location column to the table would be helpful.

 ![image](https://canada1.discourse-cdn.com/flex008/uploads/cybermetrics/original/1X/df236c6e4997fc5da2e7b0e6a13f32fd44fe3457.png)

---

<div class="post-metadata">

**Author:** ![DrewW](https://avatars.discourse-cdn.com/v4/letter/d/e99b99/32.png) [@DrewW](https://forum.cybermetrics.com/u/DrewW)\
**Post date:** [February 3, 2026, 9:39pm UTC](https://forum.cybermetrics.com/t/best-way-to-handle-transfers-of-gages-from-multiple-locations/127/4 "2026-02-03T21:39:52Z")

</div>

Colin,

I have passed this information over to our development team as well, thank you as well!