Rename Column with entity value during generic load

[TimoHart]

Hi , 

I need to rename Status according to the actual Actions value. Each generic table will eventually need its own Status depending on the Action. But it wont accept what I tried to do.. nor could i find the propper syntax. 

Master:
generic load
left("WBS Element",17),Status as S & $FieldName("Oper./Act."),"Oper./Act.", "Latest finish"
Resident StatusTable
where right("WBS Element",3) = '142'
;

// "Status", // as S & ["Oper./Act."],
// "Status", // as 'S' & ["Oper./Act."],
// "Status", // as S & "Oper./Act.",

[marcus_sommer]

The syntax is wrong - on the field-values as well as by the field-name. Further the field-name couldn't be the result of a calculation else must be an existing field within the source.

A crosstable-load and also the counter-part of the generic-load are not normal loads else for the usage simplified load-prefixes which trigger a lot of quite heavy transformations within multiple loops. This limits the possibilities to integrate further transformations within it. As a general rule - don't try to apply any further transformation on them else performing it a step before and/or afterwards.

[TimoHart]

Well thank you very much Marcus. I would like to do this before or after. The generic load seems mandatory for me to get the required transformation. I am  simply to new to the basics I guess so I have no idea on how to do it . 

I added 3 screenshorts . Possibly there is a simple hint in the right direction possible ? 

Best Regards 

[marcus_sommer]

It seems that you tries to transform the "normal" status-table per generic load into a crosstable-structure like the TO# V## table. Doing the opposite and applying The Crosstable Load - Qlik Community - 1468083 to resolve the multiple dates/status in a normal data-structure would be much easier and more expedient.

Many things should be already possible possible just by associating both tables per order-key but it might be beneficial to merge some or all information from one side to the other side - maybe per mapping against the order-key.

[rwunderlich]

In a Generic load, the final fieldname comes from the contents of the field, not the "as" clause. Also you need a key field like "Project" as your first field. 

Master:
Generic Load
  Project,
  left("WBS Element",17) & "Oper./Act.",
  "Latest finish"
Resident StatusTable;

See https://qlikviewcookbook.com/2010/05/use-cases-for-generic-load/ for similar examples. 

-Rob
http://www.easyqlik.com
http://masterssummit.com
http://qlikviewcookbook.com