I used SSIS SharePoint List source and destination to publish a SharePoint list of employees, combining data from a internal database source as well as active directory.
At some point, I noticed that the returned column from a ssis lookup returned null value.
I did notice though the lookup transformation was working at first time and the default options have 'full cache' turned on. this post a reasonable doubt that the issue might be caused by caching. after turned it off, the result is now normal.
Subscribe to:
Post Comments (Atom)
Elevating LLM Deployment with FastAPI and React: A Step-By-Step Guide
In a previous exploration , I delved into creating a Retrieval-Augmented-Generation (RAG) demo, utilising Google’s gemma model, Hugging ...
1 comment:
I believe this NULL issue has something more than the cache mode setting of LookUp component.
One reason could be the way we let the LookUp handle the non-matching rows. In "LookUp Transformation Editor", if we set it to "Ignore Failure", then for every Non-Match it dumps/report a NULL into the Destination Adapter. And if we configure it to "Redirect rows to no match output", then such NULL reporting stops.
Do tell me if yours was a different case... for, There lies many matters beyond our normal human comprehension :)
-- In 'thoughts'...
Lonely Rogue.
Post a Comment