Applymap not producing data

[Anonymous]

Hello community,

I'm having some trouble with an Apply map function.

Put simply, I'm trying to add the price of a product on a template, and the price of that product on the web, onto my main transactions table.

The joining field is called 'Order_Join', and I have checked to make sure that they do indeed link up.

However, when I apply the mapping load, the resulting field is showing Order_Join, an alpha-numeric key, rather than the corresponding price data from the Mapping load.

Mapping:

Apply map:

Any help would be appreciated.

Cheers,

Henry

[Anonymous]

One after the Temporary Orders table, and two at the very end of the script to drop the Order table after it's been stored

[Anonymous]

True, I should have thought of that.  It's loaded now anyway.  And here's my table box

[Anonymous]

Here is the original mapping file:

Order_Join definitely corresponds to the main table (unless I'm missing something obvious?) and there is valid data in the unit price field (which is what I'm trying to recover)

[Anonymous · Accepted solution]

Actually, it looks like the only reason this is happening is because I haven't specified the default value for non-matches.

Where a match is found, it does bring it back, as shown below:

Oops, thanks anyway guys!

[swuehl]

Your table box is showing the result of your mapping table attempt.

I was suggesting to link the tables instead of using the mapping, just as I understood you've done before.

(In other words, remove the MAPPING keyword and concatenate your two Price tables into one, or remove the Description filter. Then load your order table and now your two tables should be linked by Order_Join field)

From your previous screenshot, I can't really tell if the values really match. One table shows other product id range than the other.

[swuehl]

Ok, that Information piece 'where there is a match, it's working' was missing ...

Good that Qlik is working as designed 😉

[Anonymous]

Yep, I had no idea that it would default to the key field.  Cheers for the help though, we've got some good troubleshooting steps that can be referred back to now