Forum Discussion
LOOKUPVALUE and Random Blanks
Yeah, can't use RELATED in LOOKUPVALUE. Plus, there is not relationship in that direction.
Yes, just trying to get the ID into the table, saves on measure calculations/processing not having to look those up on the fly every time.
It's mind boggling. Wish I could share the PBIX file as I am wondering if it has something to do with the scale of the data.
Here is an image of the model, perhaps someone can see a relationship that is causing an issue, I don't see it. Inventory filters nothing.
Greg_Deckler bit confused, your original post says FACT_Inventory related with Dim_Product, many to one
In your relationship, don't see FACT_Inventory??
Sorry, fact_Inventory = Inventory_v
Hi Greg_Deckler
I wasn't suggesting you use RELATED inside of LOOKUPVALUE but in place of it.
Since you have a 1 to many relationship between dim_Product and Inventory_v, surely you can use the following as a calculated column inside the fact table:
SourceProductID = RELATED ( dim_Product[SourceProductID] )I appreciate it doesn't explain the weird behaviour you're seeing with LOOKUPVALUE but may give you the results you're after.
Best regards,
Martyn
I appreciate your suggestion MartynRamsden . Unfortunately I cannot use RELATED because the relationship direction is from dim_Products to Inventory and I am trying to create the column in Inventory. I already have a work-a-round using FILTER and MAXX, I just can't explain the behavior of LOOKUPVALUE.
