Forum Discussion

odevriend's avatar
odevriend
Frequent Visitor
9 years ago
Solved

XML with XSD schema

Dear Community members,   I run into the following problem. I have a XML with a XSD schema (same like XBRL instances), when configuring the upload with a sample file all available columns are avai...
  • odevriend's avatar
    odevriend
    9 years ago

    Hi,

    Please find more information about XSD on the following page:

    https://en.wikipedia.org/wiki/XML_Schema_(W3C)

     

    This morning I have completely rewritten the import of the various nested tables in the XML and I do not get an error anymore. The original file was written by someone else in a previous release op PowerBI, probably that is the source of the problem as I see completely specified columns in the functions where this is not the case in the functions I (automatically) created.

    For me the problem is solved for this moment, so I will put the message to solved.

     

    However if you know some way to handle errors within one field of a nested table this might be relevant for future problems. Till now I have only been able to handle errors on the table, so if one field within this table gives an error the complete table is not expanded.

     

Anonymous's avatar
Anonymous
Not applicable
9 years ago

odevriend,

I am not familiar about XSD schema, could you please elaborate details about how to change the schema and detailed steps you perform in Power BI Desktop?

Regards,

odevriend's avatar
odevriend
Frequent Visitor
9 years ago

Hi,

Please find more information about XSD on the following page:

https://en.wikipedia.org/wiki/XML_Schema_(W3C)

 

This morning I have completely rewritten the import of the various nested tables in the XML and I do not get an error anymore. The original file was written by someone else in a previous release op PowerBI, probably that is the source of the problem as I see completely specified columns in the functions where this is not the case in the functions I (automatically) created.

For me the problem is solved for this moment, so I will put the message to solved.

 

However if you know some way to handle errors within one field of a nested table this might be relevant for future problems. Till now I have only been able to handle errors on the table, so if one field within this table gives an error the complete table is not expanded.