0

Execution Solve Order Explanation

Morning all, 

Question around formulates and solve orders, we have had a couple of situations recently that has caused some issues that was resolved by adjusting the solve order on formulates. This worked however may present future challenges if these measures are then used again in another formulate.

Below is the only documentation i can find

Found Here 

 

Could someone explain if there is a best practice or shed some light on the following

in terms of default sort orders when you dont set them

Presumably Custom Columns are prioritised, followed by formulates then in-report quick calcs / custom members?

 

Example.

We have a formulate to generate a percent 

This is then shown by year with a deduction for 2026-2025

 This works WITH the sort orders applied, if i remove the solve orders it will calculate this incorrectly

 

We fixed this with the solve order of 1 on margin and 2 on the 2025 2026 element, but the issue is that we now have formulates with solve orders applied that may or may not be set correctly for other formulates.

Would love to hear some thoughts, feedback, best practices on this if anyone else has them.

2 replies

null
    • Customer Solutions Architect
    • Moshe_Yossef
    • 13 hrs ago
    • Reported - view

    Hi  ,

    Here is the thing:
    when you have calculations relying one on the other with no solve order applied - Pyramid's query engine has an internal logic for the solve order.

    In your case – pyramid did the growth percentage calculation first, in other words, the sales in the margin  calculation were (sales for 2026) – (sales 2025), and the WAC sales cost were also the difference between the years.

    Then Pyramid calculated the margin on the differences between the years.

    Once you applied solve order you basically instructed Pyramid to do things in a different order – the margin was first calculated for 2026, then for 2025, and the annual growth was calculated that way.

    As long as your other calculations do not rely on one another – it doesn’t look like you will run into problems with it.

    As a best practice I would use bigger numbers for solve order (100, 200) so in case things get complicated down the road I can easily find room for other calculations in between solve orders.

    I hope this helps – feel free to add questions if you have.

    Moshe

    • VP Product Management
    • Ian_Macdonald
    • 8 hrs ago
    • Reported - view

    Hi 

    Excel has the same problem / solution, https://excelk.com/en/solve-order-en/ 

    Hope that helps.

    Ian

Login to reply

Content aside

  • Status Answered
  • 8 hrs agoLast active
  • 2Replies
  • 20Views
  • 3 Following