is there a way to not generate an exeption when you find some errors in syntax of a LINQ Reporting command?
It’s very useful if you live the wrong command and add a friendly message beneath it and complete the report.
That allow the designer to quick understand where the error is.
I tried to use the option ReportBuildOptions.AllowMissingMembers for the ReportingEngine class expecting no exception in case of error.
A sintax similar to this
<<foreach [r in ds.My table name]>><<[r.Field]]>><> where erroneously the “My table name” really has spaces, generates an exception.
best is to have in the transformed document something like this
<<foreach [r in ds.My table name]>><<[r.Field]]>><> Aspose Engine ERROR! error message
What do you think and suggest?