GITBOOK-520: Replace containers and adding text elements

visualbis · Jul 31, 2024 · 2af7c02 · 2af7c02
1 parent baa9f4a
commit 2af7c02
Show file tree

Hide file tree

Showing 146 changed files with 129 additions and 88 deletions.
diff --git a/.gitbook/assets/2024-07-31_12h47_12.png b/.gitbook/assets/2024-07-31_12h47_12.png
diff --git a/.gitbook/assets/2024-07-31_12h59_02.png b/.gitbook/assets/2024-07-31_12h59_02.png
diff --git a/.gitbook/assets/2024-07-31_14h52_18.png b/.gitbook/assets/2024-07-31_14h52_18.png
diff --git a/...s/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1) (1) (1) (1).png b/...s/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/...ssets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1) (1) (1).png b/...ssets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1) (1) (1).png
diff --git a/...ok/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1) (1).png b/...ok/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (1) (1) (1) (1) (3).png b/.gitbook/assets/image (1) (1) (1) (1) (3).png
diff --git a/.gitbook/assets/image (1).png b/.gitbook/assets/image (1).png
diff --git a/.gitbook/assets/image (10) (9).png b/.gitbook/assets/image (10) (9).png
diff --git a/.gitbook/assets/image (10).png b/.gitbook/assets/image (10).png
diff --git a/.gitbook/assets/image (11) (10).png b/.gitbook/assets/image (11) (10).png
diff --git a/.gitbook/assets/image (11).png b/.gitbook/assets/image (11).png
diff --git a/.gitbook/assets/image (12) (6).png b/.gitbook/assets/image (12) (6).png
diff --git a/.gitbook/assets/image (12).png b/.gitbook/assets/image (12).png
diff --git a/.gitbook/assets/image (13) (7).png b/.gitbook/assets/image (13) (7).png
diff --git a/.gitbook/assets/image (13).png b/.gitbook/assets/image (13).png
diff --git a/.gitbook/assets/image (14) (6).png b/.gitbook/assets/image (14) (6).png
diff --git a/.gitbook/assets/image (14).png b/.gitbook/assets/image (14).png
diff --git a/.gitbook/assets/image (15) (7).png b/.gitbook/assets/image (15) (7).png
diff --git a/.gitbook/assets/image (15).png b/.gitbook/assets/image (15).png
diff --git a/.gitbook/assets/image (16) (7).png b/.gitbook/assets/image (16) (7).png
diff --git a/.gitbook/assets/image (16).png b/.gitbook/assets/image (16).png
diff --git a/.gitbook/assets/image (17) (8).png b/.gitbook/assets/image (17) (8).png
diff --git a/.gitbook/assets/image (17).png b/.gitbook/assets/image (17).png
diff --git a/.gitbook/assets/image (18) (5).png b/.gitbook/assets/image (18) (5).png
diff --git a/.gitbook/assets/image (18).png b/.gitbook/assets/image (18).png
diff --git a/.gitbook/assets/image (19) (6).png b/.gitbook/assets/image (19) (6).png
diff --git a/.gitbook/assets/image (19).png b/.gitbook/assets/image (19).png
diff --git a/.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1) (1) (1) (1).png b/.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1) (1) (1).png b/.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1) (1) (1).png
diff --git a/.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1) (1).png b/.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1) (1).png
diff --git a/.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1).png b/.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1).png
diff --git a/.gitbook/assets/image (2) (1) (1) (1) (1) (2).png b/.gitbook/assets/image (2) (1) (1) (1) (1) (2).png
diff --git a/.gitbook/assets/image (2) (1) (1) (1) (1).png b/.gitbook/assets/image (2) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (2) (1) (1) (1).png b/.gitbook/assets/image (2) (1) (1) (1).png
diff --git a/.gitbook/assets/image (2) (1) (1).png b/.gitbook/assets/image (2) (1) (1).png
diff --git a/.gitbook/assets/image (2) (1) (5).png b/.gitbook/assets/image (2) (1) (5).png
diff --git a/.gitbook/assets/image (2).png b/.gitbook/assets/image (2).png
diff --git a/.gitbook/assets/image (20) (3).png b/.gitbook/assets/image (20) (3).png
diff --git a/.gitbook/assets/image (20).png b/.gitbook/assets/image (20).png
diff --git a/.gitbook/assets/image (21) (3).png b/.gitbook/assets/image (21) (3).png
diff --git a/.gitbook/assets/image (21).png b/.gitbook/assets/image (21).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) (5).png b/.gitbook/assets/image (3) (1) (5).png
diff --git a/.gitbook/assets/image (3).png b/.gitbook/assets/image (3).png
diff --git a/.gitbook/assets/image (4) (1) (1) (2) (1) (1).png b/.gitbook/assets/image (4) (1) (1) (2) (1) (1).png
diff --git a/.gitbook/assets/image (4) (1) (1) (2) (1).png b/.gitbook/assets/image (4) (1) (1) (2) (1).png
diff --git a/.gitbook/assets/image (4) (1) (1) (2).png b/.gitbook/assets/image (4) (1) (1) (2).png
diff --git a/.gitbook/assets/image (4) (1) (1).png b/.gitbook/assets/image (4) (1) (1).png
diff --git a/.gitbook/assets/image (4) (1).png b/.gitbook/assets/image (4) (1).png
diff --git a/.gitbook/assets/image (4) (11).png b/.gitbook/assets/image (4) (11).png
diff --git a/.gitbook/assets/image (4).png b/.gitbook/assets/image (4).png
diff --git a/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (5) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (5) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (5) (1) (1) (1) (1).png b/.gitbook/assets/image (5) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/image (5) (1) (1) (1).png b/.gitbook/assets/image (5) (1) (1) (1).png
diff --git a/.gitbook/assets/image (5) (1) (1).png b/.gitbook/assets/image (5) (1) (1).png
diff --git a/.gitbook/assets/image (5) (1).png b/.gitbook/assets/image (5) (1).png
diff --git a/.gitbook/assets/image (5) (13).png b/.gitbook/assets/image (5) (13).png
diff --git a/.gitbook/assets/image (5).png b/.gitbook/assets/image (5).png
diff --git a/.gitbook/assets/image (6) (14).png b/.gitbook/assets/image (6) (14).png
diff --git a/.gitbook/assets/image (6).png b/.gitbook/assets/image (6).png
diff --git a/.gitbook/assets/image (7) (13).png b/.gitbook/assets/image (7) (13).png
diff --git a/.gitbook/assets/image (7).png b/.gitbook/assets/image (7).png
diff --git a/.gitbook/assets/image (8) (12).png b/.gitbook/assets/image (8) (12).png
diff --git a/.gitbook/assets/image (8).png b/.gitbook/assets/image (8).png
diff --git a/.gitbook/assets/image (857).png b/.gitbook/assets/image (857).png
diff --git a/.gitbook/assets/image (858).png b/.gitbook/assets/image (858).png
diff --git a/.gitbook/assets/image (859).png b/.gitbook/assets/image (859).png
diff --git a/.gitbook/assets/image (860).png b/.gitbook/assets/image (860).png
diff --git a/.gitbook/assets/image (861).png b/.gitbook/assets/image (861).png
diff --git a/.gitbook/assets/image (862).png b/.gitbook/assets/image (862).png
diff --git a/.gitbook/assets/image (863).png b/.gitbook/assets/image (863).png
diff --git a/.gitbook/assets/image (864).png b/.gitbook/assets/image (864).png
diff --git a/.gitbook/assets/image (865).png b/.gitbook/assets/image (865).png
diff --git a/.gitbook/assets/image (866).png b/.gitbook/assets/image (866).png
diff --git a/.gitbook/assets/image (867).png b/.gitbook/assets/image (867).png
diff --git a/.gitbook/assets/image (868).png b/.gitbook/assets/image (868).png
diff --git a/.gitbook/assets/image (869).png b/.gitbook/assets/image (869).png
diff --git a/.gitbook/assets/image (870).png b/.gitbook/assets/image (870).png
diff --git a/.gitbook/assets/image (871).png b/.gitbook/assets/image (871).png
diff --git a/.gitbook/assets/image (872).png b/.gitbook/assets/image (872).png
diff --git a/.gitbook/assets/image (873).png b/.gitbook/assets/image (873).png
diff --git a/.gitbook/assets/image (874).png b/.gitbook/assets/image (874).png
diff --git a/.gitbook/assets/image (875).png b/.gitbook/assets/image (875).png
diff --git a/.gitbook/assets/image (876).png b/.gitbook/assets/image (876).png
diff --git a/.gitbook/assets/image (877).png b/.gitbook/assets/image (877).png
diff --git a/.gitbook/assets/image (9) (10).png b/.gitbook/assets/image (9) (10).png
diff --git a/.gitbook/assets/image (9).png b/.gitbook/assets/image (9).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,13 +30,13 @@ 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).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).png" alt=""><figcaption><p>Connection created</p></figcaption></figure>
 
 ### ii) Edit/Delete connection
 
 You can edit the available connections using the edit icon(pencil) available on the top right corner of each connection.
 
