I don't think code from Example 2 would work in your load script as I would expect QV to return an error - something like "columns in your tables must have unique names" --> let's not forget that QV builds the association between the tables based on field name (and it is case sensitive), so it will not allow you to create 3 [Call Outcome] fields.
Example 1 would work - of course considering that that's the logic you need in your script.
Ok, so example 2 won't work. Disregarding how qlikview would handle this, is the logic at least the same. In other words, in qlikview you must nest the if statements, but really all the logic is, is a bunch of if statements together with no difference in priority. Does that make sense?
There won't be any difference in nested if else, you can use the same logic as you would do in any programming language. Your second one will give error for field names as the Qv works on field name.
