It is difficult to arrange graphs in a Tableau dashboard because it is hard to get the layout to look the way I want.
The reason is that when you drop or move an object with the mouse, it does not enter the intended hierarchy, Because changing the size or position of one object causes other objects to become unintentionally sized or positioned.
So, I gave up on the idea of elaborating on the layout and thought that if I used a grid layout, I could quickly create a dashboard that was both quick and reasonably good looking, I found an article on how to do a grid layout in Tableau, which is exactly what I was looking for! Thanks!
There was a point where I actually got into it, and I have described how to deal with it here.
Since the above article is a prerequisite, it would be easier to understand if you read that first.
Brief description of grid placement
You express a grid arrangement by constructing a table using "Horizontal" and "Vertical" and setting it to "Equal Content Placement.
For example, for a 2x2 grid, the hierarchical structure would be as follows
If the "Horizontal" and "Vertical" settings are set to "Equal Content Placement", a grid arrangement will be used. Horizontal and Vertical can also be interchanged.
I see\~! Intuitive and easy to understand!
problem
The principle is simple, and it looks like it can be done quickly, but in fact, it is very difficult to create this hierarchical structure....
As you can see below, no matter how many times you try, "It just isn't so!!!!" It turns out to be....
Cause and Solution
The reason it doesn't work is that if you drop an object or sheet in the top level container ("horizontal" in the diagram above), it will not go into that container, but will be placed on the same level.
Since the container and the overall frame are the same size, the drop goes into the overall frame, not the container.
So, once the topmost container is "floating" so that it does not overlap with the overall frame, it can be dropped into the container successfully.
Then, when the "floating" of the topmost container is released again, the container is hooked into the whole and works fine.
For example, the aforementioned 2x2 grid can be created as follows
The key point is to use "floating" not as a layout but as a function to evacuate to the work area.
supplementary explanation
If an object cannot be dropped at the intended position, it can be successfully dropped once by setting it to "floating," removing it from the hierarchy, and then dropping it again and starting over.
If you have trouble grasping the "floating" object, use [Floating Order]-[Move to Top] to solve the problem.
Since "detach from placed object to floating object" and vice versa, "drop from floating object to placed object" are frequently done in the trial-and-error process, The shortcut "Hold down the Shift key while dragging an object with the mouse" is useful for this purpose.
It is as if the entire frame (tiles) were once ignored and the "vertical" or "horizontal" direction that is made "floating" is considered the base canvas to work on.
Then, after the series of operations is complete, the base is "floated" off and fitted to the tiles to complete the process.
Impressions, etc.
I used to set the graph to "floating" and place it by specifying the position and size directly as a last resort when I was in trouble, but this seems to make my work much easier.
The following layouts can be created easily and reliably if done carefully and with an awareness of structure.
It is quite difficult to drop an object at an arbitrary position in the tree, but "drop as floating" is a technique that can be used not only in grid layouts.
It would be dramatically easier to use if the hierarchical tree could be moved directly by dragging and dropping with the mouse.
