...
| Case # | Description | ||
|---|---|---|---|
| JC-276 | We've fixed an issue with Standard Job Billing where the RM10601 was missing the Batch ID if the Job Schedule Window wasn't opened during the creation of the job invoice. | ||
| JC-277, JC-358 | The Total Contract calculation on the following reports has been updated to include the Expected Contract amount. Time and Materials change orders are now reflected in the total as expected.
| ||
| JC-293 | Job ListView Filters on the Job Cost Signature area page are no longer cleared when performing a software upgrade. | ||
| JC-298 | The JC30003 Contract_Earned_Curr_Mo column now displays the correct amount after running the Job Close procedure. | ||
| JC-299 | When posting payroll, users will no longer receive a “Cannot insert the value NULL into column ‘WS_Markup_Percent”’ message when the contract amount and total revised forecast cost fields create a null percentage. | ||
| JC-300 | Users have the ability to again apply credit memos to all invoices, not just the Job Cost invoice assigned to the credit memo job. Also allows GP credit memos to be applied to project invoices. (This is a reversal of JC-52.) | ||
| JC-304 | The Job Cost Change Order Master node now updates the Expected Contract in table JC00102 when the change order is a posted fixed change order. (Must be posted and must be a fixed change order.) | ||
| JC-307 | Users will no longer receive an error message when running the Reconcile Jobs or Reconcile Billing utilities if the job number includes an apostrophe. | ||
| JC-308 | When a job is opened and closed in the same period, an entry is now created in the JC30003 (JC_Job_MSTR_Summary_HIST) table. | ||
| JC-310 | Users can now enter a Posting/Schedule Date that is greater than the system date but still within the current period. | ||
| JC-314 | SSRS reports now print to both HTTP and HTTPS sites. | ||
| JC-320 | A lien waiver can now be created if the PO receipt line is in history. | ||
| JC-322 | When reopening a job that has an apostrophe in the job number, users will no longer receive a syntax error and the job is reopened. | ||
| JC-326 | Users who enter a note in the Item Transaction Entry window will now be able to view the note without receiving a message that the note was deleted. | ||
| JC-327 | When a project is inactivated, the jobs associated with the project now display correctly as inactive in the Job Number Lookup window. | ||
| JC-328 | Running the Reconcile Jobs Utility now recalculates the committed costs as expected. | ||
| JC-338 | Users who open the Job Close window will now see the available jobs to close as expected. The new Job Close window is no longer assigning jobs to the last user who printed a report from the Job Close window and then exited the window (without marking any jobs to close and “Save Schedule” is not enabled). | ||
| JC-341 | In the Close Job window, now only the jobs displayed in the Available to Close section are inactivated, as expected. | ||
| JC-343 | Performance enhancements when posting a batch with a purchase order within Job Costing that included new cost codes with markup. | ||
| JC-345 | When working with retention amounts within the Subcontractors Retention window, if the Apply amount is greater than the Retention Remaining and Mark All is selected the application will display an error and will not allow you to process the transaction. | ||
JC-348, | When using the Job Close window, the job is now available to close if Contract Agreement Payment is completely processed or the payment is voided before retention is processed. | ||
| JC-354 | For users who have the Posting Options for Revenue Recognition set to None and the Closing Jobs Journal Entry not marked, the message “A batch was not created. Jobs closed may not have had transactions or the jobs had reasons for not being available." no longer displays. Instead, the following message displays “The job process is complete.” | ||
| JC-355 | Discounts are now calculated as expected on Job Cost invoices if a Master Tax Schedule in Job Cost is saved. | ||
| JC-359 | Project Billed Position now displays the correct Project Contract Earned amount for jobs that have a contract type of NTE with a posted NTE change order. | ||
| JC-361 | In the Job Close window, selecting Division as the Filter and then selecting the Filter By field in the Division Lookup pop-up window, the window now performs as expected. Users reported receiving an error message and then Microsoft Dynamics GP crashes. | ||
| JC-362 | When a job has a cost plus change order with a posted purchase order return, the contract amount and the expected contract amount on the job and change order is now correct. | ||
| JC-378 | With the Job Cost setup for Revenue Recognition Method set to None, the account index is now validated that it exists, is not inactive, and is a credit line or is an unbilled line or is a Job Cost debit line. When importing through SmartConnect and you select the WS PM Transactions node type, you can now pass the account index in for the Job Cost debit line. (Previously you could pass in an account index only for a credit line or unbilled line.)
| ||
| JC-379 | When a single line project credit memo has a job matching job in a project invoice, we will now show the other job lines from the invoice when applying the credit to the invoice. | ||
| JC-384 | Users can now edit the Reminder Date on a Job note. | ||
| JC-403 | In the WS Transaction Entry window, users should no longer receive the error message "Invalid data type for arithmetic: 15" after entering a cost code. |
TimeTrack
| Case # | Description |
|---|---|
| TT-24 | When having Use Average Salary Labor Rate is marked, TimeTrack export is now exporting all of the transactions as expected. |
| TT-85 | Fixed an issue where an error occurred when posting payroll at the execution of the SQL procedure K2aSignPostToService. |
| TT-88, TT-109, TT-108 | Job Cost transaction types (time card entry and group time entry) and imported payroll transactions for jobs now have the ADDRESS code added to each record. |
| TT-104 | Empty TimeTrack batches are no longer created from MobileTech when a technician creates a labor transaction that errors out and does not create the transaction. |
| TT-106 | The Manager Approval check is now only being run against batch(es) selected for editing and committing. |
| TT-110, TT-111 | Users will no longer receive an Invalid Object error message after selecting OK in the Time Card Entry window. |