Forum Discussion
Relationship Structure for Both Non-Hierarchical Tags and Hierarchical Categories
yanivcogan,
In your scenario, you are only able to create inactive relationship between project table and course table. Assume that you are allowed to make this relationship active, in this case, you create an ambiguous path from project table to course-tags table, should project traverses tags table or course table?
When you have inactive relationship between tables, you can create measures using USERELATIONSHIP function to get desired result.
Regards,
Thanks for responding, that certainly looks like the right direction to follow. So far, I've only managed to user USERRELATIONSHIP to calculate aggregations of values based on an inactive relationship. I can't seem to figure out how to just list the relevent data, without summeraizing it in any way. I tried using the VALUES function, as suggested here, but got an error message () when trying to use the measure with any visual.
I tried using LOOKUPVALUE as suggested in some places, but it looks like that is currently only posibble if there is an active relationship between the tables involved.
Any suggestions on how to proceed from here would be very much appreciated. Again, thanks Anonymous for taking the time to respond.
- Anonymous9 years agoNot applicable
yanivcogan,
Please help to share sample data of your tables and post expected result here.
Regards,- yanivcogan9 years agoFrequent Visitor
Anonymous
Hello again, really sorry about the ridicoulus delay in getting back to you.
Here is a PBI file with example data in the same structure: Link
I can't figure out how to get either LOOKUPVALUE or USERRELATIONSHIP to return an actual list of courses, which I can display in a table - only an aggregation for numerical fields.
Ideally, I would like to have the right-most slicer (the project slicer) filter both the other slicer (the tags slicer) and the courses table, and have the tags slicer filter only the courses table.
If that is impossible, and the problem is that this data stracture is not normalized, how would I go about fixing that, to make it more PBI compatible?
Thanks,
Yaniv