-<figure><img src="../../.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Edit connection</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Edit connection</p></figcaption></figure>
 
 Clicking the pencil icon will open the 'Edit connection' page where you can edit or make changes to the connection.
 

diff --git a/display-settings/general-settings.md b/display-settings/general-settings.md
@@ -95,7 +95,7 @@ You can remove the row highlight by selecting the 'off' option from the drop-dow
 
 Enable the _**Measure Only Highlight**_ option to remove the highlight from the categories and highlight just the measures.
 
-<figure><img src="../.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Row highlight is applied only to measures</p></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Row highlight is applied only to measures</p></figcaption></figure>
 
 ### 5. Gridlines
 

diff --git a/display-settings/hierarchy-settings.md b/display-settings/hierarchy-settings.md
@@ -34,7 +34,7 @@ You can add non-numeric measures like dates and text fields and display them in
 
 <div>
 
-<figure><img src="../.gitbook/assets/image (4) (1) (1).png" alt=""><figcaption><p>Non-numeric fields displayed as totals/subtotals</p></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (4) (1) (1) (2).png" alt=""><figcaption><p>Non-numeric fields displayed as totals/subtotals</p></figcaption></figure>
 
 
 

diff --git a/formula-syntax/time-intelligence-functions/column_period.md b/formula-syntax/time-intelligence-functions/column_period.md
@@ -28,7 +28,7 @@ COLUMN_PERIOD.START
 
 <div>
 
