sigmacomputing · pballai · Aug 22, 2025 · Aug 22, 2025 · Aug 22, 2025 · Aug 22, 2025
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/addcol.png b/site/sigmaguides/src/tables_json_parsing/assets/addcol.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json1.png b/site/sigmaguides/src/tables_json_parsing/assets/json1.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json10a.png b/site/sigmaguides/src/tables_json_parsing/assets/json10a.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json10b.png b/site/sigmaguides/src/tables_json_parsing/assets/json10b.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json10c.png b/site/sigmaguides/src/tables_json_parsing/assets/json10c.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json10d.png b/site/sigmaguides/src/tables_json_parsing/assets/json10d.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json10e.png b/site/sigmaguides/src/tables_json_parsing/assets/json10e.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json10f.png b/site/sigmaguides/src/tables_json_parsing/assets/json10f.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json10g.png b/site/sigmaguides/src/tables_json_parsing/assets/json10g.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json2.png b/site/sigmaguides/src/tables_json_parsing/assets/json2.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json3.png b/site/sigmaguides/src/tables_json_parsing/assets/json3.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json3a.png b/site/sigmaguides/src/tables_json_parsing/assets/json3a.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json3b.png b/site/sigmaguides/src/tables_json_parsing/assets/json3b.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json9a.png b/site/sigmaguides/src/tables_json_parsing/assets/json9a.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json9b.png b/site/sigmaguides/src/tables_json_parsing/assets/json9b.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json9c.png b/site/sigmaguides/src/tables_json_parsing/assets/json9c.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json9d.png b/site/sigmaguides/src/tables_json_parsing/assets/json9d.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json9e.png b/site/sigmaguides/src/tables_json_parsing/assets/json9e.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json9f.png b/site/sigmaguides/src/tables_json_parsing/assets/json9f.png
diff --git a/site/sigmaguides/src/tables_json_parsing/assets/json9g.png b/site/sigmaguides/src/tables_json_parsing/assets/json9g.png
diff --git a/site/sigmaguides/src/tables_json_parsing/tables_json_parsing.md b/site/sigmaguides/src/tables_json_parsing/tables_json_parsing.md
diff --git a/..._cases_fpna_report_based_on_template/use_cases_fpna_report_based_on_template.md b/..._cases_fpna_report_based_on_template/use_cases_fpna_report_based_on_template.md
@@ -1,12 +1,12 @@
-author: pballai
+\author: pballai
 id: use_cases_fpna_report_based_on_template
 summary: use_cases_fpna_report_based_on_template
-categories: use cases
+categories: use-cases
 environments: web
-status: Hidden
+status: Use Cases
 feedback link: https://github.com/sigmacomputing/sigmaquickstarts/issues
-tags:
-lastUpdated: 2025-07-31
+tags: default
+lastUpdated: 2025-08-22
 
 # Build a Custom FP&A Report based on a Template
 
@@ -118,14 +118,14 @@ Used to slice and filter financial data by business segments:
 ### Understanding the Account Hierarchy Table
 The Account Hierarchy table typically contains three types of columns:
 
-**1. Section/Grouping for Totals:**<br>
+**1. Base-Level Hierarchy Information:**<br>
+Used to define the relationship between accounts and categories. This enables the join to the journal entry table.
+
+**2. Section/Grouping for Totals:**<br>
 Defines high-level rollup categories that appear in reports:
 
 Example values: Operating Expenses, Revenue, COGS
 
-**2. Base-Level Hierarchy Information (Level 1):**<br>
-Used to define the relationship between accounts and categories. This enables the join to the journal entry table.
-
 **3. Full Hierarchy Path (Level 1 to N):**<br>
 Optional fields that represent the full drill path across levels. These allow display and aggregation at various levels of detail.