Subsidiary views are difficult to work with and audit. Try and minimise their use especially for calculation modules; create groups of calculation modules instead with like dimensionality
Exceptions:
2.01-06a Display on Dashboards for analysis or filtering: Sometimes, to enhance the end user experience, attributes are needed to be shown on dashboards
2.01-06b Ratio Formulas: Numeric values for ratios need to be in the same module and are unlikely to need the full dimensionality
2.01-06c Synchronization for some dashboards: If you have dashboards that need to synchronize from a module, sometimes a specific line item is needed (Old UX)
2.01-06d Line items needed for sorting: Sometimes to facilitate a sort, the line items don't need the full module dimensionality
2.01-06e Reporting or Export modules: To utilize filtering in reports or to provide attributes for exports (model to model), you may need to have line items for the non-dimensional attributes. Ensure these are set as subsidiary views to minimize the calculations
Questions on this topic? See 2.01-06 Avoid Using Subsidiary Views in our Planual forum.