-<figure><img src="../../.gitbook/assets/image (2) (1) (1) (1) (1).png" alt=""><figcaption><p>Month level</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (2) (1) (1) (1) (1) (2).png" alt=""><figcaption><p>Month level</p></figcaption></figure>
 
 
 

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).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).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).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).png" alt=""><figcaption><p>NEXTNQTR</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>NEXTNQTR</p></figcaption></figure>
diff --git a/formula-syntax/time-intelligence-functions/nextnyear.md b/formula-syntax/time-intelligence-functions/nextnyear.md
@@ -23,4 +23,4 @@ NEXTNYEAR(2)
 //Returns data for 2 years after the current one
 ```
 
-<figure><img src="../../.gitbook/assets/image (5) (1) (1) (1).png" alt=""><figcaption><p>NEXTNYEAR</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (5) (1) (1) (1) (1).png" alt=""><figcaption><p>NEXTNYEAR</p></figcaption></figure>
diff --git a/formula-syntax/time-intelligence-functions/yearperiod.md b/formula-syntax/time-intelligence-functions/yearperiod.md
@@ -27,6 +27,6 @@ YEARPERIOD(2023)
 //Returns data from 2023
 ```
 
-<figure><img src="../../.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Yearperiod without offset</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Yearperiod without offset</p></figcaption></figure>
 
 <figure><img src="../../.gitbook/assets/image (6) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Yearperiod with offset</p></figcaption></figure>
diff --git a/...et-started/inforiver-writeback-matrix-pre-requisites/whitelist-inforiver-ips.md b/...et-started/inforiver-writeback-matrix-pre-requisites/whitelist-inforiver-ips.md
@@ -26,4 +26,4 @@ Follow the steps in the image below to whitelist the 5 Inforiver outbound IP add
 
 The screengrab below shows the firewall rules configured for Inforiver would.
 
