Also how would you delay the phasing = eg IT Salary value is for the months April - Dec therefore the phasing should start in April

Hi Alison,

Instead of dividing by 365 x 12 in the 'Inserted Division' step you'd use another table that has the various phasing rules for each account and bring that information in with a merge tables step. e.g. in the other table with your phasing rules IT would have the following rules:

Month Rate

Jan      *0

Feb      *0

Mar     *0

Apr    /365*30

May   /365*31

June   /365*30

etc.

You'd then use this data in your Division step instead of Number.Round([Annual Budget] / 365 * Date.DaysInMonth([Month]),2)

Mynda

Would you recommend this is done in power query or once the data is in power pivot

After merging is it the rule to then unpivot all columns before putting in power pivot 

You should always add calculated columns in Power Query if possible as it's more efficient than adding columns in Power Pivot.

There wasn't any merging performed in lesson 7.08 so I'm not sure what you're referring to, but a merge doesn't always mean you follow with an unpivot. The goal is to provide Power Pivot with tabular data, so you only unpivot if your data isn't in a tabular format. If this question refers to a different lesson, then please start a new question.

I should add, as mentioned in the Merge tutorial 3.04, a merge is similar to doing a VLOOKUP to bring data in from one table to another based on matching a value or values common to both tables.

I was referring to where you had the Actual and Budget figures in their own columns.   Would you unpivot these before sending to power pivot?

There is no actual data in the 7.08 file, it only has budget data. However, it would be correct to have a column for actuals and a separate column for budget as this would be a tabular layout.