Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
Albarosæ
Contributor III
Contributor III

Org Chart Duplicates Data

Hello,

I am trying to make an app about tasks and their relation. Also the reload times and status'.

But there is a problem about a relation I guess. You can see the image below:

Albaros_0-1690874453472.png

What  I need is like below:

Albaros_1-1690874504530.png

These are the same task and even the same taskID but it shows duplicated.

And here is the table for this task:

Albaros_2-1690874634350.png

And here is the data model for the app:

Albaros_3-1690876446909.png

 

Thanks.

 

Labels (2)
1 Solution

Accepted Solutions
Albarosæ
Contributor III
Contributor III
Author

I think the problem was occured due to task's first reload before connecting it to a parent task. It finds that log and also counts that task. 

After making the relation of tasks and parent tasks with a mapping and order by desc, the problem has solved.

There could be another solution where we rename the root nodes with a prefix and remove all tasks that has no parent and dont have the prefix.

Thank you for your interest.

View solution in original post

2 Replies
daturpin
Partner - Creator II
Partner - Creator II

Looks like multiple entries in the table with the same task name. The entries are not identical, one is failed and one has a difference in the duration. SHOULD there be only one entry? And if so, would you like the newest entry to overwrite the older one with the same task name?

Albarosæ
Contributor III
Contributor III
Author

I think the problem was occured due to task's first reload before connecting it to a parent task. It finds that log and also counts that task. 

After making the relation of tasks and parent tasks with a mapping and order by desc, the problem has solved.

There could be another solution where we rename the root nodes with a prefix and remove all tasks that has no parent and dont have the prefix.

Thank you for your interest.