Expand my Community achievements bar.

Join us January 15th for an AMA with Champion Achaia Walton, who will be talking about her article on Event-Based Reporting and Measuring Content Groups!

Header text wrapping should be turned on by default

Avatar

Level 8

3/10/18

Everyone is loving this new option to wrap header text in columns, details in here: Column Settings

"Lets you wrap the header text in Freeform tables to make headers more readable and tables more shareable. This is useful for .pdf rendering and for metrics with long names."

But again cool new setting that is hidden in the column settings. Not all users are finding these settings easily. This is also that kind of setting that I'm having hard to find situation where you wouldn't want to use this? It doesn't make any sense to me, can someone explain when you would want to hide header text? Ok, maybe if you have looooong names for metrics or have dozens of breakdowns or something weird, however, these situations are one in a million and that's why it would be wiser to have this enabled by default and you would always have the option to change it if needed.

Even better would be to have option to change all the default settings for Workspace in admin section, but wanted this header text wrapping to be own idea, because it should be no-brainer, or am I missing something? Vote, comment, agree, disagree...

15 Comments

Avatar

Level 4

3/18/18

I'm happy to have the new column wrapping feature as an option, but I would prefer if column wrapping is off by default.

The main reason is that if I have a number of tables in a workspace, then I can be sure they will have a consistent height, and this makes arranging the workspace much easier when I place tables besides one another or beside a visualisation.

Sometimes I will duplicate segments and metrics just to give them a shorter name so they don't get truncated! I make sure I don't share them with anyone so it doesn't clutter up the segment/metrics library.

Avatar

Employee Advisor

4/9/18

You bet! Thanks for fostering the discussion here, this really helped us in making our decision. We will be continuing to think about project level settings as well, to help in cases where customers do not want this as their default.