Yes this sort of logic will work. In your load script you can write the logic using an if statement. I created a small example below. The exact expression will depend on how you want to deal with other members in the RegionA or RegionB fields. If you have a more complex logic (e.g. different outcomes for RegionC based on several combinations of RegionA and RegionB you may want to concatenate the two fields and then use a mapping table to resolve the logic.
If(RegionA='ASIA' or RegionB='ASIA', 'ASIA', RegionA) as RegionC,
Both fields are in the same table. We want the scenario like Region A = 'ASIA' (Region B Can be asia or anything else)
OR RegionB = 'ASIA'(Region A can be asia or anything else) So its simple OR condition but usually Qlikview shows it like AND and OR logic does not work
RegionA RegionB Revenue
ASIA UK 100
ASIA ASIA 200
UK UK 300
US ASIA 100
So in above case when i will select my newly created field Region C which has logic like Region A = Asia or Region B = Asia The revenue for it should come as 400. I am trying to achieve it
If it's just about Asia, then no problem. As already suggested, create new field in script like this:
If(RegionA='ASIA' or RegionB='ASIA', 'ASIA', <whatever it's to be when neither is ASIA>) as RegionC
But you can't store "logic" in a field, just the result of applying it to other fields. So, if you wanted to switch to selecting "RegionA='UK' OR RegionB='UK'" at a click, you can't do this that way. For that you have to either incorporate set analysis into your expression, or create the new field as linked to all combinations of RegionA and RegionB which satisfy the logic for each and every region. I'd stick with set analysis if I were you.
Here's an example of general implementation of OR-mode selection: Or-mode selections in QlikView The Qlik Fix! . If you need it for just one field, you can trim it down to something much simpler.