Transaction List Property Formula Timing Out

Question

We have several transaction list properties with formulas that are now timing out and we are concerned we have hit a ceiling.

The transaction list is just over 6 Million rows and over 60 properties, many of which are calculations.

The formula is a simple as i can make it.
ifblank('Opp Trx'.OWNER_ID.GLOBAL_DIVISION, 'Global Division'."No Segment")

Is the transaction list simply too big or is there a more efficient formula to be used?

oredsson · Accepted Answer

I don’t think there is much to do on the formula itself. The best solution is probably to try to do fix this before the import to the transaction list so that values for division is “No Segment” instead of blank in the source data.
An alternative solution is to split your transaction list somehow. If you for example have transactions for your actuals, you can split it in one list for all years before 2026 and one list for 2026 and forward. Then your import will just trigger recalculations in one of your list where you have much fewer rows.

Dhiraj Khivsara · Answer

One more angle: at 6M rows the problem is less the formula and more that it runs on every row. I’d move the logic off the transaction list.Put the default on the Owner dimension. Make Global Division on Owner never blank (the IFBLANK goes there, on a few thousand owners instead of 6M rows).Drop the property from the list. In your metrics, aggregate the transactions by Owner first, then map Owner to Global Division at metric level. The result is the same and the mapping runs on a much smaller set.Apply the same test to the other 60 properties. Anything that is a lookup through a dimension can usually live on the dimension or in a metric.