Member from dimension '%{name/}' could not be found. This may be because of a stale dimension cache. Re-running the query after clearing the cache may solve the problem.
Master processing node must receive all expected partitions information from auxiliary processing node response accordig ...
Master table versions between Vertipaq Table '%{IMBITableName/}' and Tabular Metadata storage encountered unexpected inconsistencies ...
Maximum value '{0}' for Scale facet must be less than or equal to the maximum value '{1}' for Precision Facet in '{2}' type. ...
MeasureGroupDimension '%{name/}' in measure group '%{mgname/}' does not have property 'ShareDimensionStorage' set to 'Shared'. ...
Member from dimension '%{name/}' could not be found. This may be because of a stale dimension cache. Re-running the query ...
Member Mapping specified is not valid. The type '{0}' of member '{1}' in type '{2}' is not compatible with '{3}' of member ...
Merge of existing transaction version map file '%{fileName/}' to lazy master version map failed with error code=%d{ErrorCode/}. ...
Merge the following tables together, {[A = 1], A = 2], A = 3]}, {[A = 4], A = 5], A = 6]}, and {[A = 7], A = 8], A = 9]}. ...
Merges the specified dimension table into the cube's filter context and changes the dimensional granularity of the filter ...