While working on reports, we usually get “#ERROR”,”N/A” or “error: Input string was not in a correct format”error.
The major problem behind these issues is data type mismatches and some additional reasons that cause these issues.
Let’s talk about how to resolve these issues and why we get these issues.
1. If you are performing any aggregate operation like SUM, AVG etc on the report and also you know that your input field might have string value then never use an expression like
The reason behind this is ISNUMERIC() method works in a mysterious way. If we will try to explorer this method a bit more in detail then we will find that is ISNUMERIC()returns true for any expression if there will be any possibility to convert the expression in numeric. For example, if you test ISNumeric("1,234.55") will return true whereas SUM("1,234.55")will give you #Error. To resolve this sitution
Always use expression like =SUM(VAL(Fields!YourFieldName.Value))
2. If you are using cube/MDX report and also using your aggregate expression like above but still getting an error or an unexpected result then you need to check these points
· Start your sql server profiler (Tools menu-> Sql Server Profiler) with Analysis services as service type. Execute/Preview your report and extract/copy the MDX from the profile. Now execute this MDX on the Analysis Services query browser. Make sure that your report’s aggregate column is available in the output. If you see your column unavailable in the output then you need to play a workaround to get include your missing column in the output.
The reason behind this missing column is if the resultant of your entire column is NULL and you are using Non empty/Nonempty then query engine exclude the column from the output to increase the query response time.
To resolve this problem, you need to add a calculate Member in your MDX query and append the expression by adding +0 at the end like :
Member CalculatedMember as [Measures].[Measure Name]+0
· Sometime due to mishandling the expression in the MDX query/Calculated measure, we get “Infinity”,”N/A” or scientific numeric format like 1.00E+12 in the MDX output.
To see the expected result at report level, we need to handle these problems at MDX level by using appropriate expression/fields/methods.