How do you tag a range of years so it is iXBRL compatible?
AnsweredWe disclose various years (e.g. 2020, etc) in a couple places in our document with a extension tags (for example, we have a contingent consideration disclosure that includes projected years of payment and a range of 2020 - 2026).
I've always had my value type set to "period", period type "duration" and my extension tag as a "xbrli:gYearItemType" and it has always worked without issue.
I'm in the process of converting to iXBRL and I'm getting the following critical error: Fact has incorrect or missing fact value, date/date range, or unit (NonNumeric Fact: ext_ExtendedTagName attribute format type QName value error: , pattern mismatch)
Anyone know what this means or how to fix it?
I've tried playing around a bit and I'm not getting anywhere. I have a feeling it has to do with how my extended tag is setup and I may need to deprecate the concept & create a new one that can sustain different fact properties. But before I do, I want to make sure I have all the information to set it up appropriately as I have these types of tags in a few places.
Thanks in advance!
I've always had my value type set to "period", period type "duration" and my extension tag as a "xbrli:gYearItemType" and it has always worked without issue.
I'm in the process of converting to iXBRL and I'm getting the following critical error: Fact has incorrect or missing fact value, date/date range, or unit (NonNumeric Fact: ext_ExtendedTagName attribute format type QName value error: , pattern mismatch)
Anyone know what this means or how to fix it?
I've tried playing around a bit and I'm not getting anywhere. I have a feeling it has to do with how my extended tag is setup and I may need to deprecate the concept & create a new one that can sustain different fact properties. But before I do, I want to make sure I have all the information to set it up appropriately as I have these types of tags in a few places.
Thanks in advance!
0
-
Hi Jess! Are you tagging the range "2020 - 2026" or each year individually? 0
We tag each year individual and dimensionalize with a min/max members and range axis.
Any thoughts?0
Hmmm...seems like that should work. Is the value format set as "Date" and only the year CCYY is used? If you right click on the validation error, does it provide any further information, like a reference to the Edgar Filing Manual?0
How would you format 2020 using CCYY? Would it be CCYY2020 in the source cell?
I think this could be my issue since its not formatted like we do other time periods. For example we disclosure "5.28 years" as P5Y3M10D in the source.
There isn't a reference to the edgar filing manual, unfortunately!0
It would just need to be the year 2020, not 1/1/2020 or January 2020 in the source cell, etc. Then the value format would be Date and not Period, Accounting, Number, etc. 0
Nope - no luck! I think it has to do with how we've created the extension tag. 0
Interesting! 0
Jess - I believe the old format of "P5Y3M10D" for example, isn't used for iXBRL. ... 0
Great conversation all! You are simply amazing :)
To piggy back off Trisha, in Wdesk, you would want to make sure the links are formatted as a "Date". This should help clear the error you are seeing.
If you are still seeing the error, I would recommend reaching out to your PSM to take a closer look. And if you don’t have a PSM, your CSM can help arrange something with our Professional Services team to get you the assistance you need. Lastly, I'll add that tagging dates is optional, so you do have the option not to tag this particular disclosure.
Let me know what questions you have in the meantime. Thanks again and happy Thursday!0Please sign in to leave a comment.
Comments
9 comments