Quick OneStream Rule Behavior Check – O#Top Returning O#Import Value?

Hi Team,

Quick question — has anyone else encountered this behavior in rule logic?

I’m working with a standard api.Data.GetDataCell(...) call that includes the O#Top member in the POV. Here's the line I'm using:

Dim baseValue As Decimal = api.Data.GetDataCell("C#Local:A#1104000000:F#CLO:O#Top:I#Top:U1#Top:U2#Top:U3#Top:U4#Top:U5#Top:U6#Top:U7#Top:U8#Top").CellAmount.

BRApi.ErrorLog.LogMessage(si, baseValue)

On the Cube View, this correctly returns -501 under O#Top.
However, when I log the value in the rule using:

-          It outputs the value from O#Import, not the aggregated O#Top result I expected.

This rule worked flawlessly for 3 years until now on Version 7.4.

As a workaround, I manually aggregated the base origin members in the rule, which produced the expected result.

However, I’m still unclear why O#Top didn’t aggregate properly in this case, given that it functions as expected in Cube Views. I checked and compared with several other apps, including Golfstream, in which this rule worked. 

Environment:

• This behavior was observed in 7.4.
• After upgrading to version 8.4, the issue was resolved.
• I’d like to understand what may have caused this inconsistency, particularly:
• Could a bug affect the Origin dimension, which was resolved in 8.4?
• Has anyone experienced this behavior before?

Appreciate any insights or similar experiences the community can share!