Image naming in Next-Gen Filings
CompletedHi Mike - Can you please provide an update on the status of the below post? It is closed for comments.
Unless this issue has been fixed, this will be the third filing in a row where the names of our pie charts are a mess. We would really like this fixed by year-end so we can name them "chart1", "chart2" instead of "chart-db19aq12f63948is88f1.jpg"
Thanks!
Matt
-
Official comment
I have great news, Matt!
A recent release to Workiva has now made available the ability to rename images in your files, such as generated Charts. Thanks so much for your patience along the way. Give us a holler if you have any questions, or need anything else. Happy filings in the meantime!
Hi Matt!
Did some quick checking on that feature request and unfortunately I don't have great news. While we would like to implement it at some point, as of right now it is not prioritized for this year. This is in part due to the complexities around accuracies with the EDGAR filing process. That being said, I've definitely passed your feedback along for further consideration. Let me know what questions you have or if you need anything else. Thanks :)
0Hi Mike - I'm still having issues with chart names. I changed the name of my generated charts to "chart1", "chart2", etc. but when I went to test file, there were a bunch of errors saying that the "the document references "chart-23498fdfgdfgfh7.jpg" and it couldn't be found". Then, I re-generate XBRL to fix the issue and the charts are automatically re-named to jibberish. Any help?
0Hi Matthew,
I was able to get some info on what you are seeing. There's a limitation currently for XBRL generations, which ignores the image filename and renames it. Unfortunately there is no way as of yet to change that as of yet, though I've shared your experience with the team and will get you feedback logged.
Sorry I couldn't provide any better news. Let me know what questions you have. Thanks for your contributions and happy Friday!
0Hi Mike - Any update on this issue? We'd really like to have this fixed.
0Please sign in to leave a comment.
Comments
5 comments