I’m in the process of renovating some of our now-three-year-old DI data flows, and one thing I’m doing is replacing some pretty hairy Oracle views with Reverse Pivot transforms. However, when the job comes across a value that I am not pivoting on (and could not possibly care less about), it’s throwing a warning message and populating the error file, which is causing our alert system to have a hissy fit and page me. Since I don’t really enjoy getting these pages at O-dark-thirty in the morning, is there a way to tell DI to ignore any “unexpected pivot values” and continue on its merry way rather than throwing a warning?
Good point, worth an enhancement request. What about having a validation transform upfront that checks on the valid values and if it finds an invalid, substitutes it with a default or whatsoever?
That would work great if you only had a few values that you want to pass through. However, in one instance that I’m working on, there are over 200 individual values that we’re pivoting over (I know, don’t ask… ). In my version of reality, I’d rather have the option to be extree lazy and ignore unexpected axis values.
The “WHERE clause to only specifically include pivoted values that you care about” can be a join to another table (or even a flat file) that contains the expected values. It shouldn’t exactly be rocket science …
(BOB member since 2004-09-08)
(BOB member since 2004-12-17)
). In my version of reality, I’d rather have the option to be extree lazy and ignore unexpected axis values.
(BOB member since 2004-09-08)