Forum Discussion
Value transformation
Hi , Br1bn
Accoding to your description,you want to get two different columns by some rules. And now you have two options .
I recommend you to use the first way. Here's why:
(1)For the first way, you can create a relationship table to maintain your information, and create corresponding relationships, if there are later modifications, you only need to modify the information in the table. For the second type of DAX sentence that needs to be modified if the relationship is modified, it is not very well maintained for the later stage.
(2)Creating a one-to-many relationship, we can directly use fields from a table on one table as a dimension without having to write complex DAX sentences.
Thank you for your time and sharing, and thank you for your support and understanding of PowerBI!
Best Regards,
Aniya Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Community SupportHi , Br1bn
Accoding to your description,you want to get two different columns by some rules. And now you have two options .
I recommend you to use the first way. Here's why:
(1)For the first way, you can create a relationship table to maintain your information, and create corresponding relationships, if there are later modifications, you only need to modify the information in the table. For the second type of DAX sentence that needs to be modified if the relationship is modified, it is not very well maintained for the later stage.
(2)Creating a one-to-many relationship, we can directly use fields from a table on one table as a dimension without having to write complex DAX sentences.
Thank you for your time and sharing, and thank you for your support and understanding of PowerBI!
Best Regards,
Aniya Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly