What is the best practice if it is a connected table? You can't schedule table to table imports because it is connected.
This should be its own thread since I have run into this problem before, but I'll ask here since it is the same kind of problem. I have a connected table (People) with a relationship to another table (Tests) and a summary field that shows me earliest test date. Easy. Reporting requirements cause me to create a Days table with a "Date" as the key to display those earliest test dates and I create a relationship with the People table using the reference key of the earliest test date. Quick Base allows this, and this works, and everyone is happy right up until it doesn't work because those relationships based on a summary field can be wonky. (reports show "0" even when clicking on that "0" show multiple records in the drilldown report.). So, I think, "Well, I guess I need to take that summary value and put it in a hard-coded date field to base that relationship on." However, I have tried multiple automations that I just can't get to reliably fire and fill this out since the "change" is based on that summary field changing.
So, what is best practice here? I'm back to the relationship based on the summary field now and hoping it doesn't flake out. Is there a way to make that more stable or at least know when it might get weird? If not, what is the best way to populate this date field from the summary date field?
------------------------------
Tate Forgey
------------------------------
