02-24-2010 07:33 AM
Any help or advice appreciated...
I have a plug-in that I've developed for ACT! Premium 2010. The requirement is to open a dialog box when a post code field is modified. This works fine having navigated between contacts. No problems. However, when I've just logged into ACT and click on the Contacts View, it won't work for the first displayed Contact. If I click next and then previous, it will fires correctly. Any ideas?
Private _ACT As Act.UI.ActApplication Public Sub OnLoad(ByVal App As Act.UI.ActApplication) Implements Act.UI.IPlugin.OnLoad _ACT = App AddHandler _ACT.CurrentContactChanged, AddressOf ContactSync End Sub Public Sub OnUnLoad() Implements Act.UI.IPlugin.OnUnLoad End Sub Public Sub ContactSync() AddHandler _ACT.ApplicationState.CurrentContact.ContactFields.FieldChanged, AddressOf ContactModified End Sub Public Sub ContactModified(ByVal FieldName As String) ' Do stuff... End Sub
02-24-2010 08:18 AM
02-24-2010 11:52 AM
06-27-2010 02:37 AM
is there any word at all from Sage on this problem??
Seems that their Trigger properties work fine all the time.. no time out.. no having to move forward one contact and back to get the change event firing
This is a MAJOR problem in that one of the most basic function that most end users ask for is "When we change this we want to know ......." and even thou i can write an app that the field can trigger its not as nice as a plugin
Come on Sage.. whats going on here with this bug??
06-28-2010 07:15 AM
We're looking into this, as you've probably noticed the events trigger normally aside from the first contact after launching the application. What most folks have done to work around the problem, is to force a refresh/save as soon as the database has opened and from that point forward all event should fire normally.
I apologize for any headaches this has caused.
06-28-2010 07:53 PM
i hear that there is also a timeout period?? as in after ACT has been sitting there for some time the field trigger event stops working then also? i think i have read that somewhere in these forums about this also preventing the event from firing?
but big thanks for the feedback as to whats happening