Forum Discussion
Forecast V Actual Comparison Table
Hi TheG,
In your scenario, since FORECASTPF table and ACTUALPF table almost have the same table structure, you needn't to use two tables. You can add then into one table with FORECAST and ACTUAL column. Select Combine > Merge Queries from the Home tab on the ribbon.
Regards,
Charlie Liao
- TheG9 years ago
Advocate I
Thanks v-caliao-msft
When i merge i dont get the complete matches probably as some account numbers are not in both tables...i guess i need to rework the table layout and split account numbers out, jobs, account names etc..
- Anonymous9 years agoNot applicable
As noted above and based on the sample data screenshot, merging Actuals and Forecast could be problematic - you have multiple Actual records for July 2014, but only 1 Forecast record that I can see for that month.
- TheG9 years ago
Advocate I
HI Anonymous yep i think i need to re-organise my tables design.
- Anonymous9 years agoNot applicable
In some cases, you might prefer to keep them separate, at least as staging tables - e.g. update scenarios where you're adding new Actuals each month, checking in case Actuals for a new Account Number or Job Number have been added but no Forecast exists for it etc.