Copy Action - XML - Single Element not getting mapped / copied

[geschinger]

We are experimenting with a pipeline to take data from XML files to SQL database and everything is working great for files with multiple elements but nothing copies over when there is a single <SalesJournal> element.

For example a file like this works fine.  All the mappings for the ... elements work as expected:

Files that only have one - like this - do not throw any errors but nothing gets mapped/copied:

If I take the same file and add another empty <SalesJournal> element then it will get mapped/copied along with a blank NULL record for the empty one.

Any suggestions on what I would need to adjust or what I might be doing wrong that prevents the successful mapping/copying of an XML file with the single element?

Thanks,

Greg

[Anonymous]

Hi @geschinger ,

Thanks for using Fabric Community.

As I understand you are facing issue while working with XML files.

In order to repro the scenario I have taken two scenarios to understand.

Scenario 1:

XML File Format -

After pipeline execution (XML to Table) -

Scenario 2:

XML File Format -

After pipeline execution (XML to Table) -

I cannot find any issues with these XML formats. In case if you further help please let me know.

[geschinger]

Hello @Anonymous 

I have this XML file:

When I run the pipeline it is status succeeded but with no rows written:

If I then add <SalesJournal></SalesJournal> to the end:

and rerun the pipeline it is status succeeded and 2 rows written:

Is there something I'm doing differently and/or wrong with my mapping that would be preventing the files with only one from getting written to the DB?

Thanks,

Greg

[Anonymous]

Hi @geschinger ,

Apologies for the issue you are facing.
As per my understanding you are facing this issue in Azure Data Factory but not in Fabric Data Factory.

Unfortunately Fabric Community only supports fabric related issues, incase if you want to resolve your issue related to Azure Data Factory - please raise your issue here - Ask a question - Microsoft Q&A .

But I also tried to repro your issue in Azure Data Factory for time being and I can observe it more like a bug. 

Appreciate if you could share the feedback on our feedback channel. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.

Incase if you have any more queries related Azure Data Factory Isuue, please go ahead and raise a query here.

Hope it is helpful. 

Thank you

[geschinger]

Hello @Anonymous 

I'm pretty sure I am in Fabric Data Factory and not Azure Data Factory. 

The URL I access it from is:

I am connecting to Azure for the SQL Database:

My understanding is that I'm using Fabric Data Factory connecting to Azure SQL Server.  Azure Data Factory would be accessed through Azure Portal and not app.fabric.com portal, correct?

If this is a bug is there URL to report Fabric Data Factory issues?

Thanks,

Greg

[Anonymous · Accepted solution]

Hi @geschinger ,

When I tried to repro you scenario in fabric, I am not facing this issue at my end.

My Pipeline in Fabric Data Factory -

My Xml Sample File:

<?xml version="1.0"?>
<catalog>
   <book id="bk101">
      <author>Gambardella, Matthew</author>
      <title>XML Developer's Guide</title>
   </book>
</catalog>

Can you please re-try by creating a new connection and try to check if issue is still exists.
In case if the issue still exits please share the sample file you are using let me recheck with that file at my end.

Thank you
 

[geschinger]

Hello @Anonymous 

Recreating it seems to have solved it.  Not sure how or why as I cannot find any difference between the one that fails and the newly created replacement.  But now if I run v3 (newly created pipeline) it works as expected:

While the identical previous one still writes 0 rows in the Azure SQL DB.

Thanks for your help,

Greg

[Anonymous]

Hi @geschinger ,

Glad to know that your query got resolved. Please continue using Fabric Community for your further queries.