Values from Page Properties Report macro in Page Properties macro not shown in Page Properties Report macro

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      Issue Summary

      • "Page Properties Report" macro can be added into a table on a page.
      • The table can be wrapped in a "Page Properties" macro.
      • But using another "Page Properties Report" to display the "Page Properties" macro above, the results from the "Page Properties Report" macro is not shown.
      • This is reproducible on Data Center:
        • No.
      • Editor:
        • Legacy and current editor.

      Steps to Reproduce

      1. Create a new page: Page 1.
        • Add the label, "Page1".
      2. Add the "Page Properties" macro.
        • Add a table with some values in it.
        • Publish the page.
      3. Create another page: Page 2.
        • Add the label, "Page2".
      4. Add the "Page Properties" macro.
        • Add a table with some values in it.
        • Add the "Page Properties Report" macro into the table as well.
        • Configure the Page Properties Report macro to pull results from the label, "Page1".
        • Publish the page.
      5. Create another page: Page 3.
        • Add the "Page Properties Report" macro into the page.
        • Configure the Page Properties Report macro to pull results from the label, "Page2".
      6. All other values from the table in Page 2 will show up, except the values from the "Page Properties Report" macro.

      Expected Results

      • All the values results from the "Page Properties" macro, including the "Page Properties Report" macro, should also be displayed in the "Page Properties Report" macro.

      Actual Results

      • All other values is shown, except the "Page Properties Report" values.

      Workaround

      • Currently there is no known workaround for this behavior. A workaround will be added here when available

      Note

      • A similar issue was reported some time back, and included a workaround.
      • But the workaround is no longer applicable, and the bug has been closed.

            Assignee:
            Unassigned
            Reporter:
            Sattesh M
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: