Comment 2 for bug 494426

Said, that is absolutely correct - the 1-dimension limit is not just a "restriction", this is what has been developed based on functional requirements of FLUID and early-GHO. We didn't have any need to support more that 1 additional dimension on data entry (it is kind of difficult to show 3-dimensional tables in Web data-entry forms), and we didn't have the budget to develop features that were not in the functional scope of the project.

The code structure allows the code to be extended to support more dimension (this is the part of DynFormsDAO / DynFormsDTO where we handle either LOCATIONS or MEASURE_DIMENSION_...), but, as you correctly observed, the amount of work is not trivial.

If we would put a reasonable upper limit on the number of supported dimension, I'd estimate the effort on 10-15 person-days (with proper testing); if we'd need to support an unlimited number of dimensions, the estimate would be visibly higher (I would have to do some research to figure it out).