7.20.20 Release Notes

In the Inspection module, you can now change the sequence of the violation codes with new up and down arrow buttons.

To find the new feature, do the following.

• In the Inspection module, click the Violations tab.

  Below the violation code list, the new up and down arrows for sequencing appear.

  

In the Incident module, you can now change the sequence of both unit and personnel records with new up and down arrow buttons.

To find the new feature, do the following.

• In the Incident module, click the Units & Personnel tab.

  Below the Units and Personnel lists, the new up and down arrows for sequencing appear.

  

In the Journal module, you can now hide or display expired permits in the calendar view. Expired permits are included in the Occupancy, Inspection, Activities and Expired Permits queries.

To find the new feature, do the following.

• In the Journal module, in the lower left corner of the dialog box, click Filtering.

  The Filtering Options dialog box appears, displaying the new Hide Expired Permits check box.

  

In the Occupancy module, on the Additional Records tab, when you click Chemical Inventory, the Chemical Inventory dialog box appears. On the Basic tab, in Actual Amount, you can now specify a decimal value in the field.

In the main FH toolbar, when you click Messages, the Daily Reminders dialog box appears. In the lower right corner, when you click the Staff Birthdays icon, the staff records that included birth dates appear. If you double-click a staff record in the Daily Reminders dialog box, the Staff module opened and displayed the information for that staff member.

When you clicked Browse in the Staff module, the Query dialog box appeared, and the list of staff members that appeared included hidden staff members, and should not have. This has been corrected, and the Show Hidden records option has been added to the lower left corner of the Query dialog box so that you can choose to display hidden staff members in the query results as needed.

In the Administrative Options dialog box, on the General > Security tab, under Network, Multi-User, & Internal Messaging, if you selected Allow individual user preferences, the options for LOSAP and macros became individual user options when they should have been applied globally. If you then tried to use the LOSAP report or macros, the settings from Administrative Options dialog box are not applied to the user's settings.

If you updated to FH 7.18.18 Standard Edition, when you saved an automated task for running Setup Length of Service Awards (LOSAP), the setup options you selected did not save as expected.

In the Activity module, on the Basic tab, under Payroll Calculation, if you entered a value in Pay Scale, then added a participant to the activity record, the value in Pay Scale was cleared.

If you are using FH CAD Monitor with the Motorola Printrack interface, you could not set and change the query poll date and time in FH CAD Monitor.

If you right-click Inventory in the main toolbar and selected Batch Maintenance/Test Entry from the menu that appeared, the Query dialog box for the Inventory module appears.

If you selected a query that includes an ASK parameter for the unit code, you could not double-click on the specific unit code from the lookup table to open it.

In the Incident or EMS module, on the Units & Personnel tab, if you selected a unit and clicked Open, then in the Unit Response Detail dialog box that appeared, on the Usage tab, you clicked Add Other, the Usage/Purchasing Detail dialog box appeared. If you then clicked the Inventory ID lookup button, in the Query dialog box that appeared, you were not able use the Shift or Ctrl key to select multiple pieces of equipment.

If you ran the NFPA Yearly Fire Experience Report, Error 1190 appeared, stating that the a temp file is too large. at line 176 of procedure/method RPTFIREEXP.DBSESSION.VIEWCREATE.

Error 1190: File c:\users\brende~1.esp\appdata\local\temp\00000rdv02k.tmp is too large. at line 176 of procedure/method RPTFIREEXP.DBSESSION.VIEWCREATE.

In the Incident module, the Query dialog box displayed only incomplete incidents from the selected alarm date, instead of all incidents for that date.

If you are using FH CAD Monitor to import NFIRS fields in XML data files from Medic NXT, reports were not marked as completed in Firehouse if the EMS record was created in Medic NXT.

In the Administrative Options dialog box, on the Incident > All Incidents > Authorizations & Locking tab, under Automatically Lock Incident Reports, in Disallow changes ____ hours after initial report entry, you can specify the number of hours an incident report is to be open for editing to non-administrative users before FH automatically locks it.

In the Journal module, for month or day view, some fire incidents indicated that they were automatically locked before this time limit had been reached.

In the EMS module, if you complete the report and then right-click the Save button and choose Save & Close from the menu that appears, validation does not run on the record as expected.

In the Staff Activity module, if you clicked the Code column header to sort in ascending order, then double-clicked the Participant column header to sort the employees, error messages appeared. If you clicked Ignore in the error message windows, the following error appeared.

2199 Error building key for index.

After installing the Bi-Weekly Payroll Report query, when you ran it, the query results listed a specific number of records found. However, if you clicked + + (the Select All icon) in the lower right corner of the Query dialog box, the number of selected records did not match the number of records found by the query.

(When using SQL Server 2012 with Firehouse) If you choose Administration → Users and Security, then in the Users and Security dialog box that appears, you select a user name, and then click Properties, the User Setup dialog box appears. On the General tab, under the Group Memberships list, if you selected the groups you wanted to add the user to and clicked Save, the following error messages appeared.

102 Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '44446'.

2627 Record already exists in table 'dbo.usr_memb'. The duplicate key value is (_3R40YW2XK,_SA617CP9E).

These errors also appeared if you tried to add the user to a group from the Users and Security dialog box, through the User Groups tab.

If you updated to Firehouse 7.20.10, when you tried to open the Schedule module, the following error messages appeared.

Error 2005: Error loading file - record number 5. SCH_CTRL <or one of its members>. Loading form or the data environment : Connectivity error: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server not found at line 74 of procedure/method APP.DOFORM.

If you have a report that uses parentheses as part of a filter in the query, the report runs as expected the first time. However, if you closed Firehouse and reopened it, then ran the report again, the following error messages appeared.

Error creating view act_staff_id in database c:\users\tom\appdata\temp\fhtemp.dbc

error 1231 (missing operand)

If you choose Administration→ Automated Tasks, the Automated Task Setup dialog box appears; if you then click New, the Automated Task Properties dialog box appears. In it, you can scroll down and select Run Custom Data Export, and then click Setup Task Parameters. In the Custom Data Export dialog box that appears next, you can select the NEMSIS data export you want to run, and then finish setting up the automated task parameters.

When the report ran through the automated task service, no data appeared in the report.