Multiple Tables Report
Hi all, I have three project tables from different business units, each with fields for contract value, contract date, and other details. We want to create a dashboard with reports combining the da...
Forum Discussion
MarkShnier__You
Qrew Legend
Qrew LegendI have an alternate suggestion. I would create the fourth table that Mike talks about but I would set the key field to be a prefix corresponding to each of your three separate tables and then a dash and then the record ID of the source table.
In each of the three tables I would create a formula to make that key field of the fourth table so for example it would read like
List("-", "Business Unit 1", ToText([Record ID#]))
Then create three saved table to table copies to copy the fields from respectively each of the source tables into the combine table.
Then I would set a pipeline to run every hour say which would be to first delete all the records in the combined table and then to successively run each of the saved table to table copies.
The make Request step to run the saved T2T copy would look like.
mycompany.quickbase.com/xxxxxxxx/?act=API_RunImport&ID=10
Hi Mark,
I understand this idea, and I also read about Mike's option.
I find your option more complex, and I'm not clear on the benefits compared to Mike's approach. Could you help me understand the advantages? Is the other method less scalable?
Thanks!
- MarkShnier__You
An advantage of my method is that if for some reason a pipeline fails, then in Mike's solution, the combined table may be different from the source tables.
Also in Mike's solution, you need a lookup field for each field you have in each of the source tables, plus a formula field to resolve which lookup to use. So a lot of extra fields to create.