-<figure><img src="../../../.gitbook/assets/image (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Firewall rules configured for Inforiver</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/image (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Firewall rules configured for Inforiver</p></figcaption></figure>
diff --git a/introduction-to-inforiver/why-inforiver.md b/introduction-to-inforiver/why-inforiver.md
@@ -13,7 +13,7 @@ Inforiver for Power BI helps you retire legacy tools and deliver all analytics n
 * Avoid spending on add-ons for PowerPoint reports such as ThinkCell and Mekko Graphics
 * Eliminate Excel-based worksheets used for maintaining forecasts, budgets, master data, pivot reports, and more
 
-<figure><img src="../.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 ### 2. End-to-end Security and Governance
 
@@ -23,7 +23,7 @@ Inforiver visuals are [certified](https://learn.microsoft.com/en-us/power-bi/dev
 2. Inforiver-level security - e.g., administrators can decide whether Inforiver users can write to Snowflake
 3. Report-level security - e.g., report creators can authorize specific users to perform specific actions in the report, such as who can comment, enter data, create scenarios, etc.
 
-<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 ### 3. Built for business users with no coding experience
 
@@ -37,7 +37,7 @@ You can create the following without writing a single line of code:
 * Data writeback&#x20;
 * ... and more
 
-<figure><img src="../.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 ### 4. Get features 'highly voted' by industry peers
 
@@ -58,7 +58,7 @@ Using Inforiver, you can implement key features available in other BI tools but
 5. Lasso and reverse lasso selections like Qlik and Tableau
 6. Small-multiple tables with Excel-like formatting 
 
-<figure><img src="../.gitbook/assets/image (4) (1) (1) (2) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (4) (1) (1) (2) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 ### 6. The best no-code writeback in the industry
 

diff --git a/...er/11.-scheduling-reports/create-new-subscription/set-subscription-frequency.md b/...er/11.-scheduling-reports/create-new-subscription/set-subscription-frequency.md
@@ -38,7 +38,7 @@ This option lets you select the starting and ending date of the schedule using a
 
 You can skip subscription jobs based on a specific holiday calendar. Choose a predefined holiday calendar from the dropdown. [Learn more about setting up holiday calendars in the admin console.](../../../admin-console/settings/holidays.md)
 
-<figure><img src="../../../.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 ## 3. Scheduled time&#x20;
 

diff --git a/working-with-inforiver/12.-data-writeback/destinations/databricks.md b/working-with-inforiver/12.-data-writeback/destinations/databricks.md
@@ -17,4 +17,4 @@ When you get to the 'Add Destination' page, you have the option of using basic o
 
 You can also use OAuth-type authentication to log in that ensures a simple and secure login process. The example below illustrates adding a Databricks destination to an existing integration using OAuth-type authentication.
 
-<figure><img src="../../../.gitbook/assets/image (1).png" alt=""><figcaption><p>OAuth type authentication for Databricks destination</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/image (858).png" alt=""><figcaption><p>OAuth type authentication for Databricks destination</p></figcaption></figure>
diff --git a/working-with-inforiver/12.-data-writeback/settings/general-settings.md b/working-with-inforiver/12.-data-writeback/settings/general-settings.md
@@ -209,11 +209,11 @@ The above are sample workflows that could be triggered using the Inforiver webho
 
 You can specify the number of digits after the decimal point to be written back. This is a **one-time setup** that will apply to **all destinations** configured for a particular report page. While configuring the first writeback destination, you will see a pop-up as shown below, to configure the decimal precision.&#x20;
 
-<figure><img src="../../../.gitbook/assets/image (4).png" alt=""><figcaption><p>Configuring decimal precision</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/image (861).png" alt=""><figcaption><p>Configuring decimal precision</p></figcaption></figure>
 
 If you require high precision, you can configure Inforiver to write back numerical data with up to ten decimal digits. Any digits beyond 10 will be rounded off.
 
-<figure><img src="../../../.gitbook/assets/image (5).png" alt=""><figcaption><p>10-digit decimal precision</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/image (862).png" alt=""><figcaption><p>10-digit decimal precision</p></figcaption></figure>
 
 The precision that is set in the destination configuration is displayed in the Decimal Precision section. [Learn more about configuring writeback destinations](../destinations/).
 
@@ -223,7 +223,7 @@ The precision that is set in the destination configuration is displayed in the D
 
 You can restrict the length of text fields to be written back. The default text length allowed in writeback  is 512 characters. While adding the first destination, along with [decimal precision](general-settings.md#id-6.-decimal-precision), you can also restrict the length of text fields to 512 characters or allow writeback up to the maximum limit supported by the backend. This is also a **one-time setup** that will apply to **all destinations** configured for a particular report page. [Learn more about configuring writeback destinations here](../destinations/).
 
-<figure><img src="../../../.gitbook/assets/image (6).png" alt=""><figcaption><p>Configuring text field length</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/image (863).png" alt=""><figcaption><p>Configuring text field length</p></figcaption></figure>
 
 The text length that has been set is shown in the Text Length section of the report as below. Note that, if you have restricted the text length and the length exceeds that limit, writeback will fail.
 

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).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).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.
 
@@ -26,7 +26,7 @@ Consider that you have set up filter context for 2 dimensions E.g. Sub Region an
 
 **Step 4**: Create a new measure in your data model using the DAX generated in Step 3.
 
-<figure><img src="../.gitbook/assets/image (5) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Create new measure</p></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (5) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Create new measure</p></figcaption></figure>
 
 **Step 5**: Add the new measure to the Others (OM) visual parameter. It gets displayed in the report as well.
 
@@ -66,7 +66,7 @@ The filter selections are captured in the writeback table as separate columns. I
 
 When the Segment and Region selection is changed to Corporate + Central, the notes and comments are inserted as separate rows in the snowflake destination and tagged against the changed categories.
 
-<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Writeback for Corporate + Central selection</p></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Writeback for Corporate + Central selection</p></figcaption></figure>
 
 ### 3. Context awareness for data input fields
 
@@ -82,8 +82,8 @@ When working with context awareness, you need to select a category(ies) in the e
 
 The data input cells that are written back will also be determined based on filter selections.  In the screenshot below, the report has 3 data input columns: Benchmark, Progress, and Status. Notice how the data input fields were written back to the snowflake destination for the Consumer + January + First Class selection.
 
-<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1).png" alt=""><figcaption><p>Writeback for data input columns based on external filter selection</p></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1).png" alt=""><figcaption><p>Writeback for data input columns based on external filter selection</p></figcaption></figure>
 
 When the selection is changed to Home Office + October + Standard Class, the data inputs corresponding to the selection are written back as shown below. The data input fields for each filter selection are captured as separate rows in the destination.
 
-<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1).png" alt=""><figcaption><p>Writeback for data input fields after changing the selection</p></figcaption></figure>
+<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Writeback for data input fields after changing the selection</p></figcaption></figure>
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).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).png" alt=""><figcaption></figcaption></figure>
 
 3. Click on the **Create** button in the Report Details side pane to detach the visual.
 

diff --git a/...th-inforiver/3.-basic-interactions/explore-and-filter-data/search-and-filter.md b/...th-inforiver/3.-basic-interactions/explore-and-filter-data/search-and-filter.md
@@ -78,7 +78,7 @@ Inforiver filters can detect manually inserted row categories and calculated row
 
 In the example below, the _HighTouch_ and _Vsense_ rows are manual input rows created within the Inforiver visual. Notice how even manual input row categories are detected by the filter.
 
-<figure><img src="../../../.gitbook/assets/image (1) (1) (1) (1) (3).png" alt=""><figcaption><p>Filtering manual input row categories</p></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/image (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Filtering manual input row categories</p></figcaption></figure>
 
 ### 2.2. Column-level filter
 

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).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).png" alt=""><figcaption><p>Image URL data category</p></figcaption></figure>
 
 * **Cell-level images**
 

diff --git a/...river/4.-adding-business-logic-and-formulae/manage-inserted-rows-and-columns.md b/...river/4.-adding-business-logic-and-formulae/manage-inserted-rows-and-columns.md
@@ -50,7 +50,7 @@ Access control for all the columns can also be set through the **Manage Columns*
 
 When you have a date hierarchy in your rows/columns, you can use the time interval mapping to verify the formats that Inforiver auto-detects. Hover over the<img src="../../.gitbook/assets/image (1) (1) (1).png" alt="" data-size="line">icon to view all the supported date formats.
 
