**
 
L. J.,
 
Have you mapped the 'On Close' values of the dialogue box window open action? If you have done this mapping there is no known way of why the commit changes action should fail... hope this helps
 
Cheers
 
Joe D'Souza
Remedy Developer / Consultant,
BearingPoint,
Virginia.


----- Original Message ----
From: L. J. Head <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Friday, September 22, 2006 1:50:47 PM
Subject: Re: Commit Changes on Dialog Parent

**
That may be the route I end up taking but I was looking for someone with experience of why the commit that I have in place isn't doing what it's supposed to be doing
 

L. J. Head
Software Engineer
Remedy Approved Consultant

 


From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Roney Samuel
Sent: Friday, September 22, 2006 11:43 AM
To: arslist@ARSLIST.ORG
Subject: Re: Commit Changes on Dialog Parent

** Dear L. J. Head,
                        A simple workaround for this situation would be to set a temp field with a value "Yes" on Commit Action on the Dialog form. Then write another AL on the same action that you performed to invoke the Dialog form at a later execution order and check if the temp field is set to "Yes". If it is then save the record. Hope this helps.

Regards,
Roney Samuel Varghese


On 9/22/06, L. J. Head <[EMAIL PROTECTED]> wrote:
**
Here is the situation.  Form A opens Dialog of Form B.  On button press on Dialog B I want to set a field on Form A and Save the record of form A.
 
I have the button press on Dialog B performing an Event
I have an AL retrieving that event and doing a setfield for me...this all works.  When I run logging I see the 'Commit Changes' action fire...but it doesn't commit changes...anyone else experience this and know of a work around?
 
AR 6.3

L. J. Head
Software Engineer
Remedy Approved Consultant


__20060125_______________________This posting was submitted with HTML in it___

Reply via email to