2025 Week 34 | Sigma: Let’s Request Some Data Changes

No dataset this week

• Create the Rules Engine Foundation:

  • Build an Input Table to act as your master list for data quality rules.

  • Tip: Include columns for the rule’s name, the column it targets (e.g., “Channelgrouping”), the value to find, the value to replace it with, and a column to track the rule’s status (e.g., “Draft,” “Active”). Don’t forget to add system-generated columns for Row ID and audit fields like Submitted_By and Approval_Date.

• Build the Self-Service Submission Form:

  • Use Control Elements (like text inputs) to create a user-friendly form for submitting new rules.

  • Add a “Submit” button that uses an Action to:

    • Add a new row to your rules input table.

    • Automatically set the new rule’s status to “Pending Approval”  (or whatever you want to call it) and populate the submission timestamp and user.

    • Tip: Add a second effect to the action to clear the form fields after submission for a better user experience.

• Create the Approval Workflow:

  • Build a “Rule Approval Queue” using a Table element.

• • Tip: Filter this table to only show rules where the status is “Pending Approval.”

  • Create Action columns directly in the table for “Approve” and “Reject.”

  • Configure the actions on these columns to update the selected row in your master input table—changing its status and populating the Approved_By and Approval_Date fields.

  • Apply the Rules and See the Results: (BONUS)

    • Join your raw data (the GA table) to a filtered version of your rules table (showing “Active” rules only).

    • Create a new calculated column (e.g., [Channelgrouping_Cleaned]) that uses a conditional formula to apply the rules.

    • Tip: Your formula should check if the join found a matching rule. If it did, use the Replace_Value; if not, keep the original value.

    • Build a chart to track Request Statuses

Don’t forget to publish and share your build!

Let’s see how you use it!