Why does page properties report not show all content even when everything is labeled/formatted right

[Melissa Schwartz]

We use the page properties to house a small table with information on project status. As far as I can tell everything is properly formatted and all pages are labeled with the correct label that is being called for in the report. The report shows up on our homepage and is set to call up everything from our space with the requested labels. We have given it the table length of 30, but it is only showing 4-5 and it does not show all of the called for content. I've tried relabeling and deleting and replacing the page properties tables in the pages and none of this has fixed the issue. 

[Bastian Stehmann · Accepted solution]

Hi @Melissa Schwartz ,

Welcome to the Community. 

Are your tables formatted right with the header column? And is the spelling of the "attributes " correct?

[Melissa Schwartz]

I forgot to add that originally all of our page properties were showing up in the report and a few weeks ago (about 4 weeks) some of them disappeared without the settings being changed. This leads me to believe that I did have the header column correct as well as the attributes. Have you ever seen it work and then disappear?

[Bastian Stehmann]

I'm sorry, never experienced something like that.

[Darryl St_ Pierre]

Melissa,

If you look at the Page History, is there nothing in any of the versions showing any changes to the Page History Report macro, or the source table?

[Melissa Schwartz]

There haven't been any changes to the page properties report macro since the time we noticed the issue.

[Darryl St_ Pierre]

Sorry, I've run out of ideas. You may want to open a ticket with Support (if you're on a version with support) as they can take a deeper dive into what might be going on.

[Melissa Schwartz]

The issue has been resolved. It required opening read/write access on the server that this program is stored. Once that was granted all page properties tables showed up in the report.

[Shannon S]

Hello Melissa!

I've followed up with you on your new case, Why is CONFSERVER-34141 bug fix not working? to let you know that I have created a support ticket for you for this issue.

As I mentioned on the new question, please follow-up here once the issue is resolved, so the community can also know.

Thank you!

Regards,

Shannon

[Darryl St_ Pierre]

@Melissa Schwartz , as additional info to what @Bastian Stehmann has provided, your table headers must match exactly what's entered in the macro. Also worth noting, if you have multiple tables within the macro, it will only read the columns from the first table. Not a common occurrence, but I ran into someone doing this just last week.