diff --git a/.gitbook/assets/WB Text field length - 1.png b/.gitbook/assets/WB Text field length - 1.png new file mode 100644 index 00000000..099b877f Binary files /dev/null and b/.gitbook/assets/WB Text field length - 1.png differ diff --git a/.gitbook/assets/WB Text field length - 2.png b/.gitbook/assets/WB Text field length - 2.png new file mode 100644 index 00000000..ac827582 Binary files /dev/null and b/.gitbook/assets/WB Text field length - 2.png differ diff --git a/.gitbook/assets/image (1) (1) (1) (1) (3).png b/.gitbook/assets/image (1) (1) (1) (1) (3).png new file mode 100644 index 00000000..37e03e34 Binary files /dev/null and b/.gitbook/assets/image (1) (1) (1) (1) (3).png differ diff --git a/.gitbook/assets/image (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1).png index 37e03e34..a49f0787 100644 Binary files a/.gitbook/assets/image (1) (1) (1).png and b/.gitbook/assets/image (1) (1) (1).png differ diff --git a/.gitbook/assets/image (1) (1).png b/.gitbook/assets/image (1) (1).png index a49f0787..14b2a3ab 100644 Binary files a/.gitbook/assets/image (1) (1).png and b/.gitbook/assets/image (1) (1).png differ diff --git a/.gitbook/assets/image (1).png b/.gitbook/assets/image (1).png index 14b2a3ab..b2b97fa8 100644 Binary files a/.gitbook/assets/image (1).png and b/.gitbook/assets/image (1).png differ diff --git a/.gitbook/assets/image (10) (9).png b/.gitbook/assets/image (10) (9).png new file mode 100644 index 00000000..f705ff16 Binary files /dev/null and b/.gitbook/assets/image (10) (9).png differ diff --git a/.gitbook/assets/image (10).png b/.gitbook/assets/image (10).png index f705ff16..42490e0c 100644 Binary files a/.gitbook/assets/image (10).png and b/.gitbook/assets/image (10).png differ diff --git a/.gitbook/assets/image (11) (10).png b/.gitbook/assets/image (11) (10).png new file mode 100644 index 00000000..bd4643c3 Binary files /dev/null and b/.gitbook/assets/image (11) (10).png differ diff --git a/.gitbook/assets/image (11).png b/.gitbook/assets/image (11).png index bd4643c3..f85c5fd1 100644 Binary files a/.gitbook/assets/image (11).png and b/.gitbook/assets/image (11).png differ diff --git a/.gitbook/assets/image (12) (6).png b/.gitbook/assets/image (12) (6).png new file mode 100644 index 00000000..3b0d9427 Binary files /dev/null and b/.gitbook/assets/image (12) (6).png differ diff --git a/.gitbook/assets/image (12).png b/.gitbook/assets/image (12).png index 3b0d9427..88272d01 100644 Binary files a/.gitbook/assets/image (12).png and b/.gitbook/assets/image (12).png differ diff --git a/.gitbook/assets/image (13) (7).png b/.gitbook/assets/image (13) (7).png new file mode 100644 index 00000000..64dbdebd Binary files /dev/null and b/.gitbook/assets/image (13) (7).png differ diff --git a/.gitbook/assets/image (13).png b/.gitbook/assets/image (13).png index 64dbdebd..9dc8831e 100644 Binary files a/.gitbook/assets/image (13).png and b/.gitbook/assets/image (13).png differ diff --git a/.gitbook/assets/image (14) (6).png b/.gitbook/assets/image (14) (6).png new file mode 100644 index 00000000..ec77efdb Binary files /dev/null and b/.gitbook/assets/image (14) (6).png differ diff --git a/.gitbook/assets/image (14).png b/.gitbook/assets/image (14).png index ec77efdb..74f1cffc 100644 Binary files a/.gitbook/assets/image (14).png and b/.gitbook/assets/image (14).png differ diff --git a/.gitbook/assets/image (15) (7).png b/.gitbook/assets/image (15) (7).png new file mode 100644 index 00000000..a1ca5ba8 Binary files /dev/null and b/.gitbook/assets/image (15) (7).png differ diff --git a/.gitbook/assets/image (15).png b/.gitbook/assets/image (15).png index a1ca5ba8..627feb50 100644 Binary files a/.gitbook/assets/image (15).png and b/.gitbook/assets/image (15).png differ diff --git a/.gitbook/assets/image (16) (7).png b/.gitbook/assets/image (16) (7).png new file mode 100644 index 00000000..62e7f23c Binary files /dev/null and b/.gitbook/assets/image (16) (7).png differ diff --git a/.gitbook/assets/image (16).png b/.gitbook/assets/image (16).png index 62e7f23c..4134b4f5 100644 Binary files a/.gitbook/assets/image (16).png and b/.gitbook/assets/image (16).png differ diff --git a/.gitbook/assets/image (17) (8).png b/.gitbook/assets/image (17) (8).png new file mode 100644 index 00000000..4e1da535 Binary files /dev/null and b/.gitbook/assets/image (17) (8).png differ diff --git a/.gitbook/assets/image (17).png b/.gitbook/assets/image (17).png index 4e1da535..f697a3b8 100644 Binary files a/.gitbook/assets/image (17).png and b/.gitbook/assets/image (17).png differ diff --git a/.gitbook/assets/image (18) (5).png b/.gitbook/assets/image (18) (5).png new file mode 100644 index 00000000..845a4025 Binary files /dev/null and b/.gitbook/assets/image (18) (5).png differ diff --git a/.gitbook/assets/image (18).png b/.gitbook/assets/image (18).png index 845a4025..43e1a1d8 100644 Binary files a/.gitbook/assets/image (18).png and b/.gitbook/assets/image (18).png differ diff --git a/.gitbook/assets/image (19) (6).png b/.gitbook/assets/image (19) (6).png new file mode 100644 index 00000000..20e23576 Binary files /dev/null and b/.gitbook/assets/image (19) (6).png differ diff --git a/.gitbook/assets/image (19).png b/.gitbook/assets/image (19).png index 20e23576..43e1a1d8 100644 Binary files a/.gitbook/assets/image (19).png and b/.gitbook/assets/image (19).png differ diff --git a/.gitbook/assets/image (2) (1) (5).png b/.gitbook/assets/image (2) (1) (5).png new file mode 100644 index 00000000..238f2d43 Binary files /dev/null and b/.gitbook/assets/image (2) (1) (5).png differ diff --git a/.gitbook/assets/image (2) (1).png b/.gitbook/assets/image (2) (1).png index 238f2d43..de4a30f5 100644 Binary files a/.gitbook/assets/image (2) (1).png and b/.gitbook/assets/image (2) (1).png differ diff --git a/.gitbook/assets/image (2).png b/.gitbook/assets/image (2).png index de4a30f5..72c619f4 100644 Binary files a/.gitbook/assets/image (2).png and b/.gitbook/assets/image (2).png differ diff --git a/.gitbook/assets/image (20) (3).png b/.gitbook/assets/image (20) (3).png new file mode 100644 index 00000000..43664698 Binary files /dev/null and b/.gitbook/assets/image (20) (3).png differ diff --git a/.gitbook/assets/image (20).png b/.gitbook/assets/image (20).png index 43664698..3ba53734 100644 Binary files a/.gitbook/assets/image (20).png and b/.gitbook/assets/image (20).png differ diff --git a/.gitbook/assets/image (21) (3).png b/.gitbook/assets/image (21) (3).png new file mode 100644 index 00000000..c3d86ea2 Binary files /dev/null and b/.gitbook/assets/image (21) (3).png differ diff --git a/.gitbook/assets/image (21).png b/.gitbook/assets/image (21).png index c3d86ea2..30f97322 100644 Binary files a/.gitbook/assets/image (21).png and b/.gitbook/assets/image (21).png differ diff --git a/.gitbook/assets/image (3) (1) (5).png b/.gitbook/assets/image (3) (1) (5).png new file mode 100644 index 00000000..500bec44 Binary files /dev/null and b/.gitbook/assets/image (3) (1) (5).png differ diff --git a/.gitbook/assets/image (3) (1).png b/.gitbook/assets/image (3) (1).png index 500bec44..781da062 100644 Binary files a/.gitbook/assets/image (3) (1).png and b/.gitbook/assets/image (3) (1).png differ diff --git a/.gitbook/assets/image (3).png b/.gitbook/assets/image (3).png index 781da062..2b3a2b6c 100644 Binary files a/.gitbook/assets/image (3).png and b/.gitbook/assets/image (3).png differ diff --git a/.gitbook/assets/image (4) (11).png b/.gitbook/assets/image (4) (11).png new file mode 100644 index 00000000..7ebbf571 Binary files /dev/null and b/.gitbook/assets/image (4) (11).png differ diff --git a/.gitbook/assets/image (4).png b/.gitbook/assets/image (4).png index 7ebbf571..db41df17 100644 Binary files a/.gitbook/assets/image (4).png and b/.gitbook/assets/image (4).png differ diff --git a/.gitbook/assets/image (5) (13).png b/.gitbook/assets/image (5) (13).png new file mode 100644 index 00000000..7b890433 Binary files /dev/null and b/.gitbook/assets/image (5) (13).png differ diff --git a/.gitbook/assets/image (5).png b/.gitbook/assets/image (5).png index 7b890433..f81f5596 100644 Binary files a/.gitbook/assets/image (5).png and b/.gitbook/assets/image (5).png differ diff --git a/.gitbook/assets/image (6) (14).png b/.gitbook/assets/image (6) (14).png new file mode 100644 index 00000000..9d3ec718 Binary files /dev/null and b/.gitbook/assets/image (6) (14).png differ diff --git a/.gitbook/assets/image (6).png b/.gitbook/assets/image (6).png index 9d3ec718..8bd5a20c 100644 Binary files a/.gitbook/assets/image (6).png and b/.gitbook/assets/image (6).png differ diff --git a/.gitbook/assets/image (7) (13).png b/.gitbook/assets/image (7) (13).png new file mode 100644 index 00000000..461f8fec Binary files /dev/null and b/.gitbook/assets/image (7) (13).png differ diff --git a/.gitbook/assets/image (7).png b/.gitbook/assets/image (7).png index 461f8fec..8f3f7d85 100644 Binary files a/.gitbook/assets/image (7).png and b/.gitbook/assets/image (7).png differ diff --git a/.gitbook/assets/image (8) (12).png b/.gitbook/assets/image (8) (12).png new file mode 100644 index 00000000..e7624e70 Binary files /dev/null and b/.gitbook/assets/image (8) (12).png differ diff --git a/.gitbook/assets/image (8).png b/.gitbook/assets/image (8).png index e7624e70..6d8d4078 100644 Binary files a/.gitbook/assets/image (8).png and b/.gitbook/assets/image (8).png differ diff --git a/.gitbook/assets/image (9) (10).png b/.gitbook/assets/image (9) (10).png new file mode 100644 index 00000000..f4466f6b Binary files /dev/null and b/.gitbook/assets/image (9) (10).png differ diff --git a/.gitbook/assets/image (9).png b/.gitbook/assets/image (9).png index f4466f6b..94487e4d 100644 Binary files a/.gitbook/assets/image (9).png and b/.gitbook/assets/image (9).png differ diff --git a/.gitbook/assets/image.png b/.gitbook/assets/image.png index 30f97322..a8aa35f1 100644 Binary files a/.gitbook/assets/image.png and b/.gitbook/assets/image.png differ diff --git a/.gitbook/assets/ten digit decimal precision.png b/.gitbook/assets/ten digit decimal precision.png new file mode 100644 index 00000000..07e10ab2 Binary files /dev/null and b/.gitbook/assets/ten digit decimal precision.png differ diff --git a/SUMMARY.md b/SUMMARY.md index 3bb6b4db..633ad432 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -111,6 +111,7 @@ * [Data-level comments](working-with-inforiver/8.-commenting-and-collaboration/comments/comments.md) * [Assign & track tasks](working-with-inforiver/8.-commenting-and-collaboration/comments/comments-1.md) * [Track changes](working-with-inforiver/8.-commenting-and-collaboration/comments/track-changes.md) + * [Report-level comments](working-with-inforiver/8.-commenting-and-collaboration/comments/report-level-comments.md) * [Comment settings](working-with-inforiver/8.-commenting-and-collaboration/comments/comment-settings.md) * [10. Exporting reports](working-with-inforiver/10.-exporting-reports/README.md) * [Export to PDF & Excel](working-with-inforiver/10.-exporting-reports/export.md) diff --git a/working-with-inforiver/12.-data-writeback/destinations/databricks.md b/working-with-inforiver/12.-data-writeback/destinations/databricks.md index 82a0b6c8..737a8dad 100644 --- a/working-with-inforiver/12.-data-writeback/destinations/databricks.md +++ b/working-with-inforiver/12.-data-writeback/destinations/databricks.md @@ -2,7 +2,7 @@ Allows you to configure Databricks as a destination for Inforiver writeback. -After navigating to the add destination page, the following details will have to be entered. +When you get to the 'Add Destination' page, you have the option of using basic or OAuth authentication. If you choose basic authentication, you will need to enter the following information: * Host Name * Warehouse ID @@ -14,3 +14,7 @@ After navigating to the add destination page, the following details will have to + +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. + + diff --git a/working-with-inforiver/12.-data-writeback/destinations/snowflake.md b/working-with-inforiver/12.-data-writeback/destinations/snowflake.md index ba6052e6..d6207077 100644 --- a/working-with-inforiver/12.-data-writeback/destinations/snowflake.md +++ b/working-with-inforiver/12.-data-writeback/destinations/snowflake.md @@ -18,7 +18,7 @@ After navigating to the add destination page, the following details must be ente -You can also use OAuth-type authentication to log in, to ensure a simple and secure login process. The example below illustrates adding a Snowflake destination to an existing integration using OAuth-type authentication. +You can also use **OAuth**-type authentication to log in that ensures a simple and secure login process. The example below illustrates adding a Snowflake destination to an existing integration using OAuth-type authentication. diff --git a/working-with-inforiver/12.-data-writeback/settings/general-settings.md b/working-with-inforiver/12.-data-writeback/settings/general-settings.md index 501ca4df..06fcd8f2 100644 --- a/working-with-inforiver/12.-data-writeback/settings/general-settings.md +++ b/working-with-inforiver/12.-data-writeback/settings/general-settings.md @@ -92,7 +92,7 @@ The **Custom Filter** configuration window has the following options: If you have set up Matrix filters as well as writeback filters, the writeback filter will always take precedence. {% endhint %} -### iii) Additional column configuration +### 3. Additional column configuration This allows a user to add dimension keys to the writeback table during writeback. This will require the user to provide consent to access all the datasets from the workspace. @@ -132,7 +132,7 @@ Inforiver reports are often used for high-level aggregations such as Revenue by * If a high-level dimension category is included in the visual and additional column mapping is chosen, Inforiver will write dimension keys only if there are no conflicts. In case of conflicts, writeback will go through successfully except that the dimension key columns will be written NULL. This will be recorded in the writeback logs. It is recommended that the user add appropriate categories to avoid conflicts. * Add Date Key only works with Power BI time intelligence generated date hierarchy set in the columns field of the visualization pane. -### iv) Permissions +### 4. Permissions The permissions option allows control over users who can writeback. It is possible to grant writeback permissions to everyone in your organization or to a select few users to perform writeback. Inforiver leverages Azure Active Directory (AAD), hence finding and granting writeback permissions to your co-workers will be straightforward. @@ -146,7 +146,7 @@ Selecting this option will display an input field. Users can then specify the em -### v) Webhooks +### 5. Webhooks Inforiver webhook delivers a JSON payload to any HTTP endpoint. The JSON payload contains essential information about the writeback instance as shown below. @@ -205,8 +205,26 @@ To set up Inforiver Webhooks, paste the HTTP endpoint URL in the URL field. Clic The above are sample workflows that could be triggered using the Inforiver webhook. There are many other workflows possible. Please note that the Inforiver webhook is different from URL as Destination. Inforiver webhook's JSON payload only contains essential information about the writeback table. URL as Destination JSON payload contains the entire writeback table. Learn more [here](../destinations/url-as-destination.md). -### vi) Decimal Precision +### 6. Decimal Precision -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. The precision that is set in the destination configuration is displayed in the Decimal Precision section. [Learn more about configuring writeback destinations](../destinations/). +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. - + + +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. + + + +The precision that is set in the destination configuration is displayed in the Decimal Precision section. [Learn more about configuring writeback destinations](../destinations/). + + + +### 7. Text field length + +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/). + + + +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/3.-basic-interactions/explore-and-filter-data/search-and-filter.md b/working-with-inforiver/3.-basic-interactions/explore-and-filter-data/search-and-filter.md index 6734659f..9fe04b10 100644 --- a/working-with-inforiver/3.-basic-interactions/explore-and-filter-data/search-and-filter.md +++ b/working-with-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. - + ### 2.2. Column-level filter diff --git a/working-with-inforiver/4.-adding-business-logic-and-formulae/manage-inserted-rows-and-columns.md b/working-with-inforiver/4.-adding-business-logic-and-formulae/manage-inserted-rows-and-columns.md index 52173b61..b761f2f9 100644 --- a/working-with-inforiver/4.-adding-business-logic-and-formulae/manage-inserted-rows-and-columns.md +++ b/working-with-inforiver/4.-adding-business-logic-and-formulae/manage-inserted-rows-and-columns.md @@ -48,9 +48,9 @@ Access control for all the columns can also be set through the **Manage Columns* ### 3.2. Time interval mapping -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 theicon to view all the supported date formats. +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 theicon to view all the supported date formats. - + 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. diff --git a/working-with-inforiver/5.-conditional-formatting/rules-if-conditions.md b/working-with-inforiver/5.-conditional-formatting/rules-if-conditions.md index ade84cf3..fdad7227 100644 --- 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