Arelle validations vs DPM 2.0

[Francisco Lelewell]

Hello,

I'm trying to use arelle to generate tables html, and to get the validations log.

Everything seems to be ok, with my current set up for XBRL-xml and mapping with DPM 1.0.

However, when moving to XBRL-csv, and using the DPM 2.0 mapping, and respective taxonomies I encounter a problem. 

I can still generate the tables and validations, but the validations seem to be with the old mapping format (might be my error on understanding the mapping system)

My question are:

• Is arelle ready for the DPM 2.0, mapping?
• Is arelle ready for XBRL-csv reporting?
• Do you have any tips on understanding the dpm 2.0 mapping, and how to relate it to the arelle validations?
  

Thank you in advance,

[Austin Matherne]

Hi,

To answer your specific questions:

1. Is Arelle ready for DPM 2.0 mapping? Core XBRL support yes, but no DPM 2.0 specific logic. The old EBA plugin won't work correctly with DPM 2.0 if you're trying to use it.
2. Is Arelle ready for XBRL-CSV reporting? Yes, it's certified by XBRL International with xBRL-CSV support.
3. Tips for DPM 2.0 mapping and Arelle validations? I'd recommend relying on Arelle's core validation (what's embedded in the taxonomy itself as formulas) rather than the old EBA plugin. If you're getting specific validation errors that seem wrong, could you share an example? That would help clarify whether it's a plugin issue or something else.

Arelle doesn't have specific DPM 2.0 support beyond standard XBRL specifications. There's an old validate/EBA plugin, but it's unmaintained and was written for DPM 1.0 era taxonomies. If you're using that plugin, it would explain why your validations appear to use the old mapping format, the plugin likely has hardcoded assumptions about namespace patterns, validation rule structures, and filing indicator handling that don't align with the DPM 2.0 architecture.

[Francisco Lelewell]

Hi Austin,

Thank you for the reply.

Here is the example of an error, I was expecting the mapping properties to not be dimensions, and the context-ref doesnt make since to me, considering XBRL-csv

here is the example of the command I'm using:
arelleCmdLine.exe ^
  --file="D:\Helpers\XBRL_CSV\sample instances\xBRL-CSV\xBRL-CSV\FINREP\DUMMYLEI123456789012.CON_FR_FINREP010000_FINREPDP_2025-06-30_20250826163344182.zip" ^
  --logFile D:\Helpers\XBRL_CSV\validationLog.xml ^
  --packages="D:\Helpers\XBRL_CSV\taxo_package\EBA_XBRL_4.2_Dictionary_4.2.0.0.zip|D:\Helpers\XBRL_CSV\taxo_package\EBA_XBRL_4.2_Severity_4.2.0.0.zip|D:\Helpers\XBRL_CSV\taxo_package\EBA_XBRL_4.2_Reporting_Frameworks_4.2.0.0.zip" ^
  --validate ^
  --formulaUnsatisfiedAsserError ^
  --plugin "saveHtmlEBAtables.py" ^
  --viewFile "D:\Helpers\XBRL_CSV\tableView.html" ^
  --DTS="D:\Helpers\XBRL_CSV\dts.html" ^
  --save-EBA-tablesets "D:\Helpers\XBRL_CSV\tableView.html"

Regards,
Francisco

[Austin Matherne]

The context ref is a synthetic artifact of loading the csv report into the Arelle runtime. I'll make a note that we should update the logs not to display it when loading OIM report formats. As for the dimensions, why do you expect them not to be included? Is the fact not tagged with those dimensions?