You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would like the ability to set margin configurations for report PDFs to minimize whitespace and better utilize the available space on each page. Could be in the form of actual dimension or percent config, or some type of "wide mode" setting for PDFs.
Goal of Feature
Currently, there is a lot of whitespace in the margins on PDFs. Simultaneously, some reports do not fit on the PDF page horizontally, with tables or charts being cutoff. A configuration to utilize margin whitespace could help to improve PDF layout, reduce data tables being cutoff, and allow for more flexible formatting.
Current Solution / Workarounds
None
Alternatives
More control over component sizing or scaling when sending to PDF could help fit more on one page and prevent issues with tables being cutoff. However, this would still leave a lot of whitespace in the margins that is under-utilized.
The text was updated successfully, but these errors were encountered:
Feature Description
Would like the ability to set margin configurations for report PDFs to minimize whitespace and better utilize the available space on each page. Could be in the form of actual dimension or percent config, or some type of "wide mode" setting for PDFs.
Goal of Feature
Currently, there is a lot of whitespace in the margins on PDFs. Simultaneously, some reports do not fit on the PDF page horizontally, with tables or charts being cutoff. A configuration to utilize margin whitespace could help to improve PDF layout, reduce data tables being cutoff, and allow for more flexible formatting.
Current Solution / Workarounds
None
Alternatives
More control over component sizing or scaling when sending to PDF could help fit more on one page and prevent issues with tables being cutoff. However, this would still leave a lot of whitespace in the margins that is under-utilized.
The text was updated successfully, but these errors were encountered: