Code

Re: Afterchange code looping

Agni Jonnalagadda — Tue, 28 Aug 2007 17:02:41 GMT

You need to validate your code well here, becuase when you empty a field only "Delete" event gets fired. If you need to perform some operations even when the node becomes empty then you need to have another if condition for "Delete" operation.

Re: Afterchange code looping

shaun.nieves — Tue, 28 Aug 2007 16:23:55 GMT

I don't have a lot of experience with this but I think it's because of the way the DOM works. For onAfter and before changes fire twice. One for insert and one for delete. This is covered in Patrick Halsteads book so if you're going to be doing a lot of custom work I highly recommend it. The jist of it is you have to filter out one of the events. For instance

If (e.Operation = "Insert") Then

do something

End if

Do something will fire only on the insert and not for delete. I hope that made sense. Good luck!

Afterchange code looping

ninjaben — Tue, 28 Aug 2007 13:27:53 GMT

Hello,

i am having problems with an afterchange event on a date field with a confirm dialogue, the code is as follows:

function msoxd_my_Overall_Implementation_Date:nAfterChange(eventObj)

{

if (eventObj.IsUndoRedo)

{

}

var resp = XDocument.UI.Confirm("Are you sure you want to commit to this date?",4);

var objDataElement = XDocument.DOM.selectSingleNode("/my:myFields/my:field116");

objDataElement.text = resp;

}

The problem we are encountering is that the code loops through twice, the first time it makes the field required, then the second it adds the date, is anyone aware of a way to fix to this matter?

Thank you

Ben