GITBOOK-548: Default scenario and copy to base

visualbis · Aug 13, 2024 · 9f914eb · 9f914eb
1 parent 480b0f6
commit 9f914eb
Show file tree

Hide file tree

Showing 47 changed files with 36 additions and 20 deletions.
diff --git a/.gitbook/assets/image (1) (18) (1).png b/.gitbook/assets/image (1) (18) (1).png
diff --git a/.gitbook/assets/image (1) (18).png b/.gitbook/assets/image (1) (18).png
diff --git a/.gitbook/assets/image (1).png b/.gitbook/assets/image (1).png
diff --git a/.gitbook/assets/image (2) (18) (1).png b/.gitbook/assets/image (2) (18) (1).png
diff --git a/.gitbook/assets/image (2) (18).png b/.gitbook/assets/image (2) (18).png
diff --git a/.gitbook/assets/image (2).png b/.gitbook/assets/image (2).png
diff --git a/...(1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/...(1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/...(1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/...(1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/...(1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/...(1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/...(3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/...(3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/...age (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/...age (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/...s/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/...s/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/...ssets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/...ssets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/...ok/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/...ok/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (3) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (3) (1) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (3) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1).png
diff --git a/.gitbook/assets/image (3) (1) (1).png b/.gitbook/assets/image (3) (1) (1).png
diff --git a/.gitbook/assets/image (3) (1).png b/.gitbook/assets/image (3) (1).png
diff --git a/.gitbook/assets/image (3).png b/.gitbook/assets/image (3).png
diff --git a/.gitbook/assets/image (900) (2) (1).png b/.gitbook/assets/image (900) (2) (1).png
diff --git a/.gitbook/assets/image (900) (2).png b/.gitbook/assets/image (900) (2).png
diff --git a/.gitbook/assets/image (900).png b/.gitbook/assets/image (900).png
diff --git a/.gitbook/assets/image (920).png b/.gitbook/assets/image (920).png
diff --git a/.gitbook/assets/image (921).png b/.gitbook/assets/image (921).png
diff --git a/.gitbook/assets/image (922).png b/.gitbook/assets/image (922).png
diff --git a/.gitbook/assets/image.png b/.gitbook/assets/image.png
diff --git a/admin-console/settings/writeback.md b/admin-console/settings/writeback.md
@@ -30,7 +30,7 @@ Enter the connection name and click 'Save connection' to complete the connection
 
 The created connection will be listed on the Connections page.
 
-<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Connection created</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Connection created</p></figcaption></figure>
 
 ### 1.2. Edit/Delete connection
 

diff --git a/formula-syntax/time-intelligence-functions/monthperiod.md b/formula-syntax/time-intelligence-functions/monthperiod.md
@@ -29,6 +29,6 @@ MONTHPERIOD(2022,5)
 //Returns data from May, 2023
 ```
 
-<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Monthperiod without offset</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Monthperiod without offset</p></figcaption></figure>
 
 <figure><img src="../../.gitbook/assets/image (4) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Monthperiod with offset</p></figcaption></figure>
diff --git a/formula-syntax/time-intelligence-functions/nextnqtr.md b/formula-syntax/time-intelligence-functions/nextnqtr.md
@@ -23,4 +23,4 @@ NEXTNQTR(6)
 //Returns data for 6 quarters after the current quarter
 ```
 
-<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>NEXTNQTR</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>NEXTNQTR</p></figcaption></figure>
diff --git a/...r/11.-scheduling-reports/create-new-subscription/select-destination-s/README.md b/...r/11.-scheduling-reports/create-new-subscription/select-destination-s/README.md
@@ -94,7 +94,7 @@ When you click **Configure**, a pop-up appears where you can configure the table
 2. Select the workspace, semantic model, table, and the column that contains the email addresses.
 3. You also have the option to set up a filter if you wish to send users only specific records from the report. In the image below, we will only send the data related to the customer 'Claire Gute' using the filter option.
 
-<figure><img src="../../../../.gitbook/assets/image (900) (2).png" alt=""><figcaption><p>Dynamic table selection</p></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/image (900) (2) (1).png" alt=""><figcaption><p>Dynamic table selection</p></figcaption></figure>
 
 4. In the preview, notice how different categories are assigned to different email IDs in the dataset, specifying to whom the respective records would be sent. Click **Save**.&#x20;
 

diff --git a/working-with-inforiver/13.-context-awareness.md b/working-with-inforiver/13.-context-awareness.md
@@ -14,7 +14,7 @@ With Inforiver, you can configure filter context, which ensures that Inforiver v
 
 **Step 2**: In the popup window, enter the table and field name for which context awareness is being set up. You can enter multiple tables and categories using the Add new link. In this case, we are setting up filter context for Subregions.
 
-<figure><img src="../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Add table and category</p></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Add table and category</p></figcaption></figure>
 
 **Step 3**: Inforiver automatically generates the DAX code based on the tables and categories entered. Click on the Generate Dax button and copy the DAX.
 

diff --git a/...riteback-matrix-visuals/safe-procedures-for-copying-writeback-matrix-visuals.md b/...riteback-matrix-visuals/safe-procedures-for-copying-writeback-matrix-visuals.md
@@ -40,7 +40,7 @@ Inforiver generates a **notification** when a duplicate visual is detected.
 
 2. Expand the Profile menu and navigate to **Report Details**.
 
-<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 3. Click on the **Create** button in the Report Details side pane to detach the visual.
 

diff --git a/working-with-inforiver/4.-adding-business-logic-and-formulae/insert-image-urls.md b/working-with-inforiver/4.-adding-business-logic-and-formulae/insert-image-urls.md
@@ -6,7 +6,7 @@ Enhance data presentation and comprehension in your Inforiver reports with image
 The Power BI data category type should be ‘Image URL’ to embed images in reports.
 {% endhint %}
 
-<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Image URL data category</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Image URL data category</p></figcaption></figure>
 
 * **Cell-level images**
 

diff --git a/working-with-inforiver/5.-conditional-formatting/rules-if-conditions.md b/working-with-inforiver/5.-conditional-formatting/rules-if-conditions.md
@@ -56,7 +56,7 @@ When you use icons, you have an additional option to align your icons in the gri
 
 <div>
 
-<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1).png" alt=""><figcaption><p>Aligning icons</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Aligning icons</p></figcaption></figure>
 
 
 

diff --git a/working-with-inforiver/6.-working-with-charts/bar-and-pin-charts.md b/working-with-inforiver/6.-working-with-charts/bar-and-pin-charts.md
@@ -198,7 +198,7 @@ You can do this while creating a pin chart, or add them after creating a pin cha
 
 2. In the customization menu, click on the **Outliers** option.
 
-<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Click <strong>Outliers</strong></p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Click <strong>Outliers</strong></p></figcaption></figure>
 
 3. In the Outliers pop-up window, check **Enable Outlier.** If you wish to hide the values, select the option **Disable Label.** Enter the required positive and negative threshold values as shown below and Click **Apply**.
 

diff --git a/working-with-inforiver/7.-planning-budgeting-and-forecasting/forecasting.md b/working-with-inforiver/7.-planning-budgeting-and-forecasting/forecasting.md
@@ -112,23 +112,23 @@ The forecasted values are overwritten when the period is closed and the actuals
 
 If the column grand total is enabled, you can choose whether the grand total for the forecast measure should be derived from open periods, closed periods, or both. To customize the grand total for forecasts, click on the forecast column gripper and select the desired option from the **Aggregate total** section.
 
-<figure><img src="../../.gitbook/assets/image.png" alt=""><figcaption><p>Aggregate total for forecasts</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (900).png" alt=""><figcaption><p>Aggregate total for forecasts</p></figcaption></figure>
 
 **a) All Periods:** The grand total forecast will be the aggregate of the forecasts for open and closed periods.
 
-<figure><img src="../../.gitbook/assets/image (1).png" alt=""><figcaption><p>All periods aggregated forecast</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (1) (18).png" alt=""><figcaption><p>All periods aggregated forecast</p></figcaption></figure>
 
 **b) Open Periods:** The grand total forecast will be the aggregate of the forecasts for open periods only. The open periods in the example are 2025 Q1 and Q2, hence these will be used to calculate the grand total forecast.&#x20;
 
-<figure><img src="../../.gitbook/assets/image (2).png" alt=""><figcaption><p>Grand total aggregation for open periods</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (2) (18).png" alt=""><figcaption><p>Grand total aggregation for open periods</p></figcaption></figure>
 
 The subtotal forecasts for 2023 and 2024 go blank when the Open Period option is selected. This is because 2023 and 2024 only have closed periods.
 
 <figure><img src="../../.gitbook/assets/image (911).png" alt=""><figcaption><p>Closed forecast periods for 2024</p></figcaption></figure>
 
 **c) Closed Periods:** The grand total forecast will be the aggregate of the forecasts for closed periods only. In this example, the closed forecasts for 2023 and 2024 are used to calculate the grand total forecast. The subtotal forecast for 2025 is blank as 2025 only has open forecasts. The fields highlighted in red are the closed forecasts, and the field highlighted in green is the forecast grand total.
 
-<figure><img src="../../.gitbook/assets/image (900).png" alt=""><figcaption><p>Closed period aggregation for grand total forecast</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (900) (2).png" alt=""><figcaption><p>Closed period aggregation for grand total forecast</p></figcaption></figure>
 
 #### 3. Forecast subtotals
 

diff --git a/...th-inforiver/7.-planning-budgeting-and-forecasting/scenarios-enterprise-only.md b/...th-inforiver/7.-planning-budgeting-and-forecasting/scenarios-enterprise-only.md
@@ -158,13 +158,27 @@ On clicking on the Proceed button, the simulations in the scenario for 2023 Fore
 
 <figure><img src="../../.gitbook/assets/image (19) (2).png" alt=""><figcaption><p>Report with values set up in a scenario</p></figcaption></figure>
 
+You can also use the Copy to Base option in the toolbar to apply simulations to the base report.
+
+<figure><img src="../../.gitbook/assets/image (2).png" alt=""><figcaption><p>Copy to base option in the toolbar</p></figcaption></figure>
+
 ### 3.8. Edit/duplicate/delete
 
-To edit, delete, or duplicate a scenario - click on the additional options menu icon that appears on hovering over the name of the scenario and select the relevant option.
+To edit, delete, or duplicate a scenario, click on the additional options menu icon that appears when hovering over the name of the scenario and select the relevant option.
 
 <figure><img src="../../.gitbook/assets/image (893).png" alt=""><figcaption><p>Edit/duplicate/delete scenario</p></figcaption></figure>
 
-### 3.9. Style Formatting the Scenarios
+### 3.9. Set a default scenario
+
+When users open scenarios in reading mode, the Base scenario is always displayed by default. If you want a particular scenario to be loaded on initialization, choose the **Make as Default** option from the context menu.
+
+<figure><img src="../../.gitbook/assets/image (3).png" alt=""><figcaption><p>Make as default option</p></figcaption></figure>
+
+Scenario 1 will be opened by default in reading view when users navigate to scenarios. Default scenarios can be identified by the <img src="../../.gitbook/assets/image (922).png" alt="" data-size="line">icon.
+
+<figure><img src="../../.gitbook/assets/image (920).png" alt=""><figcaption><p>Default scenario in reading view</p></figcaption></figure>
+
+### 3.10. Style formatting scenarios
 
 You can manually format the newly created scenarios using the [cell and value formatting styles](../2.-displaying-information/basic-formatting/cell-and-value-formatting.md) or the [column styles](../8.-paginated-reporting/display-and-themes.md#iii-column-style) as well as copy the style from the Base or any other existing scenarios.
 
@@ -180,12 +194,14 @@ The image below shows _Scenario 1_ with the style format copied from the _Base_.
 
 <figure><img src="../../.gitbook/assets/image (6) (11).png" alt=""><figcaption><p>Scenario 1 with the Base Style format</p></figcaption></figure>
 
-### 3.10. Exiting scenarios
+### 3.11. Exiting scenario mode
 
-Click on the Close Scenario button to exit the scenario. You can re-visit the scenarios created by navigating to the Scenario ribbon.
+You will be able to use the other ribbons like the Home/Insert/Design/Export while working on a scenario. The simulations applied to a scenario will be visible even when you navigate to any of the other toolbar tabs.
 
-<figure><img src="../../.gitbook/assets/image (919).png" alt=""><figcaption><p>Close scenario</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image.png" alt=""><figcaption><p>Navigating to the Insert ribbon in scenario mode</p></figcaption></figure>
 
+Click on the Close Scenario button to exit scenario mode. You just need to navigate to the Scenario ribbon to re-visit the scenarios you created.
 
+<figure><img src="../../.gitbook/assets/image (1).png" alt=""><figcaption><p>Close scenario</p></figcaption></figure>
 
 In the next section, we'll look at [budgeting and allocations](../4.-adding-business-logic-and-formulae/budgeting-and-allocations.md).
diff --git a/working-with-inforiver/8.-paginated-reporting/header-and-footer.md b/working-with-inforiver/8.-paginated-reporting/header-and-footer.md
@@ -127,7 +127,7 @@ Use the **Insert** dropdown menu to add the predefined text elements listed belo
 
 <div>
 
-<figure><img src="../../.gitbook/assets/image (3) (1) (1).png" alt=""><figcaption><p>Types of elements</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1).png" alt=""><figcaption><p>Types of elements</p></figcaption></figure>
 
 
 
@@ -155,7 +155,7 @@ Before looking at creating header/footer elements from scratch, let's see how to
 
 If you choose a KPI preset, any selections made in the [KPI explorer](../3.-basic-interactions/explore-and-filter-data/explorer.md) will be reflected in the header as well.
 
-<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1).png" alt=""><figcaption><p>KPI explorer selection reflected in presets</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1).png" alt=""><figcaption><p>KPI explorer selection reflected in presets</p></figcaption></figure>
 
 ### 4.2. Footer preset
Original file line number	Diff line number	Diff line change
Expand Up		@@ -56,7 +56,7 @@ When you use icons, you have an additional option to align your icons in the gri

		<div>

		<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1).png" alt=""><figcaption><p>Aligning icons</p></figcaption></figure>
		<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Aligning icons</p></figcaption></figure>



Expand Down