hi @Chere-Oracle i think i get that you are saying, but, why does BI server seemingly move calc to in memory and adding the double float and no longer calculating on the DB when the measures in the RPD come from there? What am is asking is why do i need to do this cast to int on those raw columns when i pull in a dataset?…

hi @Chere-Oracle the two fact columns are NUMBER(18,2) in Db and come into front end OAS as number in subject area? does that help?

Thanks @Chere-Oracle and @RVohra for your responses. Certainly @Chere-Oracle casting to INT and then setting filter <> 0 works ok. But the reason for the question is more the mechanics of why BI server appears to force the double floating point type for RPD columns that are 100% number in the RPD, simply because there is a…

I think it would be great if you could get this OOTB. Appreciate in Usage tracking in OAS there are some DV type objects of visual analyser "Dim - Logical SQL"."Query Type" = Visual Analyzer but its limited. We were able to query classic agents runs and also BIP schedules but we had to query the BIPLATFORM.CSS_FILE_CONTENT…

https://community.oracle.com/products/oracleanalytics/discussion/comment/64885#Comment_64885 we have tracked this down as the actual reason for this behaviour, it might be useful for other OAS users https://blogs.oracle.com/analytics/post/oracle-analytics-dashboard-rendering-mode-options