-<figure><img src="../../.gitbook/assets/image (2) (1) (5).png" alt=""><figcaption><p>Supported date formats</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (2) (1) (1).png" alt=""><figcaption><p>Supported date formats</p></figcaption></figure>
 
 You can also choose whether to use Power BI sorting or Inforiver sorting. When the **Sort** toggle is enabled, any sorting changes made at Power BI level will not be reflected in the visual. In the example, notice how the Power BI sorting is not applied on the Quarter when the Sort toggle is enabled.
 
@@ -64,7 +64,7 @@ When row dimensions are renamed/changed, we might lose these visual elements add
 
 In the example below, we’ve applied formatting, added notes, and comments, and added data inputs to the products, _Juices_ and _Tea & Coffee_.
 
-<figure><img src="../../.gitbook/assets/image (2) (1) (1) (1) (1) (2).png" alt=""><figcaption><p>Sample report with formatting, comments and data input columns</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (2) (1) (1) (1) (1) (2) (1).png" alt=""><figcaption><p>Sample report with formatting, comments and data input columns</p></figcaption></figure>
 
 The visual elements were lost after the product names were renamed to _Fruit Juices_ and _Chai & Coffee_ respectively.
 
@@ -76,7 +76,7 @@ To avoid this, let us map the dimension IDs to a constant dimension, such as the
 
 The image below shows the default row dimension ID mapping.&#x20;
 
-<figure><img src="../../.gitbook/assets/image (4) (1) (1) (2).png" alt=""><figcaption><p>Default row ID mapping</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (4) (1) (1) (2) (1).png" alt=""><figcaption><p>Default row ID mapping</p></figcaption></figure>
 
 Let us map the 'Product Name' to the constant dimension, 'Product ID' as shown below. Click **Apply**.
 

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) (5).png" alt=""><figcaption><p>Aligning icons</p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (3) (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).png" alt=""><figcaption><p>Click <strong>Outliers</strong></p></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (3) (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**.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -34,7 +34,7 @@ You can add non-numeric measures like dates and text fields and display them in

		<div>

		<figure><img src="../.gitbook/assets/image (4) (1) (1).png" alt=""><figcaption><p>Non-numeric fields displayed as totals/subtotals</p></figcaption></figure>
		<figure><img src="../.gitbook/assets/image (4) (1) (1) (2).png" alt=""><figcaption><p>Non-numeric fields displayed as totals/subtotals</p></figcaption></figure>



Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -28,7 +28,7 @@ COLUMN_PERIOD.START

		<div>

		<figure><img src="../../.gitbook/assets/image (2) (1) (1) (1) (1).png" alt=""><figcaption><p>Month level</p></figcaption></figure>
		<figure><img src="../../.gitbook/assets/image (2) (1) (1) (1) (1) (2).png" alt=""><figcaption><p>Month level</p></figcaption></figure>



Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -26,4 +26,4 @@ Follow the steps in the image below to whitelist the 5 Inforiver outbound IP add

		The screengrab below shows the firewall rules configured for Inforiver would.

		<figure><img src="../../../.gitbook/assets/image (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Firewall rules configured for Inforiver</p></figcaption></figure>
		<figure><img src="../../../.gitbook/assets/image (1) (1) (1) (1) (1) (1).png" alt=""><figcaption><p>Firewall rules configured for Inforiver</p></figcaption></figure>
Original file line number	Diff line number	Diff line change
Expand Up		@@ -17,4 +17,4 @@ When you get to the 'Add Destination' page, you have the option of using basic o

		You can also use OAuth-type authentication to log in that ensures a simple and secure login process. The example below illustrates adding a Databricks destination to an existing integration using OAuth-type authentication.

		<figure><img src="../../../.gitbook/assets/image (1).png" alt=""><figcaption><p>OAuth type authentication for Databricks destination</p></figcaption></figure>
		<figure><img src="../../../.gitbook/assets/image (858).png" alt=""><figcaption><p>OAuth type authentication for Databricks destination</p></figcaption></figure>
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) (5).png" alt=""><figcaption><p>Aligning icons</p></figcaption></figure>
		<figure><img src="../../.gitbook/assets/image (3) (1) (1).png" alt=""><figcaption><p>Aligning icons</p></figcaption></figure>



Expand Down