This topic describes resolutions or solutions in GainSeeker version 9.1 and corrections to the Online User Guide.
When using the GainSeeker Charts module or the Dynamic Reports module to filter for a traceability value, GainSeeker did not automatically uppercase the value that you manually typed into the stored filter or quick filter. This could be a problem on case-sensitive databases because GainSeeker always stores uppercase traceability values for SPC and DMS data, so a filter for lowercase traceability values would never return any data. GainSeeker now correctly uppercases traceability values in stored filters and quick filters. This issue has been resolved.
Deleting an inspection, planned inspection, template, planned session, or stored session did not log this event in the Audit Trail. These items are now written to Audit Trail when deleted. This issue has been resolved.
When creating or editing a stored filter, after selecting the Show Existing Data Table Values check box to display a list of all values that exist in the traceability column, changing the Test for that row would leave the Show Existing Data Table Values check box selected but display the predefined list of values for the new traceability column. The workaround was to clear the Show Existing Data Table Values check box and then select the check box again. Now when the Test is changed on a row, the Show Existing Data Table Values check box is automatically cleared. This issue has been resolved.
When creating or editing a stored filter, after creating two filter rows and then deleting one of those rows, clicking the Build Multi Row Filter button could generate an "Object reference not set to an instance of an object" error. This issue has been resolved.
All GainSeeker modules failed to correctly import a GainSeeker License file, except for the GSSetup.exe utility. This issue has been resolved.
When Windows was configured for a language other than English, GainSeeker could generate an error - especially in the Administration module on the Configurations tab. This issue has been resolved.
The SPC Data Entry and SPC Designer modules erroneously required a GainSeeker OPC license that is no longer used. This issue has been resolved.
In the GainSeeker Charts, PC Collect, GainSeeker Inspections, and GainSeeker Utility modules, SPC corrective actions (Event, Cause, or Action Taken) set to Hide Everywhere could still be assigned to a data record. This issue has been resolved.
When using command line parameters to automatically open and email a chart, dashboard, or desktop, the command line parameter ExportType=EmailHTML would fail to send the email. This issue has been resolved.
When using the Desktop menu to email multiple chart windows, if the Include attachment for each item check box was selected and an item was cleared from the Include in email list, GainSeeker would remove that item from the email body but still include it as an email attachment. This issue has been resolved.
When generating SPC Charts and selecting all SPC standards, applying a filter for traceability field 7 or higher would fail to retrieve the correct data for those standards. This issue has been resolved.
After generating a chart of external data, any user attempts to change Retrieval/Configuration settings or Standard Overrides for that chart were unsuccessful. This issue has been resolved.
When charting external data, choosing a Statistics Table chart window and selecting any report name except "Default" could generate an error. This issue has been resolved.
When charting external SPC data, options to group data were not available or did not work correctly. This issue has been resolved.
When a chart of external DMS data was displayed, the Group/Sort toolbar button was erroneously disabled. This issue has been resolved.
When charting external DMS data, getting Cost information from a traceability field did not work correctly. This issue has been resolved.
When configuring a dashboard component to display GainSeeker statistics, appending another statistic would overwrite the last statistic in the label if the cursor was in the middle of the label. Statistics are now correctly appended to the end of the label, no matter where the cursor is located. This issue has been resolved.
When a Multiple Data Table was displayed, right-clicking a data cell would display a menu with the option to Delete data, but clicking Delete did not actually delete any data. Right-clicking a Multiple Data Table no longer displays the option to delete data. This issue has been resolved.
When viewing a Short Run SPC control chart with data grouped by SPC standard, right-clicking the chart and choosing New chart for group or New charts for groups would generate a new chart window that displayed the message "No Chart Available". This issue has been resolved.
Changing the ValueMinimum and ValueMaximum properties on a DMS Bar Gage dashboard control could sometimes cause GainSeeker to stop working. This issue has been resolved.
When saving a Dynamic Desktop, clicking the Delete button did not actually delete the selected desktop. This issue has been resolved.
Using the chart settings to display a different OEE Goal value for an OEE chart would not update the chart correctly. This issue has been resolved.
When an External Data chart was displayed, the charting toolbar erroneously allowed the user to set a Filter and a Date period. This issue has been resolved.
When editing a Dashboard, pressing the Ctrl key while clicking on an existing dashboard control would erroneously change the Location of that dashboard control. This issue has been resolved.
When displaying charts, the default chart skin for the configuration was not applied to the charts if the user did not have rights to override the chart settings. For users without the right to override chart settings, GainSeeker will now apply the default chart skin for the configuration when drawing charts. This issue has been resolved.
After brushing data points on a control chart and using them to make a new data table of brushed data, deleting a record from that table of brushed data failed to remove that row from the table. This issue has been resolved.
When an SPC data table displayed a column for Outlier, drawing a Pareto chart for that data table would generate an error message. This issue has been resolved.
When resizing the GainSeeker Charts window to a certain height, it was possible to partly or completely cover up the login name in the top right corner of the window. This issue has been resolved.
A Dashboard Grid control that was configured to display region colors based on cost or percentage statistics would fail to display the colors. This issue has been resolved.
A Dashboard Grid control that was configured to display a custom statistic could generate the error "An item with the same key has already been added". This issue has been resolved.
When the GainSeeker user role did not allow changing of Chart Overrides or Retrieval/Configuration settings, attempting to open the Settings window for a drilled-down Pareto chart caused the GainSeeker to stop working. This issue has been resolved.
When using Edit/Open to open a Dashboard that contains at least two Dashboard Grid controls, two Big Data DMS controls, or two Big Data SPC controls, changing the filter or date on two or more of the same type of control would cause the property to be changed on one control but not the other. This issue has been resolved.
When viewing a Dashboard Grid control with DMS data columns, if the rows are defined by something other than Part Number or Process, right-clicking in a cell and selecting View Data would display the message "No Data Found" even if data actually existed for that cell. This issue has been resolved.
Generating a Monitor Table chart would sometimes crash if all standards were selected. This issue has been resolved.
The list of Inspections was correctly sorted in alphabetical order when managing Inspections but not when creating or editing a Planned Inspection. Both lists of Inspections are now correctly displayed in alphabetical order. This issue has been resolved.
When editing a Checkbox test whose ExtraTrace property had been left blank, that property would sometimes erroneously display "TextEntry" (although this had no effect on how data was collected and stored). This issue has been resolved.
On the Manage Planned Inspections window, selecting the Debug check box and then clicking Run failed to display the list of Python scripts so that the user could place breakpoints in the scripts before running the planned inspection. This issue has been resolved.
Copying an Inspection that had users assigned to it would generate a "Data at the root level is invalid" error. This issue has been resolved.
On a sub-inspection with an OnChange formula, when the inspection was long enough to display a vertical scrollbar, sometimes interacting with one of the bottom tests would erroneously scroll back to the top of the sub-inspection. This issue has been resolved.
When a Traceability test or DMS Part Number test was automatically filled with a value from a previous inspection or sub-inspection, this could sometimes trigger an OnChange formula. This issue has been resolved.
When the user clicked a button (a Formula test with FormulaMode set to Click) on a sub-inspection, the focus did not return to that button after its Python script had finished running. This meant that pressing the TAB key to move to the next test on the sub-inspection would instead move to the first test at the top of the sub-inspection. This issue has been resolved.
When charting External data from a Python script, if no date/time stamps were specified in the Python script, the first two DMS data records could erroneously have the same date/time stamp. This could happen if the Python script specified a Part Number without a Process, or a Process without a Part Number. This issue has been resolved.
Instructions for comparing Python commands with Template commands referenced the wrong filename (TemplateToPythonCommands.txt). This filename has been corrected to TemplatePythonGuide.txt . This issue has been resolved.
OPC commands could not connect to any server except 'localhost'. GainSeeker now installs and registers newer .dll files that make it possible to connect to other OPC servers. This issue has been resolved.
When using the traceability.insertvalue() method to insert values into the pre-defined lists for traceability fields 7-48, duplicate values could be erroneously entered for the same traceability field. This issue has been resolved.
Using the retrdms.external.event command to set an Event that does not already exist in GainSeeker could sometimes generate an error. This issue has been resolved.
When multiple device UUIDs had identical DataItemID tags defined, the mtconnect.current command could erroneously return the values of DataItemID tags from the wrong device UUID. This issue has been resolved.
The correctiveaction.actiontakenlist, correctiveaction.causelist, and correctiveaction.eventlist commands with the onlyde parameter set to True would fail to exclude corrective action items that were set to Hide in Data Entry. These Python commands also failed to exclude corrective action items that were set to Hide Everywhere. This issue has been resolved.
When creating or editing a Custom Statistic and setting its name longer than 40 characters, this could cause the Custom Statistic to be deleted (on some databases). You are now limited to 40 characters when setting the name of a Custom Statistic. This issue has been resolved.
The System Administration module could behave unexpectedly when working on a configuration with internal configuration number 0. This issue has been resolved.
When viewing or setting Statistics Labels for a configuration, using the Contains box and Find Next button to search for a label would generate an error if no check boxes were selected in the View statistics labels for list. This issue has been resolved.
When viewing or setting Statistics Labels for a configuration, three SPC statistics were displayed under the wrong categories. This issue has been resolved.
Exporting SPC data would sometimes fail to include all of the data values in the subgroup - especially if the subgroup size was greater than 6. This issue has been resolved.
Exporting a dashboard that included a Quick Filter would display a message that the filter could not be exported. This issue has been resolved.
Exporting a dashboard that included a Data Table control with the data table columns set to Default would display a message that the data table column setting could not be exported. This issue has been resolved.
When exporting SPC or DMS data, using the Set export file button to change the file type did not correctly change the format of the data being exported, even if the file name extension was changed. This issue has been resolved.
When the LaunchPad was configured with fewer buttons, there were cases when the bottom row of buttons did not display correctly. This issue has been resolved.
When configuring a New GainSeeker Item for PC Collect to open an Inspection, Planned Inspection, or Python script, with Advanced Settings that selected a different Configuration or Login Name, the GainSeeker Item Settings window would not display the list of Inspections, Planned Inspections, or Python scripts from the selected configuration. This issue has been resolved.
In the topic for the Pass/Fail/NA test, the description of the SetNCU property contained inaccurate information about the way that data is stored when the configuration setting "Set nonconforming units = number of defects" is enabled. This issue has been resolved.
In the topic for SPC Statistics available, the statistics "Conversion multiplier" and "Paired Sample Grouping" were not listed. This issue has been resolved.