Combine two applications tables into single dashboard or report

  • 1
  • 1
  • Question
  • Updated 4 months ago
  • Answered

I have an application which host multiple projects with individual tasks due based on calendar days.  I now have a requirement to change one particular project tasks over to business days.

Since the task need to be either calendar or business days, I duplicated my application specifically for the project that needs to be converted over to business days.  I than modified my formula -work date field to reflect business days.

 

My question is: Is there a way to take the report from this new application and have its results added to the same report name in the original application.

I typically view the report to determine what tasks are due, and am hoping that I don’t need to jump between multiple applications.

I know that I can add a URL to link over the report, but a hoping that we wouldn’t have to perform extra steps in viewing.

 

For example:

App 1  has multiple project with tasks scheduled based on calendar days. I created a report to list out current task due called “all open task” I would see something like this

 

Project 1 Task due 7-30-18

Project 1 Task due 7-30-18

Project 2 Task due 7-30-18

Project 3 Task due 8-10-18

Project 3 Task due 8-11-18

Project 6 Task due 12-1-18

 

App 2 was a copy of App1, but only carried over new project that is based on business days. That is the only change. All fields, setting, report etc. are the same. If I run the same report “all open task” I see the new business day tasks

BusinessDayProject Task due 7-30-18

BusinessDayProject Task due 8-30-18

BusinessDayProject Task due 9-30-18

 

 

Ideally I would like to see a running report merging these into one report or dashboard

Project 1 Task due 7-30-18

Project 1 Task due 7-30-18

Project 2 Task due 7-30-18

BusinessDayProject Task due 7-30-18

Project 3 Task due 8-10-18

Project 3 Task due 8-11-18

BusinessDayProject Task due 8-30-18

BusinessDayProject Task due 9-30-18

Project 6 Task due 12-1-18

 

Photo of Priscilla

Priscilla

  • 30 Points

Posted 4 months ago

  • 1
  • 1
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 51,306 Points 50k badge 2x thumb
I strongly suggest that you abandon the duplicate app concept.  It will cause you no end of grief.  For starters you will have Duplicate maintenance and an inability to get consolidated Dashboards or even a simple consolidated report of Tasks.  Every user will need to go to two places for no good reason.  Twice the number of report subscription emails of My Tasks.  The list goes on and on.

I suggest instead that you make a required multiple choice field checkbox field to indicate if the task duration is in days or business days.  Then have a formula use that information to calculate the correct due dates.
Photo of Priscilla

Priscilla

  • 30 Points
thank you very much. This is a much easier method then were I was going. Everything is working beautifully,
Photo of Ⲇanom the ultimate (Dan Diebolt)

Ⲇanom the ultimate (Dan Diebolt), Champion

  • 26,502 Points 20k badge 2x thumb
One fundamental rule of databases is that once you copy a database you start the process of your data becoming corrupted because subsequent changes to the data or structure to either database will become difficult or impossible to reconcile. 

However, there are times when data in two different tables needs to be reported in one report. Typically in databases that use SQL this is done with a UNION query. This isn't possible with QuickBase but you can emulate the net result.

Let's say you have two tables dbid1 and dbid2. Create a third table dbid3 which will be used solely to temporarily view the merged data.

Using script and the API perform these stems:

1) Purge dbid3 

2) Query dbid1 and obtain csv1 using:
  dbid1?a=q&qid=6&opts=csv 
3) Query dbid2 and obtain csv2 using:
  dbid2?a=q&qid=6&opts=csv 
4) Import csv1 and csv2 into the third table dbid3 making sure the columns are similar

5) redirect to the appropriate report of dbid3 which will show the merged data

The resulting report will only be valid at the time you invoke the script but you can view the merged data, manipulate it or link back to the source data in either of the original tables using native formulas and features. The reason we purge dbid3 table at the start of the process is to generate fresh results each time you invoke the script.