Bug #8390
closedPFMEA & DFMEA: Can't able to Open the Document its displaying an Error Message as "Object Error Number 64928 has occurred in SortedCollection::CompareSingle"
0%
1.Open the Browser
2.Enter the URL
3.Enter the Username and Password
4.Click on Login Button
5.Click on Module icon
6.Click on AQuAPro
7.Click on Main Menu
8.Select the PI -> Open PFMEA Document
9.Enter the Value in Recommended Actions Column
10.Right-Click to Select Insert Branch in the added Recommended Action Cell
11.Then Add another Recommended Actions in the Created Branch
12.Now Right-Click on the Header and Select the Refresh Document option (or) Again Open the PFMEA Document
13.Observe the Result
Description
In the PFMEA & DFMEA Document, by Opening the Document its displaying as "Object Error Number 64928 has occurred in SortedCollection::CompareSingle. The text of the message is: ?ErrUtInvSrtKeys?"
Note: By this Scenario only this Error is occurring "If we adding the Value in Recommended Actions Column and creating New Column in the same Recommended Actions Column and adding another Recommended Action and by Refresh the Document or else by Opening the Document again this will display"
Files
Updated by Anonymous over 6 years ago
- Subject changed from PFMEA: Can't able to Open the Document its displaying an Error Message as "Object Error Number 64928 has occurred in SortedCollection::CompareSingle" to PFMEA & DFMEA: Can't able to Open the Document its displaying an Error Message as "Object Error Number 64928 has occurred in SortedCollection::CompareSingle"
- Description updated (diff)
Updated by Sugesh g pillai over 6 years ago
- Status changed from Open to Resolved
Fixed and will be available in next build 9/22
Updated by Sugesh g pillai over 6 years ago
- Assignee changed from Sugesh g pillai to Anonymous
Updated by Anonymous over 6 years ago
- File Issue No 8390 Replicating on 27.09.2018.jpg Issue No 8390 Replicating on 27.09.2018.jpg added
- Status changed from Resolved to Not Resolved
This Issue is Not Resolved and its Replicating Now also so Changing the Status as Not Resolved on 27.09.2018
Updated by Sugesh g pillai over 6 years ago
- Status changed from Not Resolved to Resolved
- Assignee changed from Anonymous to Sugesh g pillai
Fixed setting the sort information in reorg for document that don’t have it set properly. This should fix this error that is displayed when a user tries to open the document:Will be available for build on 10/08/2018