Hi,

thanks for these hints -, seems like another bug in MS surroundings...

Hi, I got some support from the programmers of the component- , now it works. An example query for a 3d pie chart:

(SELECT '' AS `color`, 0 AS `isSliced`, 'Dauer 1' AS `label`, ((SUM(`dauer_z1`) / SUM(`dauer_ges`)) * 100) AS `label` FROM `#__trlog`) UNION
(SELECT '' AS `color`, 0 AS `isSliced`, 'Dauer 2' AS `label`, ((SUM(`dauer_z2`) / SUM(`dauer_ges`)) * 100) AS `label` FROM `#__trlog`) UNION
(SELECT '' AS `color`, 0 AS `isSliced`, 'Dauer 3' AS `label`, ((SUM(`dauer_z3`) / SUM(`dauer_ges`)) * 100) AS `label` FROM `#__trlog`) UNION
(SELECT '' AS `color`, 0 AS `isSliced`, 'Dauer 4' AS `label`, ((SUM(`dauer_z4`) / SUM(`dauer_ges`)) * 100) AS `label` FROM `#__trlog`) UNION
(SELECT '' AS `color`, 0 AS `isSliced`, 'Dauer 5' AS `label`, ((SUM(`dauer_z5`) / SUM(`dauer_ges`)) * 100) AS `label` FROM `#__trlog`)


So basically you have to create a "table" with your query that has all columns like label, column, value etc. like the backend settings need to done for each single row. Then, with UNION you can create a the next row!

Hope, this helps you too!

.. I think it's related to the need to set up all exaxtly (number and order) like the backend fields, you must also have the correct version of bar etc. to match your query set-up with what's needed. For example the "colour code" field in the backend must be included in your Select ..... data base query (at least it looks like this from the examples in the help site), which is really not what it's normally like and I can't make it work until now.

totallnet wrote:


..I have the same problems when trying to use the data base query instead of putting manually values into fields. When clicking on "try" each time only one row remains, all others vanish. Any help anyone much appreciated...