Total Paid
Total Members
New Members Today
Users Online
: Use the exact same column headers in every Page Properties macro to ensure the report columns align correctly.
The chaos of "multiple rows" emerges when we attempt to defy this sovereignty. This manifests in two distinct dimensions, each revealing a flaw in our digital metaphysics.
The fundamental issue stems from a design choice in Atlassian's macro architecture: Each page in your report corresponds to a single Page Properties macro instance. If you place multiple tables or rows within a single Page Properties macro, the report will only capture the first one.
Every single page with that label will now appear as its own distinct row in your master table. If you have 20 risk pages, you will have 20 clean rows. Strategy 2: Multiple Page Properties Macros on One Page confluence page properties report multiple rows
Before diving into multiple rows, let’s define the basics:
: If you have multiple Page Properties macros on one page, the report will automatically create a separate row for each macro instance found on that page. 3. Alternative: Table Excerpt (For complex tables)
If you only need the appearance of multiple rows within a single page's report entry, and you do not need to sort or filter those sub-rows individually, you can use a formatting trick inside a native Page Properties macro. On your child page, open your macro table. : Use the exact same column headers in
On your main parent page, insert the macro. Set it to filter by the label inventory-item and restrict the ancestors to "Current Page". This instantly creates a clean, multi-row table where each child page acts as a row. Method 3: Leverage Advanced Third-Party Add-ons
If your version concatenates the data, remains the most stable workaround for clean data separation. Troubleshooting Common Report Issues Data is Spilling Into One Row
Confluence recommends that the table inside a Page Properties macro , as the report macro will ignore it. The correct structure is a simple two-column table: The fundamental issue stems from a design choice
Confluence is a powerful tool for documentation, but it truly shines when used for structured reporting. The and Page Properties Report macros are a dynamic duo that allows you to aggregate key data from multiple pages into one organized overview table.
Inside the macro, create a standard two-column table for a single item. Step 2: Use the Create from Template Macro
The cleanest, native way to get multiple rows in a Page Properties Report is to change your page structure. Instead of putting all your items on one page, create a separate child page for each item you want as a row. Step 1: Create a Blueprint/Template Child Page
This add-on allows for highly customizable table structures and data pulling capabilities. It bypasses the strict structural limitations of the native Atlassian Page Properties macros, allowing row-by-row data indexing. 3. Confluence Databases (Atlassian Native)
If you are looking to promote your product or services. This is the right place for you, with competitive prices and the ability to reach thousands of potential customers, you will get the traffic you always wanted!