Error - Mapping Sink is Empty.

[abhidotnet]

I am attempting to create a pipeline in my workspace. During the activity of mapping the source and the destination columns, I believe, I have found a bug.
1. This is my table structure for a table named opportunity2 in the lakehouse.

Table Structure

2. In my pipeline, I am setting this table as a the destination table.
Set Destination

3. When I try to map the destination columns, both Import Schema as well as manual mapping are failing.
Error in mapping.

[Anonymous]

Hi @abhidotnet ,

Your source table and destination table seems to be one table, they both have OPPORTUNITY_ID field and you want to implement Append operation, am I understanding correctly?

I ran a similar test and it worked.

Here is my configuration:

I do not see the configuration on your source page, here are some of my suggestions:

• Make sure the column names in source and destination tables match.
• Check that the data types of the columns in the source and destination tables are the same, otherwise the mapping may fail.
• Try clearing the existing mapping settings and then do the mapping again manually.
• Ensure that the table structure of the destination table is correct and contains all the required columns.

If you have any other questions please feel free to contact me.

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[abhidotnet]

No. I have a table called DailyOppDataStage with a very similar column structure.
Opportunity2 is my destination table.

[Anonymous · Accepted solution]

Hi @abhidotnet ,

I have tested and when executing map column in data pipeline, the data pipeline may report an error if it is two different tables with mismatched column names or data types.

Here are some of my suggestions:

Columns in both tables should have similar or same names. This will make it easier for the mapping rules to recognize and match the columns.

The data types of the columns involved in the mapping should be the same or compatible. For example, an integer column in one table can be mapped to an integer column in the other table, but not to a string column.

Manually specify which columns are to be mapped in the mapping configuration, even if they have different names.

Preprocess the data so that the column names and data types are as similar as possible before performing the mapping.

If you have any other questions please feel free to contact me.

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!