Trying to use any of the new INFO functions in a measure generates an error "An unexpected error (file 'TMTransaction.cpp', line 420, function 'TMTransaction::GetSaePointForDiscovers').
Feedbac...
Anonymous That seems like an arbitrary limitation. There are many reasons we would want access to that info.
Also why not include that detail in the error message? The reason for the error is clear but the error message to the user is incredibly cryptic.
Instead of: "An unexpected error occurred (file 'TMTransaction.cpp', line 420, function 'TMTransaction::GetSavePointForDiscovers')."
How about saying: "INFO functions are only available in Dax Query View".
This all seems fairly obvious...