3
10.4.5442 Breaks Custom Fields ??
Problem reported by Mike Galusha - 12/1/2014 at 9:14 AM
Resolved
Upgraded to 10.4.5442 last evening and my CSRs are reporting that they can no longer enter/manipulate data in their custom fields in non-IE browsers.

Anyone else having issues with this?  Any known fixes?  Thanks in advance.

8 Replies

Reply to Thread
0
Mike Galusha Replied
To be more specific, when choosing the custom fields tab in a ticket any edits are not saved when the "save" button is pressed - and a message is displayed stating "No items to show in this list".
I have verified that this is in all browsers.
0
Sergio Zozulenko Replied
Same issue here. Got a ticket opened with them regarding Custom Field issues. This was supposed to be a fix, and it went and caused this problem.

Only way we found to get around it, is to enable the custom fields in the Communication View in the template. And put in the values from there instead of the Custom Fields tab. That seems to work with simple text fields, but doesn't seem to save values from drop-down lists.

Its become a huge headache where on some brands, we had to disable them completely just to be able to process tickets.
0
Mike Galusha Replied
Is it possible to rollback the application leaving the new tickets in-place? This is a business-crushing issue for us. looking for options.
0
Steve Reid Replied
If this is important and you need help asap then you should open a support ticket.
0
Mike Galusha Replied
It's very important, a support ticket has been created.
2
Employee Replied
Employee Post
Hello all,
I have a custom build that will fix this issue.  Please uninstall your current version of SmarterTrack, and then install this build.
 
0
Sergio Zozulenko Replied
This has fixed the issue with Tickets. However, you now cannot save Custom Fields to Call Logs.

Upon filling out the Custom Fields tab in a Call Log and hitting Save, the custom fields tab goes blank and the custom fields no longer show.

Saving the Call Log and looking at it after its saved confirms the fields were not saved. It even allowed the Call Log to be saved with required fields not filled out.

I have updated my ticket with a video showing the issue, but wanted to update this post in case someone else encounters the same issue after upgrading.
0
Grady Werner Replied
Employee Post
Thanks for the feedback. This secondary issue was resolved by build 10.4.5451 (released 2014-12-04).

Please let us know if you have any further issue with this.
Grady Werner SmarterTools Inc. www.smartertools.com

Reply to Thread