Preceding load and join to main table - Qlikview changes the field name when it's not asked to

[#1]

Hello;

I'm just using a preceding load to derive a new field and add it to my MainTable (can't do this during the load for MainTable because the fields are actually derived after). So my problem now is, Qlikview adds the new field, but it changes the name of the NewFieldKey to Temp.NewFieldKey. However, I want to have it named as NewField because that's my key to link this MainTable to another table that I have.

TempComp:

LOAD

[Field1] & ' ' & [DerivedField] as NewFieldKey,

[ID]

;

Load

  [ID],

  [DerivedField],

  Field1

  Resident [MainTable];

Join (MainTable)

Load *

Resident TempComp;

Drop table TempComp;

[sunny_talwar]

Are you using Qualify Statement above the TempComp Table?

[swuehl]

Try a

Unqualify NewFieldKey;

before your TempComp table load.

[#4]

I am using Qualify Statement, but before this - for another table.

[#5]

I am using Qualify Statement, but before this - for another table.

[#6]

Hi Swuehl,

added "Unqualify NewFieldKey;" - didn;t work unfortunately

[sunny_talwar]

You might have to do Unqualify *; before the TempComp table.

[sunny_talwar]

May be like this:

Unqualify *;

TempComp:

LOAD

[Field1] & ' ' & [DerivedField] as NewFieldKey,

[ID]

;

Load

  [ID],

  [DerivedField],

  Field1

  Resident [MainTable];

Join (MainTable)

Load *

Resident TempComp;

Drop table TempComp;

[Clever_Anjos]

"I am using Qualify Statement, but before this - for another table."

Qualify efects persists until end of script or a Unqualify. It´s not per-table

[Digvijay_Singh]

If this is linked to your previous post and you have used Qualify which is preceding table name in your fieldnames to meet your other requirement, you can use Unqualify to avoid certain fields unqualified.

QUALIFY *;

UNQUALIFY NewFieldKey;

Use Unqualify * after your required use of Qualify to avoid any impact on existing scripts.