- Posts: 539
- Thank you received: 59
Transformation Fail on Zero (0) Writes
- bruce.gibbins
- Topic Author
- Offline
- Platinum Member
-
Less More
1 year 5 months ago #21490 by bruce.gibbins
Transformation Fail on Zero (0) Writes was created by bruce.gibbins
Hi.
I may have missed this option if it already exists. But I was wondering if there was an option to have a Flag on the Transformation Action in a package that would throw an 'Error' if there were records processed but nothing written?
In my case we get an inbound source file that is then filtered via a Validator with unmatched rows being DISCARDED in a Transformation. On occasion this results in no valid records being found and thus nothing written. The Transformation completes with no Error and nothing actually went wrong at our end except that they sent us a file that was missing the data we needed. We should still investigate.
The workaround at the moment for us is to interrogate the <Transformation Processed> and <Transformation Error> After Execution variables but just thought it would cleaner and in our case a bit more intuitive to have a simple flag that can then force the Transformation o end in error. Then the rest of the package flow would not have to jump into scripts to check for values and change workflow control from that point.
Cheers
I may have missed this option if it already exists. But I was wondering if there was an option to have a Flag on the Transformation Action in a package that would throw an 'Error' if there were records processed but nothing written?
In my case we get an inbound source file that is then filtered via a Validator with unmatched rows being DISCARDED in a Transformation. On occasion this results in no valid records being found and thus nothing written. The Transformation completes with no Error and nothing actually went wrong at our end except that they sent us a file that was missing the data we needed. We should still investigate.
The workaround at the moment for us is to interrogate the <Transformation Processed> and <Transformation Error> After Execution variables but just thought it would cleaner and in our case a bit more intuitive to have a simple flag that can then force the Transformation o end in error. Then the rest of the package flow would not have to jump into scripts to check for values and change workflow control from that point.
Cheers
Please Log in or Create an account to join the conversation.
1 year 5 months ago #21496 by admin
Mike
ETL Architect
Replied by admin on topic Transformation Fail on Zero (0) Writes
Good Idea we will have a look at it for you
Mike
ETL Architect
Please Log in or Create an account to join the conversation.
- Peter.Jonson
-
- Offline
- Platinum Member
-
1 year 5 months ago #21497 by Peter.Jonson
Peter Jonson
ETL Developer
Replied by Peter.Jonson on topic Transformation Fail on Zero (0) Writes
Peter Jonson
ETL Developer
The following user(s) said Thank You: bruce.gibbins
Please Log in or Create an account to join the conversation.