Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Team,
I have a confusion in resolving Circular Reference from my Application.
I want the most easiest way to resolve it.
I am giving an example of my Table structure:
Table1: Table2: Table3
Team, City Country
Country Team City
How will i remove circular reference from it. Since, All the columns are important in my application I cannot omit it
Regards,
Priyanka
Hi,
You can join the tables instead of managing as three different tables, then you won't get this issue.
Regards,
Jagan.
Hi Reshma,
Thank you for your instant replay
Can you please tell me which table should i consider, to include as Lossen table
Regards
Priyanka
Hi Ranga,
Thank you for your reply with such a great example.
But, Qualify and Rename does some what the same thing. ie Qualify uses Tablename.Columnname & using Rename would directly change the column name. Which is not feasible in my case.
I have read in Qlikview 11 for developers book as well as few blogs about "Loosen Table" can you please help me out with this.
I am little confused on which table should i select for loosen table concept, and how do we identify it from this 3 tables
Thanks in Advance
Regards
Priyanka
Hi,
Not sure why are going for complex method instead of simply solving this by joining any two tables?
Regards,
jagan.
It is good method.
Why you have chosen that complex method? Is there any specific reason?
Hi Priyanka018
Can you give some sample data to provide quick solution.
Hi,
Apology for delayed response.
Attached is the QVW file for your reference.
Please suggest any appropriate solution.
Regards
Priyanka
Use this code to laod your Employees:
Employees:
LOAD EmployeeID,
LastName,
FirstName,
Title,
TitleOfCourtesy,
BirthDate,
HireDate,
Address,
City AS EmployeeCity,
Region,
PostalCode,
Country AS EmployeeCountry,
HomePhone,
Extension,
Photo,
Notes,
ReportsTo,
PhotoPath;
SQL SELECT *
FROM NORTHWND.dbo.Employees;
The reasoning is that it's probably not very useful to look at facts for which both the Employee (Sales Executive) and the Customer live in the same city.
Best,
Peter
Hi Peter,
Thank you for your instant response.
Previously, I also thought of renaming this to columns to avoid reference, but when I checked in SQL 25% of the city is matching in both the tables.
What do you think, should I proceed with the same logic or we need to find some different solution.
Regards
Priyanka
Well that is up to you and your document users: will they ever want to see the data for which both customers and employees reside in the same city? I guess not, so this simple Renaming trick will do. But then, I won't be a user of your QlikView document...
Best,
Peter