We currently have zero suppression, but I would like to propose suppress blank/null, so that summations is not suppressed even if the sum total is zero. Currently I can easily miss data that sums to zero
Expose the PHP functions in the spreadsheet functions
for instance I want to compare 2 ranges, I have a function: function arrayintersect($array1,$array2){ return array_intersect($array1,$array2);} this would be helpful if the array_intersect function would be directly accessible from the spreadsheet...
Version Blending / Forecast Splashing: Centralized HOLD
I would like to be able to manipulate "HOLD" using rules and Integrator. Currently the users needs to use the Planning Assistant / right click in UI. But general hold is needed for Forecast scenario's like 3+9 to ensure splash works correctly, and...
The concatenate.range function is awesome! This would be even more awesome to have the opposite, say, "split.range", that would allow splitting a string regarding a delimiter (like PHP's explode(<string>,<delimiter>). This would return...
the design of the method value() in the macro engine should be improved. It returns a different type depending of the arguments passed to the range() property. Example: activesheet()->range('A1')->value => returns a string // this is corr...
Allow pasting array formulas in Macro Engine, using a method "FormulaArray" like in VBA, e.g.: activesheet()->range('D3:G3')->formulaArray = "=TRANSPOSE(C4:C7)";
Currently we have a very complex model that is depending a lot on the SVS server. But we noticed that with the amount of interaction between the spreadsheet and SVS server sometimes the SVS server "freezes". In order to solve this we must restart ...
Since chromebooks / pixelbooks are becoming popular, make jedox compatible with Chrome OS. Currenlty jedox is very glitchy in pixelbooks e.g. not able to scroll Thanks
I would like to propose being able to make user defined queries for rule templates. I'm thinking exposing it from the integrator which could generate the query, and then expose the result to the rules engine. This would create a much more flexible...