In this Topic Hide
This section provides a list of unresolved issues at the time of release:
1. When exporting data to Excel and PDF the icons are not included. This is because DevExpress doesn't support custom draw events when exporting. TS 32647 and TS 32648
2. New languages are not shown on expanded items in Static Vocabulary and Vocabulary. This is due to DevExpress not automatically reloading child rows in their grids. They recommend expanding/collapsing it manually to see the changes. TS 33337
3. Sometimes dragging concerns to Concern/Repairs does not work as expected. This is only an issue when using touch screen monitors and trackpads and can be overcome by using a mouse. TS 34285
4. The first time an operator adds a defect the focused Responsible Area and Cell might not be visible. The issue is with DevExpress. TS 33906
5. Thumbnails of vector bookmarks shown as question marks. If upgrading from pre 6.0.95.25 you need to update the bookmarks and save the views.
6. There is a visual issue when your switch between bookmarks while the model is still moving. This is a 3rd party software issue. TS 46180
7. When you click "Add from disk" multiple times it will reload the images it already loaded from the folder and duplicate them over and over. TS 44876
8. Red square symbol appears and no components are called out when hovering in defect entry mode. This only happens with some specific CAD models that have been in the database while it underwent update scripts somewhere around 97 to 110. If the issue occurs contact ATS and a fix will be made for your database. TS 48416.
9. Defects cannot be added to CAD models that contain the file extension in the image name. TS 48692
10. Exception when opening main form due to ViewImageControl. This occurs when database is upgraded to 6.2.177 from an earlier version of 6.0. TS 48989
11. Unable to assign defects to vector views that have components embedded in the view. This is an issue with custom names and can be resolved by setting LockNameOnDescendents and IgnoreAncestors at the right level in the component tree in View Composer. TS 51151
12. Double clicking on an imported form from an older version produces the error message Failed to find required class. The issue can be fixed as follows:
a. Import the form and open it in Form Composer.
b. Copy the name of the form from the Property Grid:
c. Select the Source Code tab at the bottom of the design pane.
d. Replace the string InspectForm with the copied form name.
e. Save the form, close it and reopen it.
13. An error is generated when saving the form if it contains a control name that starts with a number. This can also cause issues with stored procedures.
Error Invalid token '1' in class, struct, or interface member declaration 25 87
14. Using the Bezier
theme can cause an error
when a form is created. The form can be created when the error is closed
but can't be used in Data Collect. It also causes the border for several
components, such as static labels, to not be shown. TS 53304
15. After drilling down into a report two levels or more the Return to parent report button occasionally causes an error to occur. TS 17048
16. If a system has network printers installed on it, the Travel Service will have to be set to log onto the system using a local system administrator account that is also a domain user – otherwise, the network printers will not be available when the Travel Service is started.