Sage 100

Sage100C Advanced - Broadcast messages not being received. Just upgraded a client to Sage100 version 2016 (from 2015) and it is Sage100 C. Most users are not getting the broadcast messages. I found a setting in role maintenance (tab #3 module options) under library master ""receive Broadcast messages"" I turned that on for all available roles and had everyone log out and back on even though that didn't seem necessary but most users are not getting the messages. Users for this client use the feature constantly throughout the day (of course). to alert each other of various happenings in Sage100 (product outages, availability etc.) so it is really important to them. before I call Sage, has anyone seen this or am I missing some other setting?

What product update are they on? I usually check on these 3 (same tab you ref) to allow broadcast and receive broadcast as well as receive system shutdown notices.

they are on 2016 PU2 I had them test and if they are in classic mode it seems to fix those that can't get the messages. new information: those that DO receive the messages in the new user interface, if they don't close the message (or notice it) then it locks up Sage100

Charming, system lockups...so much for that shiny new facelift on the user interface.

Not the first with Classic vs the new look. Last spring, I could not VI into PR (legacy modules) using the new shiny interface. had to do it in classic. Go figure.

I hear ya! I called Sage - ""no one has reported that. We will do internal testing"" emailed the client that the current work around will have to be to switch to classic view. I have not heard back yet but I'm sure that won't be well received.

UPDATE I Called Sage back today and bugged them I got Ronnie Aspe and he had an installation handy with 2 workstations that he could test with. He was able to duplicate this. I'm guessing nobody has reported this earlier since most clients only use broadcast to kick user out anyway. That is typically what I use it for and once I broadcast the message if users don't get out within a reasonable time frame I assume they are not at their desk and I start kicking them out. Now with 2016 we can't assume they are not at their desk. Ronnie is going to write it up and submit it to engineering.

Good ol Ronnie!!!!!! It will be a very dark day when he leaves.....

I'm 100% in agreement with that!