XBRL error when copy/pasting checkbox from template
AnsweredWhen I follow the template for the Boolean Item type (copied/pasted the appropriate box from the template to the applicable field for tagging our cover page and entered in/formatted as text) I get the 'displayed value for this fact is incompatible with iXBRL requirements' validation error. Please advice. Thanks!
-
Official comment
Hi Abraham!
Good news, I have answers for you for both items. Its truly your lucky day :)
Yes, the Arial Unicode MS font checkbox items were released to Wdesk this week, but they are found in the Symbols and not in the font menu. To access, go to Edit > Insert > Symbol and then change the font drop-down to "Arial Unicode MS". Then, locate the box you need and select Insert. Here's how the new window looks and the checkboxes found there:
Essentially its the same process you probably used before for inserting Wingdings checkboxes on your cover page, but in this case you are using Arial Unicode MS.
Regarding your second question, the updates to the Help page were mostly to provide an off-calendar template in addition to the existing standard year end version. If you have that version, you are ok to keep using it and no need to re-import anything.
Hope that helps answer your questions. Holler if you need anything else. Tanks again for your contributions and have an excellent weekend!Hi GG!
Thanks again for the question. I've attempted to follow your same steps but do not receive the same error. One thing to try is copying and pasting the the desired checkbox in again and reapplying the XBRL to see if that addresses it. If you still receive this same error it might be worth contacting your CSM or PSM, or our 24/7 Support Team at 1.800.706.6526 to see if they can take a closer look.
Sorry I couldn't be of more help. Let me know what additional questions you have for me, or if you need anything else.0Hi Mike,
At the FAST Act webinar, they mentioned there would be a release with the Arial Unicode MS font so we could use the right checkboxes. Is this still happening, or should we just use the ones in the sample template? Those ones are in Times New Roman. Also I noticed the Help page was updated since I downloaded the templates - should I re-download them?0
Do you have to be on the next gen platform to see this? I'm currently not so I have to use the copy/paste from template method (which works for me at the moment).0You do not need to be in next gen to see the option. It should be available in classic Documents. In my window, its above Myriad Pro. Hmm... let me dig a little deeper here. 0Is there a requirement to tag the box in the document cover? Can we tag in the phantom and indicate True or False? 0Perfect! Thank you, Mike! 0I'm having the same issue - I don't see the the Arial Unicode MS option at all. Please advise if you find anything. 0Moving to its own conversation to then combine with an existing convo of the same topic that is currently answered. Please reference the new conversation here: Is there a requirement to tag the checkbox on the cover? 0Just a follow-up. I tried the oldest IT trick in the book - logged out and logged back in. I also closed my browser. It seemed to work for me. I tend to keep my browser / Wdesk up basically non-stop throughout my 10Q process so if they pushed this out [relatively] recently I probably needed to get out to allow for the update. 0Good call Ethan. You definitely want to make sure you are loading the most up-to-date instance of Wdesk. Sometimes your browser can still have the older version cached, so a logout, restart and/or clearing your browser's cache can do the trick. 0
Thanks Ethan/Mike, restarting worked for me as well.0I'm getting data validation warnings when I run a section validation on the cover page. My boolean tags (and some others) has the following error message - "Fact has an incorrect or missing fact value, date/date range, or unit (DocumentQuarterlyReport type boolean value error:"
I don't think any of these are filing critical, but I like my document clean.
Thanks,
Ethan0Please sign in to leave a comment.
Comments
13 comments