The error is displayed in Admin/View Data errors after the Report has failed to process. (Note: Your error message may not be exactly like the one shown)
ReportWriter.ProviderBase.Core.RequestException: Source System Request Failed ---> System.AggregateException: One or more errors occurred. ---> System.Exception: Low Value has wildcard at 3 but High Value does not (comparing 600606 between 712

In 7.x we are checking account masks and ranges in the Row Definition more carefully to be sure the user intent is explicit.
Asking for a range with mis-matched wildcards is a poorly defined way to set up the account request.
It is easily fixable into the manner that clearly defines what is being asked for.
If the Row Definition includes a range, there must be wildcards in the same positions of the Low and High values.
For example, this is OK: 100*00:900*00
This is not: 123456:999**9
The reason the second one is invalid is it is very unclear what it should mean.
To avoid confusion, we now error check the values. The clean up is pretty easy – if you really mean “everything”, put wildcards in both places. If you really mean “within a range”, put a real value.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article