2
.. i18n: Defining Level
3
.. i18n: ==============
9
.. i18n: :ref:`Level <level-link>` It specifies the actual data to be displayed. It
10
.. i18n: specifies the depth for the hierarchy. Now taking the same example for the
11
.. i18n: Prodcuts. We need it to be two level depth.
14
:ref:`Level <level-link>` It specifies the actual data to be displayed. It
15
specifies the depth for the hierarchy. Now taking the same example for the
16
Prodcuts. We need it to be two level depth.
18
.. i18n: #. Product Category
19
.. i18n: #. Product Name
25
.. i18n: Lets start with making the levels. Details like hierarchy name, level name
26
.. i18n: filled by default according the schema we are in. We need to specify the column
27
.. i18n: to be used for filling the level. We open the column name and it will show all
28
.. i18n: the fields from tables defined in the hierarchy. We select name from the
29
.. i18n: product category
32
Lets start with making the levels. Details like hierarchy name, level name
33
filled by default according the schema we are in. We need to specify the column
34
to be used for filling the level. We open the column name and it will show all
35
the fields from tables defined in the hierarchy. We select name from the
38
.. i18n: .. image:: images/level1.png
42
.. image:: images/level1.png
45
.. i18n: We want more level for displaying the name of the products. In the column name
46
.. i18n: we will select the column name from the product_template. The main thing is to
47
.. i18n: change the sequence to 2. This will show the prodcuts category wise on the
51
We want more level for displaying the name of the products. In the column name
52
we will select the column name from the product_template. The main thing is to
53
change the sequence to 2. This will show the prodcuts category wise on the
56
.. i18n: .. image:: images/level1.png
60
.. image:: images/level1.png