I would like to know if I can set a label to a hierarchical dimension, because If I have 2 dimensions, it will show like below:
That seems not beauty, so, there is a way to change this with a label or something in qlik sense?
Thanks, any ideas?
1. Unlink the Visualization
In the edit panel, click the chain icon and accept to unlink it from the master dimensions. This will allow you to edit the label accordingly.
Of course, this removes it as a master dimension so you it might not be the best if you have numerous sheets using the same chart.
2. Add the Label in the Master Visualization
I don't know what the rest of your app looks like, and I've found this to be finicky sometimes so it may not work --play around with it though.
While editing the master table, experiment with using ="Your Label Here" in the titles of the measures.
In my opinion and experience, Qlik Community Forum is more active than Stack Overflow. I highly recommend checking it out for help if you're finding Stack Overflow to be too slow: https://community.qlik.com/
Related
I see only 5 labels even that i have 6 options - how can i solve it? the Malicious Bots are not shown in the labels.
You can't see them because there no space available and so Tableau suggest you to not show it.
If you want to see it anyway, you can go to the Label mark of your worksheet, and check the flag "allow label to overlap".
Remember that selecting a specifc slice you can move the label, but I would not reccomend it if your chart may change due to filters.
Hope you can help.
I have attached my workbook. Basically, I have made swapping sheets. The sheets have different filters, and I need the filters to disappear depending on the sheet showing.
I have no problem with the sheet swapping. I been going through the internet for hours, without finding a good solution. I did look into this: New series of videos on swapping and popping on a dashboard(https://vimeo.com/294170859), but did not find it that helpful since it is not very flexible and too difficult to use if you have many filters, that need to change.
I have some kind of an Idea, of putting my filters in each of their container, and then have the container showing depending the sheet but do not how either.
But in the end, the filters needs to appear in the same spots too.
But I really need your help - Simply can't find a good solution!
Thank you!
Without putting your filters in containers and swapping those I can't think of any alternative way to alter which filters appear on your dashboard.
I don't know the exact specifics of your task, however, having perhaps faced similar issues almost always the best solution is to simplify. If possible instead of swapping sheets consider a new dashboard and just "show sheets as tabs". Altering a parameter is a click, just as clicking a dashboard tab - so no difference to the user. Also changing filters may be confusing to a user - they generally get used to seeing things in a certain place.
Of course none of this may apply to your specific situation.
I don't know if this is the right place to ask this question but I figured I might as well try to get an answer here.
My problem is the following: I'm a huge fan of Bootstrap and all there components so I'm genreally using them in every project im working on. So when I'm using container and container-fluid with different row's in between for sertain content-elements I haven't figured out a way to implement this inside the backend in an user-friendly way.
The way I used to do it was simply use the Grid Elements Extension to simply create containers, row's and col's and implement those within each other in the backend. Works fine, but its a whole lot of work for the user of the site to create content. I don't know if my explenation was clear, english isn't my first language and I don't know how to describe it in another way, but here's a picture of what I'm trying to say:
As you can see there are a lot of elements nested within each other so the user or admin has to actually "know" how bootstrap works to edit content without destroying the layout.
Is there any other way I can achive full flexibility for the content, e.g. a bunch of container's within a container-fluid as a wrapper and another bunch of cols's as children of the container?
I've tried to work with Mask, which seemed to be the solution at the beginning, but in the end I had to create one mask object for every possible way an element could be loaded, so there goes this option..
Does anyone else have this kind of "problem" or is there a simple (or hard, idc) solution I can use?
Thank you guys :)
I understand your "problem". My opinion: As soon as you have a page layout with multiple containers (container / container-fluid) and a flexible grid layout, I guess there is no better way without restricting flexibility or have some dirty logic / code. In some (minor) cases, you can help yourself with layout classes (DB field "layout") and some logic in fluid + a viewhelper to calculate the grid columns (e.g. imagegallery, where you can set the columns in backend and calculate the columns in frontend). But in my opinion, this is the most flexible way.
There are some people who solve this with new content elements and inline relation to its content elements. But IMHO this is more confusing for editors to see a grid layout in the backend and the possibility to flexible add content elements via content element to the container / column of choice.
A small, but effective useful helper for editors is to colorize your grid elements in the backend to help the editor to recognize different grids.
In my experience, editors can handle nested grids better than searching for multiple dropdowns in elements to understand grids.
Offtopic: editors survived templavoila, they will understand grids :-)
Others have asked this question before, but no one has provided an actual answer to it. I can't get all of the marks/labels to display in my Tableau visualizations.
Selecting "allow labels to overlap" does not fix the problem. That displays several hidden labels for the smallest of the areas, and it places those labels at the top of the bars, ignoring the formatting that sets the labels to the bottom. However, whether or not that option is checked, the empty areas in the screen shot stay empty. And those areas are clearly large enough to display the missing labels without encroaching on any other label.
I'm guessing this is a bug in Tableau because there's no reasonable explanation as to why this is happening, but I'm new to Tableau and unsure how to address this.
While I can offer no explanation, this has been a reported problem for several years. Tableau's own documentation states to check the Allow marks to overlap checkbox, yet that doesn't always work.
I don't know if it's a bug so much as it is a complicated calculation for the rendering engine to determine what will and won't fit into a space. To the human eye it will fit but it's possible the underlying calculations inside Tableau don't see it that way. I find that particularly on dual-axis charts (like yours) this happens more frequently. I've done two things to get around it when it comes up:
Change font family or font size
Put more info into the tooltips so the end user sees the data when they hover.
If you wish to pursue this as a bug, you will need to contact Tableau Support and file a case. They will ask you to submit a twbx file to reproduce the issue.
I hope that helps.
Label -> Font -> Automatic solved the problem for me
You can select individual marks, right click to pop up a menu, and specify whether to always hide or always show the labels for the selected marks (overriding the default behavior)
From a design and usability perspective is it best that an edit page mimics the layout of the view page?
Our view page is very dense. The data is tightly packed together, but when editing there are going to be extra controls next to each entry field. If we leave the layout the same it will be overly crowded. Will this cause problems with usability if the fields are rearranged?
It definitely impairs usability. Two hazards of re-arranging fields are:
Confusing users about which field they are editing
Making it difficult for users to find the field they want to edit.
These problems are exacerbated on high-density pages.
There are some times when this is ok. The best example I can think of is where the editor and viewer are different users. Another (more ambiguous) case is a situation where the edit screen needs to be highly optimized for fast throughput.
If possible, you might consider splitting the screen up, or making collapsable regions to give the user (and the screen) a little room to breathe.
In general you want to keep the edit page as simillar as possible to the view page. In general. There are cases where this just doesn't make sense especially if you have to input a lot of extra data that is not shown in the view, which it sounds like is your case.
What I would try and do is make sure you continue to group and order the fields in the same manner as if you were viewing so while they might be in slightly different places at least they would be logically grouped the same.
It depends upon your workflow.
If the user has to go back and forth between edit and view, it will be very confusing to the person, as fields may jump around, they might lose which field they are on, etc.
If your view page is very dense, you might try breaking it up into sections, each with its own edit function. You could have it shoot to its own edit page or be all 'web 2.0' and throw up a lightbox with the section edit form over the view page.
The more that things are similar, typically, the easier it is for a user to use. I don't know what your particular layout looks like but from a general point of view, a crowded view is often hard to look at and cluttering it up with additional controls would make it worse.
As much as I'm not a spreadsheet guy, editing in Excel or similar products is easy because it doesn't clog up the view with lots of controls. The edit panel is the view panel. For my own products, when things are consistent, the users are generally less confused.
I have had a similar problem. What I did was have a View page that lets you see everything, but you need to drill into individual edit pages for logical sections. Within the logical sections the fields are always in the same order (and with the same labels) as on the view page. It's things like this which make your application just feel a bit nicer.
Don't throw everything onto a massive edit page just because they all relate to the same thing in your database model. Break them out into sets that make sense each with 3-7 fields on them.
If they really need to edit everything (like when creating a new thing) then I would go for a wizard approach which steps through through, presents a view-only summary and then lets them save.