Error: Unhandled script exception: Bad Datatype detected for operation EXCEPTION_CLASS_SCRIPT_BAD_TYPE SCRIPT_CMD_COLUMNOFTABLE

Issue:

The following error appears when you click the Exceptions button in the Inactivity Timeout Advanced Settings window:

Unhandled script exception:

Bad Datatype detected for operation

EXCEPTION_CLASS_SCRIPT_BAD_TYPE

SCRIPT_CMD_COLUMNOFTABLE

Cause:

This issue has been recently documented as a software bug.

Workaround:

Adding Inactivity Timeout Exceptions

To add an Exception, follow these steps:

1. Click OK to the error message.
2. In the Inactivity Timeout Exceptions window, click the Add Exception button (+).
3. Enter the Product ID, Form Technical Name (if there is one associated with the Script Name), and the Script Name.
4. Click Save.
5. Click OK.

Note: It will not display in the window due to the bug and the error message will appear if you click Redisplay.

Viewing Inactivity Timeout Exceptions

To view the Exceptions, use the following steps to create a SmartList Designer report for the RSTBIT04 table which holds the Exception values.

1. Click OK to the error message.
2. Close the Inactivity Timeout Exceptions window.
3. Go to Microsoft Dynamics GP | SmartList.
4. Click New.
5. Expand Dynamics GP Toolbox, Tables, and then System.
6. Mark the RSTB Timeout Exceptions Setup table checkbox.
7. Click OK.
8. The new report will populate with the records from the RSTBIT04 table.