Replies: 1 comment 1 reply
-
Could you show us the steps you take and/or share a report that could be used to reproduce this? I assume just viewing the finding group and the list of findings in them and then select "Excel Export" from the Download button? I just did some tests with a finding group a created via bulk edit in a Test. The Excel export seems to work for me without problems. Could you also provide the version of Defect Dojo you're at? That would allow we to check the line number to get a clue of the error. In recent versions I don't see any obvious problems in line 1009 and the lines around that. Can you include the full traceback of the error (if present in the logs, could be that they are only logged at DEBUG level). |
Beta Was this translation helpful? Give feedback.
-
Wondering if anyone has any suggestions, we are unable to export finding groups to excel, csv or to a report. When we try there are thousands of errors spammed into the uwsgi container log. Here is an example of trying to export to Excel.
ERROR [dojo.reports.views:1009] Error in attribute: Cannot convert <Finding_Group: Findings in: ejs> to Excel
ERROR [dojo.reports.views:1009] Error in attribute: Cannot convert <Finding_Group: Findings in: extend> to Excel
ERROR [dojo.reports.views:1009] Error in attribute: Cannot convert <Finding_Group: Findings in: extend> to Excel
ERROR [dojo.reports.views:1009] Error in attribute: Cannot convert <Finding_Group: Findings in: extend> to Excel
ERROR [dojo.reports.views:1009] Error in attribute: Cannot convert <Finding_Group: Findings in: graphql-upload> to Excel
ERROR [dojo.reports.views:1009] Error in attribute: Cannot convert <Finding_Group: Findings in: graphql-upload> to Excel
ERROR [dojo.reports.views:1009] Error in attribute: Cannot convert <Finding_Group: Findings in: json-schema> to Excel
ERROR [dojo.reports.views:1009] Error in attribute: Cannot convert <Finding_Group: Findings in: opener> to Excel
I have tried importing the exact same findings, creating a finding group and exporting on a dev environment and it always works, I can't figure out what is wrong with the prod env.
I'm thinking maybe its database related but I dont know what I would check for issues.
Any suggestions, thanks for anyone who takes the time to look into it.
Beta Was this translation helpful? Give feedback.
All reactions