How to add attributes to fact?

[BartDelouvroy]

Hi,

I want to use your library to create XBRL files for EBA reports (based on DPM - data point model) .
A fact consists of attributes unitRef, decimals, contextRef which are covered by the method AddFact.
However it also needs some additional attributes like in below example:

<eba_met:mi170 unitRef="uGBP" decimals="-3" model:table="C_40.00" model:x="070" model:y="030" contextRef="c13">6238000</eba_met:mi170>

My question: how can I add attributes like 'model:table' etc?

Kind regards,
Bart.

[dgm9704]

I’ll take a look at this and get back to you!

[dgm9704]

Hi!
Bad news I'm afraid.
The way the library is built, means that handling additional attributes
in the same way as the normal ones is not supported.

The main reason is (there are others also):
Any facts with the same metric, context, value, unit and decimals
are considered "identical" as per the taxonomy (and DPM)
Additional attributes would/could create facts that are duplicate
in that way, but different in a way that would require them both to be
represented in a file.
This would be true eg. for facts that are modeled in more than table
in a given entrypoint (module).
That report file could then violate the taxonomy, Filing Rules,
or some other validation.

There is a possible work-around however:
That is to create your report normally, but instead of writing it to file,
you would call Instance.ToXmlDocument(), manipulate the returned XmlDocument
by adding any necessary attributes, and finally writing that XmlDocument
to file.

Having said all this, I confess I am very curious:
I handle lots of XBRL files coming and going in my day job, also those
that are based on the EBA DPM, and I haven't seen any need for additional
attributes for facts in succesful reporting.

EBA releases different test and reference instances for each DPM/taxonomy version.
I vaguely remember that they did put out some files that still had some of their
internal modeling data still "attached" by mistake.
(And afterwards released the corrected files without this extra info)
Now, please don't take offense, but could it be that you might be working
with those incorrect test files, and trying to reproduce them?

If that is the case then simply downloading the newest test files
would perhaps help you or clarify the issue?
If not, then I will gladly try to figure a way around this problem.

[BartDelouvroy]

Hi,

Despite my 10 years in banking industry I'm totally new to XBRL.
You are totally right. I started experimenting with XBRL for EBA reports and took the XBRL samples some 3 months ago. Following your suggestion, I just downloaded them again and it now contains a readme file with errata containing the text "Originally provided instance files mistakenly contained model:table, model:x, model:y, model:z etc attributes on fact values.". The new samples do not contain these attributes anymore.

Glad that this can be categorized as a non-issue. Thanks a lot for pointing me in the right direction!

Kind regards,
Bart.

[dgm9704]

I'm glad I could help, I know first hand that there is a somewhat steep learning curve to XBRL. Please feel free to ask if there are any other problems, either with the library, or even XBRL reporting in general.

[BartDelouvroy]

<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} .MsoChpDefault {mso-style-type:export-only;} @page WordSection1 {size:8.5in 11.0in; margin:70.85pt 70.85pt 70.85pt 70.85pt;} div.WordSection1 {page:WordSection1;} -->Hi John, I hope you are well. This week we are running tests to generate xbrl for EBA and ran into an issue:   This happens the moment of serialization of the instance into xml document: XmlDocument xbrldoc = instance.ToXmlDocument();             Trying all day long to get it resolved.It’s not related to the namespaces at the top because if I skip creation of facts it works.If I take 1 fact away it works again. Also not sure which one as removing nth fact seems to work , but also works when putting this back and removing another one. I can’t get hold on why this happens. Do you have an idea? Kind regards,Bart. Sent from Mail for Windows 10 From: John NordbergSent: Friday, January 4, 2019 1:03 PMTo: dgm9704/XoxoCc: BartDelouvroy; State changeSubject: Re: [dgm9704/Xoxo] How to add attributes to fact? (#63) I'm glad I could help, I know first hand that there is a somewhat steep learning curve to XBRL. Please feel free to ask if there are any other problems, either with the library, or even XBRL reporting in general.—You are receiving this because you modified the open/close state.Reply to this email directly, view it on GitHub, or mute the thread. 

[dgm9704]

Hello.
Could you provide the actual error message if there is one? You can leave out any information that is private of course.
What you could try is to serialize the same Instance that gives the error with .ToFile and see what that produces. If that works as it should then the problem would be in the ToXmlDocument or related code.

[BartDelouvroy]

<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} .MsoChpDefault {mso-style-type:export-only;} @page WordSection1 {size:8.5in 11.0in; margin:70.85pt 70.85pt 70.85pt 70.85pt;} div.WordSection1 {page:WordSection1;} -->Hi John, We tried to save as file but then it left out the part that gave trouble. The error now got solved because I found the reason: either the metric or the dimensions in the scenario were empty I added checks before executing AddFact (on metric and scenario) and log the number of excluded facts to give indication to user: if (!scenario.HasMembers){                        exlcudedFacts++;                        continue;}  instance.AddFact(scenario, Metric, UnitRef, Decimals, FactValue);  So, basically it was a data quality issue. Kind regards,Bart. Sent from Mail for Windows 10 From: John NordbergSent: Saturday, March 28, 2020 10:19 AMTo: dgm9704/XoxoCc: BartDelouvroy; State changeSubject: Re: [dgm9704/Xoxo] How to add attributes to fact? (#63) Hello.Could you provide the actual error message if there is one? You can leave out any information that is private of course.What you could try is to serialize the same Instance that gives the error with .ToFile and see what that produces. If that works as it should then the problem would be in the ToXmlDocument or related code.—You are receiving this because you modified the open/close state.Reply to this email directly, view it on GitHub, or unsubscribe.