Issue: Can't edit Assumption Accounts
Assumption accounts are only editable at the Top (Only) level in your organization. These accounts are global drivers and a single value in the account at the Top (Only) level applies to all levels in your organization. To access the Top (Only) Level on a sheet, expand your organization structure in the top right level drop down and scroll to the bottom.
Error: This formula refers to a level that cannot be referenced from this level
This error can be resolved by navigating to the account settings page for the account and then making the value of the account public on a levels. This area of the application can be found on the Modeling > Accounts page for your specific account type on the right hand panel under the "Data Privacy Settings" tab. These settings prevent users from being able to reference an account for levels they are not assigned to which is why the default setting is "Value of Account is private".
You can read more about Data Privacy settings in our article covering General Ledger Account Fields and Settings as these settings work similarly across Account types.
Issue: Actuals does not show for an account
You can disable Actuals on an account by account basis using the setting No Actuals for Account (Show Plan Data). You can modify this setting on the right panel of the Modeling > GL/Custom/Metric Accounts page under the first tab.
If the account is set to Enable Actuals, but Actuals are still not showing, one thing you might check is if the account has data in the Actuals version itself. You can do so by changing the drop-down in the upper-right of a sheet to your Actuals version and looking at the same sheet and level for the Actuals months.
Issue: Can't change the tagged attribute for a child account
A child account will always default to the the tagging of its parent, as attribute tagging propagates to children accounts. This will prevent you from updating the attribute tagging for children accounts. If most of the values under a parent should have the same attribute tagging, but one or two may be different, you might try the following:
1. Assign the parent account an attribute value. This will assign the attribute value to all children accounts of the parent.
2. Reassign the parent account to none. When the parent account is untagged, all of the child accounts will retain the attribute assigned in Step 1.
3. Update any child accounts that need to be assigned a different attribute than what was assigned in Step 1.
Issue: Metric account does not evaluate correctly in time rollups
A time modifier on a formula like [time=this-X] is calculated relative to the current time period where this is always the lowest time strata of the sheet in question.
Metric accounts are designed to re-evaluate in roll-up periods, and as such, "this-1" doesn't make sense in a rollups since this would be a quarter or full year for some cells. As a result, metric accounts do not support this form of time modifier and will drop the time modifier when evaluating in time rollup periods.
As a workaround, you may want to create a separate account to perform time shift calculations. You can then reference that new account in the metric account removing the need for time modifiers from the metric account altogether.
For example, ACCT.Example[time=this-1] will not evaluate properly in a metric account. However, you can build a new custom account, and place this same formula as a "master formula" for that account. You can then set ACCT.New_Custom as the formula in your metric account if desired.