Trying to print a report for connection 6, but keep getting an error saying "An error occured while rendering the report..." (see the attached picture). Why is this happening? I have attached the connection file as well (in zip file since BC was giving an error trying to upload the RAM Connection file itself). I am using version 13.
Connection_Chase QC Corrected.zip
The file worked fine for me in v13.00.00.56 I reviewed Joint 6, and a redesigned all the joints without error. I saved it under a new name just in case it helps, but if the problem persists on your end a clean installation seems best.
https://communities.bentley.com/cfs-file/__key/communityserver-discussions-components-files/5932/Connection_5F00_Chase_5F00_seth.rcnx
I have no issues doing the design, but the problem occurs when I try and print a report from within the joint 6 module (see attached picture). That is when the error occurs. Can you produce a report for joint 6 without errors from within the joint 6 module?
I see. I can reproduce that error too. Meanwhile, use the Output - Results route to get the reports from this file.
Please check the model which our developers fixed.
https://communities.bentley.com/cfs-file/__key/communityserver-discussions-components-files/5932/Connection_5F00_Chase-QC-Corrected_5F00_Fixed.rcnx
That file worked without the rendering error. What was the issue? Is this an issue due to something we did or something internal to RAM Connection? How can this be avoided in the future?
There were some issues with some files in v12.00 format when several connections were deleted and then created again. This was causing errors when trying to report from the connection pad, this has been fixed in v13.0. However, there might be some models (created in v12.0) that already have this issue in the model file. When this happens, we have to clean the model file from a developer machine to fix it. If you update to version 13.00 it should not come up again for new files.
Can this be done for my file as well? I have the same issue with the "error rendering..."). I've updated my RAM connection to latest v13, but error persists.