we’ve just started using embedded dashboards to allow the downloading tables and I’ve noticed a couple of inconsistencies.
We have some monetary amounts and so I have formatted them as 12345.67 numbers (currency is no good as we have to support multiple currencies), in the analysis these show up numbers as 1.20 correctly but in the CSV file we don’t get the 2 decimal points (we get 1.2), the Excel version does have the 2 decimal points.
The CSV version also doesn’t export fields as “null” where as the Excel version does export them as “null” (I’d rather not have to until the option to populate with null on every column in the table and onscreen I actually don’t mind it but it should be consistent whichever way it is).
thanks for the response, the downloaded CSV files were viewed in a text viewer, what I didn’t notice is the data also doesn’t have the extra decimal place in Excel - it’s just formatted to look right. What’s actually going on is the underlying query is not keeping the decimal places so I guess I’ll need to fix that and force it to two decimal places.
The nulls/empty strings inconsistency is still there, I’m happy to go and (un)tick the box about nulls but it looks like I have to do that on every field in the table, is there a setting that applies across the table rather than having to do that at the filed level?
Hi @nlp - Thanks. Can you please share sample data for the null/empty string so that issue can be understandable in detail. I am expecting null or empty should be behave same as excel and notepad and csv.
If there is some differences, we can highlight to QS team.
I’ll try and create something that doesn’t have any sensitive data in it to show it, I have done some googling on CSVs and their treatment of nulls and it seems it’s pretty common to use empty strings so perhaps it’s expected (the RFC is not very specific).
I’m not going to worry to much at the moment as I can live with it, but thanks for the pointers and clarifications.