Forum Discussion
Solution SageMerging issue where a line gets doubled when pulling in field from merged query
Hi rpinxt ,
Since your keys are matching for all rows you get more than one line for each one:
When you expand you get two rows. In this case you need to select the aggregation and not the expansion:
One row per each one
Be carefull on this merge since if there are for the same key more than one Storage type you will only get the maximum, you can also select the minimum or make it in a different way.
Solution SageYes you are correct MFelix
And these 2 rows come from the RunTime. For next run you get 3 rows etc.
Your solution worked but unfortunately not for me.
First of this aggregate is really slow as it needs to calculate for every row.
Not that much rows but I could see it going one by one.
And when done it said I could not use this step in directquery.....
So bad luck for me. But it did set me on the correct path.
Having the key every runtime was the problem.
Luckily I not needed runtime on the second source.
It serves merely as a lookup so I only needed the latest version.
So now I overwrite everytime the last version and therefore my key is only in once 😄
Solved my problem!
Thanks again for pointing me in the right direction.
Super UserHi rpinxt
Another option can be to generate an aggregated table that is only use ffor the lookup that will group the keys and return that column value and then merge it with your final table
- rpinxt
Yes could probably also done that. But now I was able to configure the source (removing the column with the timestamps). So no extra steps in query editor.