Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

QVD Joining doesnt work

Hi Folks,

i have an issue with my QVW. I got a lot of tables joining in together through some common fields. I got help here creating an previous version. Then i needed another table and I cant seem to maek them map. Its the RBT table who isnt joining to RBA1. I choose a MarketId but it doesnt map unfortunately it takes other markets in the RBT table still:S

I'll attach what i've got amybe someone has some input. It would be much appreciated:D

Cheers

9 Replies
boorgura
Specialist
Specialist

It will be helpful if you can post a sample QVW with your issue.

Or at least a screenshot of the internal table viewer.

Not applicable
Author

I attached the code in a word document. Because the QVW was too big.

ciaran_mcgowan
Partner - Creator III
Partner - Creator III

Hi Niklas,

I'm not seeing a MarketID field in the RBT table. Are you using MarketOrderID but they don't seem like they would be the same thing.

Can you confirm that both fields you are using share common values (i.e. load both fields as different field names to manually check that the data matches)?

Not applicable
Author

Yeah. In RBT its called ExecutionVenueId but the data is the same like COP in and COP in both tables...

ciaran_mcgowan
Partner - Creator III
Partner - Creator III

Thanks. Are there any synthetic joins that could be causing you problems? I'm looking at AccountID specifically. If not, it might be a good thing to double check the format of matching values by exporting them to excel. There could be leading/trailing blank spaces, case issues, etc. You may need to use functions like Trim(), Replace() or Upper() to make sure they all match.

Not applicable
Author

AccountID and TradeDate makes a synthetic join. How would that Trim() function work and what does it do?

boorgura
Specialist
Specialist

Trim() functions cleans up the data for proper association - so that if data is coming from different sources - any leading or trailing blanks would be removed.

also - what are the common fields do you WANT the JOIN to be? Are they all named the same for Qlikview association?

ciaran_mcgowan
Partner - Creator III
Partner - Creator III

I'd say that's your issue there. The synthetic join means that a field will only map when all fields match so AccountID, MarketID AND TradeDate would ALL have to match.

You should try renaming AccountID & TradeDate to something else in the RBT table to see the difference it makes.

ciaran_mcgowan
Partner - Creator III
Partner - Creator III

Sorry. Trim() removes blank spaces from the start and end of a field.