CLONE 2020R3 - Forecast Basis - Causing problems in production

After looking into an issue where the Restaurant Accuracy was not being populated in Production we dug in and found some things....

• When a forecast is imported, the line for Actual, is shown in purple on the Evaluator, this is triggered when ExternalGenerationDate is not Null.
• When the forecast basis is NOT supplied by the AWS Forecast Import we assume a ForecastBasis value of 1 = Gross Actual
  • Note: Null also represents Gross Actual
• When Quantiphi start to supply the forecast basis, it will be supplied as either:
  • GrossActual = 1
  • NetSales = 0
  • The goal of the enhancement for this feature was to support NetSales

Things that we have seen, but do not have answers to, and data is being cleaned up for!

1. It appears that the forecast basis was set to 0 for all forecasts from 5/31 onwards.
   • Was there a deployment script to do this?
   • Why 0, and not Null, or 1, as all existing forecasts are Gross Actual, not Net Sales
2. When the forecast is imported, and the ForecastBasis is set to 0, the forecast Evaluator does not display the Restaurant Accuracy
   • 
   • 
3. The Forecast Basis is being set to zero for InFORM generated forecasts, is this expected, or should this column be left as Null for InFORM generated forecasts?
   • Note: the evaluator works fine when the ExternalGenerationDate is Null

Note: Cherlyn Thomas is cleaning up the data in Prod, so that stores can once again see the Restaurant Accuracy.
I have a suspicion, that after today, the Imported Forecasts have a Forecast Basis of 1, so will reflect the Restaurant Accuracy correctly.
I can cause the error, by manipulating data in the non-prod environments

This sheet, shows some of the details of what we had saw: https://docs.google.com/spreadsheets/d/1Rvv5t3QEvgiMqIiEnG3a86HStHI1W--atwZVsyH0njs/edit?usp=sharing
Tabs:

1. Store 02158 (The store that called in the issue)
2. Imported ForecastBasis = 0 (From Quantiphi)
3. Not Imported ForecastBasis = 0 (InFORM Generated)