GitHub user dmainou added a comment to the discussion: Previous transform fields are not propogating after mongoDB input transform
I can't really open it properly because I can't connect to your SQL database or your mongo database. In saying that, I think you are trying to do a bit too much. e.g. The outputs of your table input flow on to your mongo input and that's ok. However I'm not sure that these would flow on to a 3rd step. Especially because the mongo step is designed to retrieve data not to perform a join. Your mongo step is expecting exactly 1 column and n rows. Looking at your query you have over 30 columns. You would benefit from making a table input query that outputs the 1 column/variable that the mongo input needs then join the outputs with the inputs from a separate query that contains all your data. then keep going. I highly recommend that you preview your data at every step. e.g. Every time you start building a pipeline you should start with no more than 2 transform joined by a hop. The second transform must be a dummy. You start by configuring the input transform and preview on the output/dummy transform. If the data flows and looks like what you need, you add another transform in between the first transform and the dummy splitting the hop. Configure the transform and preview on the dummy rinse and repeat. GitHub link: https://github.com/apache/hop/discussions/5568#discussioncomment-13885479 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
