Forum Discussion
Case Sensitivity?
When the data move from PowerQuery into vertipaq (the in memory engine for PowerBI) it translates the data into the dictionary. The dictonary compresses the data so it is faster to work with for the model engine and because, as far as the vertipaq engine is concerned, 'Pasco Prod' and 'Pasco PROD' are the same, it puts the first version it finds into the dictionary. Then, when your model goes to get the value for that column from the dictionary, the entry for those two rows get the single value from the dictionary. It just happened to be that 'Pasco PROD' was saved to the dictionary. It could just as easily have been 'Pasco Prod' and every where Power Query sent that string in.
- Pasco Prod
- PASCO PROD
- PaScO pRod
- pASCO pROD
- etc.
Would all come out as 'Pasco Prod' because that is what the vertipaq dictionary has.
When the data move from PowerQuery into vertipaq (the in memory engine for PowerBI) it translates the data into the dictionary. The dictonary compresses the data so it is faster to work with for the model engine and because, as far as the vertipaq engine is concerned, 'Pasco Prod' and 'Pasco PROD' are the same, it puts the first version it finds into the dictionary. Then, when your model goes to get the value for that column from the dictionary, the entry for those two rows get the single value from the dictionary. It just happened to be that 'Pasco PROD' was saved to the dictionary. It could just as easily have been 'Pasco Prod' and every where Power Query sent that string in.
- Pasco Prod
- PASCO PROD
- PaScO pRod
- pASCO pROD
- etc.
Would all come out as 'Pasco Prod' because that is what the vertipaq dictionary has.