Hi, export via XLSX, CSV (formatted) is giving wro...
# gooddata-cloud
m
Hi, export via XLSX, CSV (formatted) is giving wrong numbers in compare what I see in report and getting from raw csv export.
m
Hi Marketa, im happy to help, could you please share with us the direct link to the insight/dashboard. Is this happening only in one dashboard/insight?
m
https://cruxo.cloud.gooddata.com/analyze/#/5971b507ad704396af215edd4451d905/46a79c2e-785d-40c3-af6a-f5eb4a2a2d83/edit - currently I am observing it in one insight, but I didnt test it in different one
👀 1
m
Hi Marketa, first of all thank you for your time. After long testing, with many different combination including, filter using differing attributes/values and date in different ways. I figured out the issue , it seems it is related (a priori) with the number of columns when the Rollout Total or SUM for All columns is applied. Now, I will need to test it on my end to see if I can reproduce the issue and report it as a bug or as expected. As a workaround, for now, if works for you, you can stop using the Rollout total for all columns, and the values in the last row will be correct. I want to offer our apologies for this. Once again thank you for your time, I will keep you updated on this.
Hello Marketa, I have an update. I manage to reproduce the issue and the cause is related with the number of columns (data/metric), so if you have up to 100 columns of data, it will show right values in the last row, but if you have, for example 101, the error will appear.. always in the column number 101. Thus I am reporting this as a bug, right now I do not have any ETA but I will keep you update. Additionally, can you let us to know how critical is this? Thank you once more for bringing this to us.
m
I have every monday automatic report from this table to our client, and last time I had to fix it manually, and also the next step - is not possible to make - and that together took me last time 4h to fix and send correctly.
gratitude thank you 1
m
Hi Marketa, I will pass your message, our engineers are actually looking into this. Thank you for your patience.
m
Hi @Mauricio Cabezas any news?
j
Hi Markéta, according to our engineering, the current ETA is up to two weeks. There is not much that can be done by Support to speed this process up. However, if you wish, you can escalate the issue with your account owner @Pavel Doubek (pavel.doubek@gooddata.com). Otherwise, we will let you know once the problem is fixed. Thank you for your understanding and apologies for the inconvenience.
🙏 1
m
Hi Marketa, I have some good news! It seems that the issue is fixed. I went ahead and impersonated your environment, and I can see that all the values are displayed correctly in the downloaded file. Could you please confirm this as well?
🙌 1
m
Yes it is fixed now! Thank you! 🙂
I just noticed that 1 line is moved as well 😬
👀 1
j
Hi Marketa, I'm sorry but I'm not sure if I understand the issue solely from this screenshot. Also it looks that it's not related original thread? Anyway, maybe it would be better if you send us screenshot how the specific table looks like in the UI so we can compare with this export?
m
I am sending how it is, vs. what I would expect, it happening during python API call for exporting a pdf from dashboard. Also adding screenshot of good data table.
j
Hi Marketa, could you please send a link to the table where we can test this?
m
Hello Marketa, could you please confirm which dashboard or visualitation is by sending a direct link? Also, can you please elaborate a bit more how and when you see the issue, and also what is the issue itself? you mentioned a Python API call, can you explain to us, specifically, which call?, is this happening if you export directly in the UI? or using the simple API call (without Python). Finally, with '1 line is moved...' I believe you mean that the first date column (column E) on the first line, should be in the column C, no?