+
+### Base_Table in Sigma
+In Sigma, create a new workbook and add a new table to a page, using the `Base_Table` from the `SIGMA_QUICKSTARTS` database and the `PIVOT_SPREADING` schema.
+
+
+
+Rename the page to `Data`:
+
+
+
+Group the table as shown in the screenshot below:
+
+
+
+Set the `Price` and `Revenue` columns to currency
+
+Add a new column and set it's formula to:
+```code
+DateTrunc("year", [Date])
+```
+
+Rename the column to `Year`.
+
+Add a new column and set it's formula to:
+```code
+RowNumber()
+```
+
+
+
+Add three more columns after the `RowNumber` column, rename and apply the following formuala to each one:
+```code
+Column Name: Formula:
+l1_key MD5([Product Type] & Text([Year]))
+l2_key MD5([Product Type] & [Product Family] & Text([Year]))
+l3_key MD5([Product Type] & [Product Family] & [Product Line] & Text([Year]))
+```
+
+
+
+These three columns each is a hashed representation of a combination of product attributes and the year. Hashing (MD5) ensures that the keys are compact, unique, and suitable for efficient lookups.
+
+These keys represent different levels of granularity in the data:
+
+- l1_key: Represents the highest level, combining Product Type and Year.
+- l2_key: Adds Product Family to provide more specificity within the same Product Type and Year.
+- l3_key: Adds Product Line for the most detailed level, capturing Product Type, Product Family, Product Line, and Year.
+
+This allows the stored procedure to apply changes only to rows associated with the selected grouping.
+
+We will use these later in a store procedure to determine how we make spreading adjustments.
+
+Click `Publish`.
+
+
+
+
+## Create Pivot Table
+Duration: 5
+
+Add a new page and rename it to `Pivot`.
+
+Add a new pivot table to the page and set it's source to the `BASE_TABLE` table on the `Data` page.
+
+Configure the pivot as shown in the screenshot below:
+
+
+
+Rename the pivot table to `Revenue Planning`.
+
+Our pivot is done for the moment. We need to prepare additional data in Snowflake to support spreading operations.
+
+
+
+
+## Spread Update Table
+Duration: 5
+
+In order to make this work, we will use another table that we have arbitrarily named `Spread_Update`. You may have noticed this table was created when we ran the Snowflake script to load the `BASE_TABLE` data from S3.
+
+### Add to Sigma page
+Add it to the `Pivot` page under the `Revenue Planning` table:
+
+
+
+With this table added to the workbook, we can now reference it's columns in the `Revenue Planning` table.
+
+### Add more columns to Revenue Planning
+
+
+
+Add a new column set the formula to:
+```code
+Lookup([SPREAD_UPDATE/Revenue], [Order Number], [SPREAD_UPDATE/Order Number], [Date], [SPREAD_UPDATE/Date], [Sku Number], [SPREAD_UPDATE/Sku Number])
+```
+
+This formula performs a lookup operation, retrieving the value of `SPREAD_UPDATE > Revenue` from the `SPREAD_UPDATE` table based on a match between the specified columns in the current table and the corresponding columns in the `SPREAD_UPDATE` table.
+
+Add another new column and rename it to `Coalesced Revenue`. Set the formula to:
+```code
+Coalesce([Revenue (SPREAD_UPDATE)], [Revenue])
+```
+
+This formula will display the `SPREAD_UPDATE` value where it exists, and fallback to the base `Revenue` value otherwise. Since we don't yet have any data in `SPREAD_UPDATE`, the existing `Revenue` value will be used.
+
+Drag the `Coalesced Revenue` column to the `VALUES` grouping and rename it back to `Coalesced Revenue`.
+
+The page now looks like this, including a little bit of text and currency format adjustments:
+
+
+
+Click `Publish`.
+
+### About Spread_Update
+The `Spread_Update` table plays a central role in the pivot table spreading functionality, as it is the target for all updates made by the soon to be created stored procedure. It's primary role is to:
+
+Act as a Data Adjustment Target:
+- This table holds the rows that will be updated during the spread process.
+- Adjustments made in the pivot table are applied to this table, modifying the relevant rows based on the selected `KEY` and `LEVEL` values passed.
+
+Act as am Intermediate Layer:
+- It acts as a bridge between the source data (BASE_TABLE) and the final output.
+- Rows from the `BASE_TABLE` are merged into the `SPREAD_UPDATE` table if they don’t already exist, ensuring that all necessary data is available for spreading.
+
+Efficiency:
+- By focusing updates on a single table, the stored procedure ensures that adjustments are localized outside of the orginal source data.
+
+The SPREAD_UPDATE table includes the following columns (based on the stored procedure):
+
+| Column | +Description | +
|---|---|
| date | +The date associated with the transaction or data row. | +
| l_1_key | +Hierarchical key representing the highest level of aggregation. | +
| l_2_key | +Hierarchical key for a more specific grouping. | +
| l_3_key | +Hierarchical key for the most granular level. | +
| order_number | +Unique identifier for each order. | +
| revenue | +The revenue value for the specific row, which will be adjusted. | +
| sku_number | +Identifier for the product or item in the transaction. | +
+
+This creates a new `hidden` page called `Modal 1`. The page is hidden as we only want it to show up when a user clicks something that requests it.
+
+Rename the page to `Adjustments` and the title from `New Modal` to `Adjustments`.
+
+For the purposes of this demonstration, this modal will allow the user to adjust the selected `Coalesced Revenue` from the pivot table, choosing from three different methods. It will also display information about selections have been made.
+
+
+
+### Adding the Controls
+
+### Selected values display
+We will use a Sigma input controls to capture user selected values and to refer to these values when we call the stored procedure.
+
+
+
+Add the following controls to the `Adjustments` modal:
+
+#### 1: Current revenue value selected (p_current):
+Add `Number input` control and set the `Control ID` to `p_current`. Also set the `Data format` to `Currency`.
+
+#### 2: Level selected (p_level):
+Add `nunber input` control and set the `Control ID` to `p_level`. Also set the `Data format` to `Automatic`.
+
+#### 3: Key correcsponding to the level selected (p_key):
+Add `text input` control and set the `Control ID` to `p_key`. Also set the `Operator` to `Equal to`.
+
+#### 4: Selected product type (p_type):
+Add `text input` control and set the `Control ID` to `p_type`. Also set the `Operator` to `Equal to`.
+
+#### 5: Selected product family (p_family):
+Add `text input` control and set the `Control ID` to `p_family`. Also set the `Operator` to `Equal to`.
+
+#### 6: Selected product line (p_line):
+Add `text input` control and set the `Control ID` to `p_line`. Also set the `Operator` to `Equal to`.
+
+#### 7: Selected year (p_year):
+Add `Date input` control and set the `Control ID` to `p_year`.
+
+To save some actions later, place all these controls in a container. Simply left-click/hold and drag a mouse window around them and click the container icon.
+
+While not required, we applied a little styling to the container and renamed it to `Selected_Values`. We also added a `UI` > `Text` label to it:
+
+
+
+
+
+### Adjustment values selection
+Now lets add a few more controls (outside the `Selected Values` container) to allow the user to enter a value for the adjustment and select a method from three options.
+
+#### 1: Adjustment value desired (p_adjustment):
+Add `Number input` control and set the `Control ID` to `p_adjustment`. Also set the `Data format` to `Number`.
+
+#### 2: Adjustment method desired (Method):
+Add `Segmented` control and set the `Control ID` to `Method`. Configure the `Create manual list` as shown in the screenshot below:
+
+
+
+#### 3: Value of the adjustment:
+Add `UI` > `Text` element and set its formula to:
+```code
+If(IsNull([Method]) OR IsNull([p_current]) OR IsNull([p_adjustment]),
+ 0,
+ Switch([Method],
+ "Adjust", [p_current] + [p_adjustment],
+ "Change", [p_adjustment],
+ "Scale", [p_current] * (1 + [p_adjustment] / 100),
+ 0))
+```
+
+This formula dynamically calculates a new value based on the selected adjustment method:
+
+- Adjust: Adds or subtracts P Adjustment directly from P Current.
+- Scale: Adjusts by percentage the value supplied in P Adjustment.
+- Change: Replaces the value with the value for P Adjustment.
+- If the required values are not set, it will return zero.
+
+After some fiddling with the UI, and placing the adjustment items in a container called `Desired Adjustment`, the section now looks like this:
+
+
+
+
+
+
+## Actions
+Duration: 5
+
+With our modal configured we can now setup actions to leverage the controls on that page.
+
+Return to the `Pivot` page, select the `Revenue Planning` pivot table and click on it's `Actions`.
+
+We have one action configured so far that opens the modal when a user clicks on a `Coalesced Revenue` cell. You can test that now to see it work.
+
+We can now add more actions to clear the modal's controls and pass values to it, based on the user click.
+
+### Clear the containers (2) of previous values
+For our second action, click the `+` and configure a `Clear control` action, targeting a `Container` and the `Selected_Values` container.
+
+Repeat the process (this time using the lower `+` icon) and create the same action for the `Desired Adjustments` container:
+
+
+
+### Set actions for three product levels
+Configure three `Set control value` actions for product `type`, `family` and `line`:
+
+
+
+### Configure action for selected level
+In this next `Set control value` action, we will use a formula to determine the value of the product level selected:
+
+Here is the formula to be used, as shown in the screenshot below:
+```code
+If(IsNotNull([p_line]), 3, IsNotNull([p_family]), 2, IsNotNull([p_type]), 1)
+```
+
+
+
+### Set selected year
+You know what to do now...
+
+
+
+### Set the key value selected
+Configure another `Set control value` action to update the `P Key` control, using this formula:
+```code
+Switch([p_level], 3, MD5([p_type] & [p_family] & [p_line] & Text([p_year])), 2, MD5([p_type] & [p_family] & Text([p_year])), 1, MD5([p_type] & Text([p_year])))
+```
+
+
+
+### Set the current value selected
+Configure another `Set control value` action to update the `P Current` control, using this formula:
+```code
+Lookup(Sum([Revenue Planning/Coalesced Revenue (1)]), [p_key], Switch([p_level], 3, [Revenue Planning/l3_key], 2, [Revenue Planning/l2_key], 1, [Revenue Planning/l1_key]))
+```
+
+
+
+Now drag the `Open a modal` action to the last position:
+
+
+
+Click `Publish`.
+
+### Give it a quick test
+Click on any `Coalesed Revenue` value, noting the product details, value and year. These values should appear in the modal as expected. For example, if the value selected below is clicked:
+
+
+
+We can see those values appear in the modal as expected. We also can enter a value in `P Adjustment` and click the `Change` method to see the desired value appear too:
+
+
+
+Now we will wire up the stored procedure to take some of this information and update our `Revenue Planning` and `Spread_Update` table.
+
+
+
+
+
+## Stored Procedure (procedure)
+Duration: 5
+
+Sigma users will click a button to execute a stored procedure, named `SPREAD`, that is designed to handle pivot table spreading by adjusting values in a designated Snowflake table called `SPREAD_UPDATE`, based on user input.
+
+The procedure interacts with the `BASE_TABLE` to prepare data, applies adjustments (e.g., scaling, direct changes, or percentage changes), and ensures data integrity vy not altering the source data.
+
+It also logs SQL operations for troubleshooting purposes.
+
+
+
+This procedure can dynamically handle adjustments at different hierarchical levels (e.g., l1, l2, l3 keys) and updates only the rows relevant to the selected pivot table cell.
+
+### Summary of operation
+
+Here are the basic steps taken by the procedure:
+
+- **Prepare the data:**
+
+The `Secondary` button will be used to clear and exit the modal:
+
+
+
+From the `Actions` menu of the `Primary` button, configure the action to call the stored procedure:
+
+
+
+
+
+
+
+Once Sigma evaluate the selected procedure, we are prompted to choose how required variables should be passed:
+
+
+
+Add another action to refesh the `Revenue Planning` pivot with the new data.
+
+Add another action to clear the `Selected Adjustments` and `Desire Adjustment` containers, just so we are always sure that the current values are removed prior to using the modal.
+
+Add one more action to `Navigate in this workbook` to the `Pivot` pages, `Top of page`.
+
+
+
+Click `Publish` and switch to the published version:
+
+
+
+### Give it a test
+Clicking on a value in a `Coalesced Revenue` column:
+
+
+
+We set `P Adjustment` to `90000` and clicked `Change`.
+
+Since we are directly changing values, the `Calculated Adjustment` is also `90000`.
+
+
+
+After saving, we are returned to the `Pivot` page and can see the value we selected for `Coalesced Revenue` has been updated to `90000`.
+
+
+
+Notice that the original value for `Sum of Revenue` in `2020` has not changed as we did not want to alter the source data.
+
+Feel free to try more adjustments using the `Adjust` or `Scale` methods. They will work as expected and the actual calculations that were called out earlier can easily be adjusted to suit different business requirements.
+
+
+
+
+## Logging
+Duration: 5
+To assist in debugging and to also have a detailed audit of the adjustmnents, we have included a log table of all the adjustments.
+
+Add a new page to the workbook and rename it to `Log`.
+
+Add a new table and connect it to the `SQL_LOG` table:
+
+
+
+For clarity, we cleared the `SQL_LOG` table and did one adjustment so we could show the expected results from each adjustment saved.
+
+`SQL Text` contains the actual query that was built and exectuted by the procedure:
+
+
+
+This can be really useful in debugging and tracking. Of course, there are other options like using Sigma's [Audit Logging](https://help.sigmacomputing.com/docs/enable-audit-logging) or Snowflake's [Query History](https://docs.snowflake.com/en/sql-reference/functions/query_history) reporting as well.
+
+
+
+
+## What we've covered
+Duration: 5
+
+In this QuickStart, we built a data application to enable end users to make adjustments in a pivot table, without altering the underlying data.
+
+This functionality allows businesses to transition from static reporting to dynamic, interactive workflows.
+
+**Additional Resource Links**
+
+[Blog](https://www.sigmacomputing.com/blog/)
](https://twitter.com/sigmacomputing)
+[
](https://www.linkedin.com/company/sigmacomputing)
+[
](https://www.facebook.com/sigmacomputing)
+
+
+
+
diff --git a/site/sigmaguides/src/dataaps_fundamentals/dataaps_fundamentals.md b/site/sigmaguides/src/dataaps_fundamentals/dataaps_fundamentals.md
index eb42278a..2c2ddce3 100644
--- a/site/sigmaguides/src/dataaps_fundamentals/dataaps_fundamentals.md
+++ b/site/sigmaguides/src/dataaps_fundamentals/dataaps_fundamentals.md
@@ -3,9 +3,9 @@ id: dataaps_fundamentals
summary: dataaps_fundamentals
categories: dataapps
environments: web
-status: published
+status: hidden
feedback link: https://github.com/sigmacomputing/sigmaquickstarts/issues
-tags: default
+tags:
lastUpdated: 2024-10-24
# Data Apps Fundamentals
@@ -712,7 +712,7 @@ On the `Modal - Create Task` page, revise the title to include the project name.
Select the text `Create Task` and append it with `for ` followed by `=`, which opens the formula bar.
-Type `[master_ProjectName]` and click the green checkmark:
+Type `[master_Project-Name]` and click the green checkmark:
@@ -732,7 +732,7 @@ The new task should appear in the `Task Tracking Input Table`:
Try this multiple times to add new tasks to the task tracking table.
### Step 15:
-On the `Project Tracking` page, add a new `Column via lookup` to the `Task Tracking Input Table`.
+On the `Project Tracker` page, add a new `Column via lookup` to the `Task Tracking Input Table`.
This time we used the selected element panel, `COLUMNS` menu to add a new column to demonstrate another way to do it: