Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I have a 2 table with Employee_initials, Employee_Name, Employee_Number, Jan2020pay, Feb2020pay
RG, Roger Gara, 12345, 100, 200
JK, Jack Kent, 23456, 200,350
KLM, King Larry Moe 234556, 400, 500
SECOND TABLE
RG, Roger Gra, 12345 , 0 ,0
JK, Jack Kent ,0 ,0
KLM, King Moe 234556,0,0
now looking at these, I create a key as
if(Employee_initials<> "" and Employee_Number<>'',
Employee_initials &'|'& Employee_Number,
Employee_initials & '|' & Employee_Name) as EMPLOYEEKEY (2 fields will always match)
the next columns should be able to display both versions of the Employee_Name
If I use a join, I end up with 2 records the differences instead of 2 columns for the name
when I use NoConcantenate, it does give me both tables, but sooner or later I need to combine them.
I tried to alias the field name, but the same type of data still merge.
The ultimate goal is to migrate the pay to the new system.
What would be most helpful is the QVW file or a sample QVW showing the issue, that will make it much easier for folks to try to assist you with this, little difficult, at least for me, to try with what you have provided, the data model is key in this case, and not being able to see that is a problem...
About the only thing I can give you would be the Design Blog area main link to search for examples there:
https://community.qlik.com/t5/Qlik-Design-Blog/bg-p/qlik-design-blog
Regards,
Brett
What would be most helpful is the QVW file or a sample QVW showing the issue, that will make it much easier for folks to try to assist you with this, little difficult, at least for me, to try with what you have provided, the data model is key in this case, and not being able to see that is a problem...
About the only thing I can give you would be the Design Blog area main link to search for examples there:
https://community.qlik.com/t5/Qlik-Design-Blog/bg-p/qlik-design-blog
Regards,
Brett