Forum Discussion
MarkShnier__You
Qrew Legend
5 years agoLet's back up a step here.
That's the whole reason you were doing this because you want to freeze to look up fields so they do not change?
If so, there is native functionality for this using snapshot fields.
https://help.quickbase.com/user-assistance/setting_up_snapshot_fields.html
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
That's the whole reason you were doing this because you want to freeze to look up fields so they do not change?
If so, there is native functionality for this using snapshot fields.
https://help.quickbase.com/user-assistance/setting_up_snapshot_fields.html
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
ChrisFaye1
5 years agoQrew Cadet
Thanks, Mark!
Unfortunately, the snapshot option only triggers when initiating the snapshot option in the field settings. The requirement of this process is that the user needs to be able to click a button (update something) that triggers a the snapshot and then those snapshots needs to be editable for possible manual future corrections.
Basically this is looking at the Property table's *current* rates at the time the rental application is placed for each individual rental application and freezing those values in an manually editable way.
It sounds like duplicating the look-up fields in the child table and doing the copy values locally in the button currently still the most efficient way. 🤷♂️
------------------------------
Chris
------------------------------
Unfortunately, the snapshot option only triggers when initiating the snapshot option in the field settings. The requirement of this process is that the user needs to be able to click a button (update something) that triggers a the snapshot and then those snapshots needs to be editable for possible manual future corrections.
Basically this is looking at the Property table's *current* rates at the time the rental application is placed for each individual rental application and freezing those values in an manually editable way.
It sounds like duplicating the look-up fields in the child table and doing the copy values locally in the button currently still the most efficient way. 🤷♂️
------------------------------
Chris
------------------------------
- OanaWhalen5 years agoQrew CadetChris,
Is there a reason you can't use automations to accomplish this? I have several automations in my applications that are triggered by a button that simply checks a box, then all my actions copy the necessary values as static entries. As long as one of the fields that gets copied is the Related Parent field record id, you can still use look-up fields for any fields you do want to follow changes in the parent record.
------------------------------
Oana Toma
------------------------------