Forum Discussion
Data modeling - Non unique values
- 9 years ago
Hi, using a calculated column And DimA is 10
When DimA-10 = LOOKUPVALUE ( Table1[Dim B], Table1[Ticket], Tickets[Ticket]; Table1[Dim A], 10 )Using a measure:
Measure-When DimA-10 = IF ( HASONEVALUE ( Table1[Ticket] ), LOOKUPVALUE ( Table1[Dim B], Table1[Ticket], VALUES ( Tickets[Ticket] ), Table1[Dim A], 10 ) )let me know if works.
Victor
- Anonymous9 years ago
Tulio_DL,
Create the calculated column in TABLE A.When DimA-10 = LOOKUPVALUE ( 'TABLE B'[DIM b], 'TABLE B'[Ticket], 'TABLE A'[Ticket], 'TABLE B'[DIM a], 10 )
Also you can change the second formula of Vvelarde to the following:Measure-When DimA-10 = IF ( HASONEVALUE ( 'TABLE B'[Ticket] ), LOOKUPVALUE ( 'TABLE B'[DIM b], 'TABLE B'[Ticket], VALUES ( 'TABLE A'[Ticket] ), 'TABLE B'[DIM a], 10 ) )
Regards,
I can no wrap my head around the way you are using dimension and fact tables. I feel like you have them swapped.
Dimension tables should have unique id's...
- Tulio_DL9 years agoHelper I
Hello Anonymous
It really looks like....... actually it is very confusing! BUT.... that's the only way a *** system gives me the information I need
='[
- Anonymous9 years agoNot applicable
Well, given you DO have a table of unique values, I would go ahead and create the relationship between ticket id's. The 1 to many direction will be a bit opposite of what people think, but so be it.
Now, in your table of unique values, apparently you want a new calculated column... that looks up into the non-unique table, and does *what* exactly?
- Tulio_DL9 years agoHelper I
Yes Anonymous! I have already established this relationship, and yes it's totally in the opposite way...
I would like to bring the information at 'DIMENSION table'[DIM b] into my 'FACT table'
considering that 'DIMENSION table'[DIM a] = 10 for example