Hi Anandhswarupp ,
The cause of issue is limitation of the product. Please try with following two possible workarounds.
- Load the data as-is and use DAX to create a calculated column with the necessary transformation.
If you are using Import mode or if the dataset is not too large, a practical workaround is to load the data into Power BI as-is and then perform the necessary transformation using DAX. Once the data is imported, you can create a calculated column within Power BI that applies your transformation logic.
For example, if you need to map or categorize values, you can use functions like SWITCH
or IF
to build the logic directly in DAX.
- Create the mapping as a table on the SQL Server and use joins to do the transformation
For scenarios where you are using DirectQuery or need better performance with large datasets, it is recommended to move the transformation logic to the SQL Server side. You can create a separate mapping table in the SQL database that holds the transformation rules or reference values.
Once the table is in place, you can join it to your main data table within Power BI, allowing the SQL Server to handle the transformation before the data reaches Power BI