Column value gives error the moment I add @Round function

HCL Domino Domino Forum
1

I created a view, whereby I have a column called year end projection, which is the value of actual to date + forecast up to financial year end (i.e 1 Apr to 31 March following year).

I have the following formula for this column, called YEP, with the last line is:

@If(B_Status=“Actual” & B_Period=“”;l;za). it works fine.

However, I got this error message the moment I incorporated the @Round formula into view:

“Error, incorrect data type for operator or function, number expected.”

a=@If( @Month(@Now)-1= 3 ;((B_Qtr2CY+B_Qtr3CY+B_Qtr4CY+B_Qtr1CY)/1000);0);

b:=@If(@Month(@Now)-1= 2 ;(B_Qtr2CY+B_Qtr3CY+B_Qtr4CY+B_CYJan+B_CYFeb)/1000;a);

c:=@If(@Month(@Now)-1= 1 ;(B_Qtr2CY+B_Qtr3CY+B_Qtr4CY+B_CYJan)/1000;b);

d:=@If(@Month(@Now)-1= 0 ;(B_Qtr2CY+B_Qtr3CY+B_Qtr4CY)/1000;c);

e:=@If(@Month(@Now)-1= 11;(B_Qtr2CY+B_Qtr3CY+B_CYOct+B_CYSep)/1000;d);

f:=@If(@Month(@Now)-1= 10;(B_Qtr2CY+B_Qtr3CY+B_CYOct)/1000;e);

g:=@If(@Month(@Now)-1= 9;(B_Qtr2CY+B_Qtr3CY)/1000;f);

h:=@If(@Month(@Now)-1= 8;(B_Qtr2CY+B_CYJul+B_CYAug)/1000;g);

i:=@If(@Month(@Now)-1= 7;(B_Qtr2CY+B_CYJul)/1000;h);

j:=@If(@Month(@Now)-1= 6;(B_Qtr2CY)/1000;i);

k:=@If(@Month(@Now)-1= 5;(B_CYApr+B_CYMay)/1000;j);

l:=@If(@Month(@Now)-1= 4;(B_CYApr)/1000;k);

za:=@If(B_Status=“Actual” & B_Period!=0 ;B_Act/1000;0);

@If(B_Status=“Actual” & B_Period=“”;@Round(l,1);@Round(za,1))

Very much appreciate any help given.

2

Subject: Column value gives error the moment I add @Round function

Hi,

try this

@If(B_Status=“Actual” & B_Period=“”;@Round(@ToNumber(l),1);@Round(@ToNumber(za),1))

Regards

Rajiv

3

Subject: RE: Column value gives error the moment I add @Round function

Ap Kasei Hei, Rajiv,

Thanks, it works! Can you share to me some insights, why it is was interpreted as text in the first place (that’s the reason for the error message right?).

Thank you.

4

Subject: RE: Column value gives error the moment I add @Round function

hi Will Smith2,mein theek hu…

Yes, u r right it was interpreting the data as text and was the reason for the error

am not sure of why it interpreted as text but, i think internal (implicit) typecasting resulted into it…

Regards

Rajiv