SSIS 2005 how to resolve the error "input column has lineage id that was not previously used in the data flow task" programmatically
Asked Answered
P

4

11

I'm trying to write a program that automatically add columns from the OLE DB Sources in all of the components in a .dtsx file (the target is SSIS 2005). When I process the .dtsx with my program seems that the columns are added correctly, but when I open the modified package, in the components appears this message:

input column has lineage id that was not previously used in the data flow task.

If I double click on the component and then I press OK the error disappear.

My question is:

is there a way to have the same behavior programmatically? I'll try to automate this operation for the user by using this program but with this error block me in the project.

Prague answered 20/9, 2013 at 15:18 Comment(3)
I am not sure how you are adding columns but it seems like the columns you are adding are getting added correctly but the metadata is not getting updated. When you open the component, the metadata gets updated and the error goes away. You should be asking how to update metadata programmaticaly. Thanks!Soapwort
Without knowing how you are adding the columns and assigning their lineage id, it is impossible to diagnose this issue.Desiderata
I would compare the package (it is XML) before and after opening component in designer, and see what changed. It might hint on what needs to be fixed.Fassett
D
0

i had this problem, i could resolve that by bellow solution but i know it's not useful solution. meta data can not detect your changes , you can delete your task and create again that task.

Dalliance answered 27/1, 2021 at 7:37 Comment(1)
Shouldn't this answer be a comment then?Yonah
P
0

Lineage ID must be invalid

  • Option 1 delete data flow and add again & remap all column

  • Option 2 Open the SSIS package XML Code and search for an invalid Lineage column, copy and paste existing lineage and it should work.

LineageID Print Screen

Paoting answered 24/1 at 21:7 Comment(0)
Y
0

I resolved by deploying the package again to the SSISDB

Yonah answered 23/7 at 14:22 Comment(0)
A
-2

Both source and destination column must have the same linage id.

Anoa answered 8/5, 2018 at 11:22 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.