One-time Lookup fields

Feature Ideas
1

This type of field Looks up its value only when the Link ID/Value controlling its lookup is created or deleted/recreated in the same table. Ie, change the Link ID and the field re-looks up if you need it to.

Use case: Staff Table/Record holds field: pay rate per hour. Each Shift record has a lookup field for the Staff pay rate field. Over time, admin adjusts the Staff record pay rate(hopefully up!), but traditional lookup fields will now update in all Shift Records containing that Staff ID - innacurate data salad.

Having a one-time lookup solves this as well as a myriad of other use-cases like using Templated data in one table to help create new records in diff tables (all new data in other tables is looked up AND then editable).

Thank you!

2

Hey @sparrow, thanks for sharing your idea. :slightly_smiling_face:

Do you have examples of similar functionality from other tools that we can test out?

3

If you use FileMaker Pro database, you’ll see it used widely there. A typical use case is basically all the looked up information on an invoice from addresses (yours and customers), to line items to line item prices to tax & even the footer text. If if those data points are not one time look ups, and someone changes them in the referenced tables. All your past invoices have now been altered, that would cause major problems for your bookkeeper/taxes.