RPE 220.127.116.11 and older allowed in certain circumstances to create invalid queries and invalid data source references ( a property used in a context where it did not exist). This would happen most often when performing copy/paste or when replacing schemas.
The biggest problem is that the 18.104.22.168 and older RPE Studio/Launcher/RRDG would not detect these issues and would load and use these template. The results at run time range from a failed document generation to a document generation that apparently succeeds.
RPE 1.2.1 no longer allow creating corrupted templates and also improves the verification made when a template is loaded. This means that with the added verification RPE Launcher and RRDG will refuse to load corrupted templates. Document Studio allows loading these templates so that you can correct them but warns the user of the detected problems.
This post describes how to use Document Studio to correct these errors.
When you load the template in Document Studio RPE will immediately warn you that the template contain errors.
Additional error information is located in the errors view.
You can now go on each error to learn more details. Right click on an error will bring up the context menu from where you can choose “Open in editor”
The editor most often is the data expression/script expression editor but it can also be the filter/sort expression editor. Once open you will usually observe a property being used but nothing selected in the left tree indicating that the property is out of context. If you know what the context should be you can make the change here.
Once you’ve corrected all the errors save your template and select “Verify template” from the Template menu. If you have indeed addressed all errors than the error view will show no errors.
But if you need more context on the error ( to see where the element is in the template) you can use the following technique. Select “Simple Value” and put something like “<<<ERROR>>>” inside. You can use other value that it is unlikely to exist in the template already and you should also include the original value from the problm.
Once you’ve done this for all errors you can search for the markup string using the Search menu. Use * if you want to do a wildcard search.
This should give you all the information and context you need to fix the error.