on 07 Feb 2019 17:44:25
When you add a new tab to an existing template file, it does not fetch the attributes (background color or a company logo or any such you feel to have in each page) to the new tab. For example, I created a template with company Logo and a page background with a .PNG slide having a boarder in it. The pages you create as template will be there existing. However, if you add a new tab to the file even from its template file does not bring the new pages features to it rather it creates another fresh common PBI tab. I wonder if there are any existing features that can override this issue.
-Jinu Peter-
- Comments (13)
- Merged Idea (7)
RE: Template feature apply to new tabs
Power BI does not have an option to create a master page or template page similar to Powerpoint
This will help an organisation to update the visualisation on a template page and reduce the time spent on creating a standardised page for every new project.
Customisation and making a template for visualisation -
1. Power BI can help in customising the default font that will be used for visualisation. This will same time in changing the font, font size , color everytime when we create a visualisation. (For Example, An organisation's default font shall be Arial, Font Color shall be - Blue, Font Size shall be -14 etc..)
2. It can also help in customising the default background colours for the visualisation etc...
RE: Template feature apply to new tabs
Hi,
Every time we create a new report, we have to either customize the template with company name and logo etc., or set the page back ground. Instead, if we could set a default template then every time we create a new report we can see the customized template as a default page. Eventually, this will help to save report design time.
RE: Template feature apply to new tabs
Can you create a master tab (such as Power Point Master) where multiple pages' visuals CAN be linked to that master? In that way if a column needs to be added you just make the change on one visual and the filters are relative to the page filters.
RE: Template feature apply to new tabs
I'm using SVG images as a page background template. If the image is updated, each page must be changed individually. If the report had master pages, the change could be done once. There are also some common page elements including some with a common navigation action. These could be moved to the master page.There are also some elements that would exist on each page related to the master, but would have per-page differences. For example, navigation buttons that would change their target and displayed text, but otherwise remain the same. Master page elements should be able to be set to "locked", where they stay the same on each page, or "unlocked", where they stay linked to the master page, but can have attributes selectively override the master page one. I'd also like to add guidelines to the master page to allow proper snapping, and control if master page elements create a snap target in the individual pages. This would rely on custom guidelines to be added first, for example:Better layout support with granular control of gridlines and guidesThis is important because:Once a design is made by using an image background instead of shapes, there is no longer a snap target preventing accidental overlap of design elementsThe actual snap location may not be directly up against an object. Usually a small margin would be better.
RE: Template feature apply to new tabs
There is precedent for this in multiple other M365 products:PowerPoint (Slide Masters)Visio (Background Pages)Publisher (Master Pages)This would be valuable to improve productivity and consistency, but it's also important to have some UX parity across products within the M365 suite: once a user learns how to use a feature, they can leverage that skill across the suite.
RE: Template feature apply to new tabs
There is precedent for this in multiple other M365 products:PowerPoint (Slide Masters)Visio (Background Pages)Publisher (Master Pages)This would be valuable to improve productivity and consistency, but it's also important to have some UX parity across products within the M365 suite: once a user learns how to use a feature, they can leverage that skill across the suite.