Is there something that is user-friendly that can be defined with a visual interface instead of an MDX statement?

DefineCalc is not a replacement for user-defined consolidations because an MDX statement is not a substitute for something that can easily be done visually on the fly. Half of my director's views that no longer work in PAW or PAfE and this is being considered a dealbreaker for moving off of Perspectives. 

At this point, we cannot embrace PAfE without a replacement for this functionality that doesn't require an MDX statement. 

I am the first person to say that PAfE falls short in many usability aspects. However, you don't need to manually write "DefineCalc" statements. You can add calculations from the right click menu in most of the new interfaces. This is not well exposed in CustomReports, but on the others it is. 

There was a simiar comment about TM1VAL the other day. The use of MDX is explicit in DEFINECALC, TM1SET, TM1VAL and you can build in references to predefined MDX statements and build a simple dropdown to select from a list. Universal Reports is all about MDX.  Cube Views and  Explorations and the set editor have MDX just below the surface. I suggest teaching the users to make their selections in the Set Editor and then use the generated MDX in the formulae. It's not the same as a user generated function but it will get them where they need to be. It woukd be nice to raise the SET Editor from within the custom function (And return the generated MDX)  but that's not how it is.

we are also exploring the Universal Reports, but in order to convert all our Perspective Active Forms, I was hoping IBM will create some kind of tool to do at least half of the job for us

is anyone aware of any utility that can help to migrate Perspective Reports to Universal Reports?

If the dimension is in Context, then one could open it is Subset editor, select the required elements, close editor. Right Click and select SUM. Not as flexible but does meet some of the requirements. DefineCalc is another option - though we found a bug where by it does not work if dimension name has more than 2 periods (.) in it .