Hello @ANIL2025
I was using your calculated field reference and could get the same error for my sample data.
I was running into “encountered an overflow error when performing lad/ln function”, thus I included another ifelse in my calculation to address below zero values (you can change it to your previous value if that was working fine):
My final Calc_Product_Fund looked like:
runningSum( ln(abs(ifelse( (sum({Weighted Revenue}))>0, (sum({Weighted Revenue})),1))), [Date ASC]) *
ifelse(runningMin (abs(sum({Forecasted Monthly Revenue})),[Date ASC])=0,0,1) *
ifelse (runningSum( sum(ifelse({Weighted Revenue}<0,1,0)), [Date ASC])%2=0,1,-1)
However when calculating Calc_Product_fund_last_value, I was running into the same error like yours → “we encountered an error trying to save your calculated field”, possibly because of aggregations:
Then I tried using all of it together →
lag((runningSum( ln(abs(ifelse( (sum({Weighted Revenue}))>0, (sum({Weighted Revenue})),1))), [Date ASC]) *
ifelse(runningMin (abs(sum({Forecasted Monthly Revenue})),[Date ASC])=0,0,1) *
ifelse (runningSum( sum(ifelse({Weighted Revenue}<0,1,0)), [Date ASC])%2=0,1,-1))
,[Date ASC]
,1
)
And the above worked for me, it could fetch me the previous value.
Please note my {Weighted Revenue}/{Forecasted Monthly Revenue} are direct fields from the dataset and not CFs.
This may be due to aggregations in your Calc_product_fund, further nesting it in lag function might be causing this error.
Hope this helps.
If you are still seeing the errors, I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf.
Thanks.