{"id":1024,"date":"2016-09-30T14:11:48","date_gmt":"2016-09-30T19:11:48","guid":{"rendered":"http:\/\/www.iqaccountingsolutions.com\/blog\/?p=1024"},"modified":"2016-09-30T14:11:48","modified_gmt":"2016-09-30T19:11:48","slug":"bug-sage-50-2017-customer-notifications","status":"publish","type":"post","link":"https:\/\/www.iqaccountingsolutions.com\/blog\/bug-sage-50-2017-customer-notifications\/","title":{"rendered":"Bug in Sage 50 2017 Customer Notifications"},"content":{"rendered":"<h3>IF YOU USE THE &#8220;ALWAYS NOTIFY&#8221; FEATURE FOR CUSTOMERS, DO NOT UPGRADE TO VERSION 2017 YET!<\/h3>\n<p>If you have been waiting to upgrade to version 2017 of Sage 50, you may want to wait a little longer. In my Sept 2016 newsletter I said that I hadn&#8217;t found any significant problems in Sage 50 2017 and encouraged people to go ahead with the upgrade. But it looks like I spoke too soon.<\/p>\n<p>There is a very useful feature that allows you to create notifications that pop up any time you enter a transaction for a customer. You can read about the feature <a href=\"http:\/\/iqaccountingsolutions.us2.list-manage1.com\/track\/click?u=0b92990bba1267be26b8ca6db&amp;id=e8e453e4d4&amp;e=b0476d6293\">here<\/a>. However there is a problem with it in version 2017.0.<\/p>\n<p>Any notifications that are already set up before upgrading will continue to work properly, but if you try to view or edit the message in\u00a0 <em>Maintain Customers<\/em>, the <em>Message<\/em> field will appear blank.<\/p>\n<p>If you try to add a notification for a customer that didn&#8217;t have one before you upgraded, the message will appear to save correctly, but if you close the <em>Maintain Customers <\/em>window and come back to it, the <em>Message<\/em> field will be blank. If you enter an invoice or other transaction for that customer, instead of getting the message that you created, you&#8217;ll get a message that says &#8220;You have requested to be notified when a transaction is created for this customer.&#8221;<\/p>\n<p>Sage says this is a known issue and it will be addressed in the 2017.1 update, which is currently scheduled to be released in November 2016.<\/p>\n<p>My apologies to Sherrie and anyone else who went ahead with the upgrade on my recommendation.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>IF YOU USE THE &#8220;ALWAYS NOTIFY&#8221; FEATURE FOR CUSTOMERS, DO NOT UPGRADE TO VERSION 2017 YET! If you have been waiting to upgrade to version 2017 of Sage 50, you may want to wait a little longer. In my Sept 2016 newsletter I said that I hadn&#8217;t found any significant problems in Sage 50 2017 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[9,3],"tags":[],"_links":{"self":[{"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/1024"}],"collection":[{"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/comments?post=1024"}],"version-history":[{"count":1,"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/1024\/revisions"}],"predecessor-version":[{"id":1025,"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/1024\/revisions\/1025"}],"wp:attachment":[{"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=1024"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=1024"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=1024"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}