Planning Views and Exports
Present model results with focused views and charts, share scoped access, and generate repeatable CSV or Excel exports.
Planning views and exports turn a working model into a reviewable result. Use saved views for live, focused access. Use exports for a point-in-time file.
Choose a Presentation
| Presentation | Use it when |
|---|---|
| Grid | A model author needs to inspect variables, formulas, and periods. |
| Chart | A reviewer needs to understand a trend or comparison quickly. |
| Saved view | A teammate needs a stable slice of the live model. |
| Export | A reviewer or downstream process needs a file. |
The presentation should answer the decision without exposing unnecessary model detail.
Saved Views
A saved view keeps a useful model presentation, including the selected model context and visible planning scope.
Create a view for:
- a board review
- a department plan
- a scenario comparison
- a budget-versus-actual review
- a weekly liquidity review
- a focused set of assumptions and outputs
Use a specific label such as Board review, Collections +30 days or Sales plan, FY27 base.
A saved view does not freeze formulas, actuals, or source data. It presents the current model through the saved scope.
Charts and Comparisons
Use charts when the shape of the result matters more than individual cells.
A useful chart should have:
- a clear business title
- only the variables needed for the question
- the correct period range
- the intended scenario
- units that can be read without opening the formula
When a chart or table offers comparison controls, choose a scenario or comparable version and confirm both series use compatible time and currency settings.
Do not compare a version marked Not comparable as though its periods or units match the current model.
Share a Saved View
Only model owners can manage saved-view sharing.
- Open the sharing controls.
- Select the saved view.
- Select Share view.
- Choose a teammate.
- Assign the access level.
- Select Copy link.
- Open the link once to verify the scope.
Available access levels are:
- Can view
- Can comment, which also allows proposals from eligible scenario changes
- Can edit, which allows input and formula edits within the shared view when the teammate is eligible to edit
Sharing one view does not automatically expose every view in the model. The share is designed to show the selected view without exposing the full working model.
A saved view is a filtered lens, not a separate security model. A visible total can still include hidden rows beneath it, which may let a recipient infer a hidden value. A scenario filter also does not hide variables that fall back to the base. Hide sensitive totals and add explicit variable filters before sharing.
Verify Shared Access
Before sending the link, confirm:
- the model
- the saved-view label
- the active scenario
- visible variables
- visible periods
- comments that should be available
- the recipient's access level
Use the lowest access that supports the review.
Export a Model
Open Export and download or the export action from the model.
Supported saved export formats include:
- Formatted (.xlsx)
- Raw (.xlsx)
- Raw (.csv)
Linked-model scope
An export covers one of three scopes:
| Scope | Includes |
|---|---|
| Current | The current model only. This is the default. |
| All | The current model and every model linked to it |
| Custom | The current model and the linked models that you select |
All is stored as a rule, not as a fixed list. A saved definition using All re-resolves the set on every run, so a model linked after you saved the definition is included automatically.
Linked models are included only when all of these hold:
- the scope is All or Custom
- the export covers the whole model rather than a saved view
- the caller is a workspace Owner
Otherwise Eigenn exports the current model alone. A linked model that no longer exists for the team is dropped from the file rather than failing the export.
Review the export dialog before generation so the shape, columns, scenario, view, and revision are the intended ones.
Saved Export Definitions
A saved export definition keeps a reusable export configuration.
- Enter an export name.
- Choose a format.
- Select Save.
- Use Generate when you need the latest output.
Generating a saved definition runs it against the current state of the model. The definition is reusable. It is not a frozen receipt.
Saved definitions are model-scoped and shared with users who have full model access.
Export Run History
The export area shows recent runs, including:
- file name
- generation time
- row count
- status
- a download action when a stored artifact is available
A small export can download immediately. A larger export can be queued and appear in run history when it is ready.
An inline export can remain in history without a stored file for re-download.
Treat Exports as Point-in-Time Results
An exported file does not update when:
- source data refreshes
- formulas change
- the active scenario changes
- a version is restored
- the model timeline moves
- a saved view changes
Include the model, scenario, version, and generation date in the review context.
Troubleshoot
The shared link opens the wrong view
Select the intended saved view again, copy a new link, and confirm the URL contains the correct model and view context.
A teammate can view but cannot comment
Change the share to Can comment or Can edit. View access is read-only.
A chart comparison is unavailable
Confirm that the scenario or version is visible and comparable with the current model's time and currency settings.
An export is queued
Check export run history. Large files are completed asynchronously and can be downloaded after the run finishes.
A completed run has no download action
The file may have been delivered inline rather than stored. Generate the export again if another copy is needed.
A saved export contains newer values than the prior file
That is expected. A saved definition runs against the current model state each time.
A linked model is missing from the export
Confirm all three conditions: the scope is All or Custom, the export covers the whole model rather than a saved view, and you are a workspace Owner. A linked model that no longer exists for the team is dropped from the file rather than failing the run.