Form Triggers do not fire with custom OnLookup code

Comments

• Options

  girish.joshi Member Posts: 407

  2008-05-07

  When you call Validate("Location Code") only the Table level validations would get called, not the form level validations.
  
  Instead, the code that you have in your Form Validate triggers could be moved to separate function and instead of Validate, you could call that function.
  
  I have to say that I'm pretty suspicious of this design, however.
  
  Are you *sure* this is the only way to accomplish whatever you are trying to do?

  0
• Options

  Grant Member Posts: 30

  2008-05-07

  Thanks for the quick response - by the way, you should know that I relocated the custom Lookup code to the form level from the table level, and it still does not call the form level validations. I thought that might be one "alternative", even though I don't like the thought of moving my code to the Forms from the Tables for any number of good reasons.
  
  As for what I'm really trying to do - it boils down to the fact that I need to:
  1. Set a variable before the Lookup form is called based on a value in a field in the current record.
  2. Have the Lookup form's behavior be altered based on the value of that field.
  3. Potentially run some alternate field validation code if the user selected a value from the Lookup form, based on certain circumstances.
  
  I'm thinking that I'll have to live with these deficiencies. After all, NAV should not have any code in their form-level triggers, so there should be no problem if those triggers don't get called, right?

  0
• Options

  girish.joshi Member Posts: 407

  2008-05-08

  No problem.
  
  You don't have code to the table validation trigger - you just shouldn't try to automatically run code from teh form validation trigger. You can put your code in your function on the form, and call it your function (instead of validate) from the onlookup trigger. Shouldn't hold you back too much.
  
  As you noticed, NAV doesn't really put code into the forms - and there is good reason for this. If you can avoid this, you should.
  
  The basic principle is that your business logic should be data driven, not action driven. And the logic should be more or less the same if the initial data conditions are met. If you must have different behavior that is action driven, find some data that you can set, and use that to determine which code actually gets run.

  0
• Options

  kine Member Posts: 12,562

  2008-05-08

  You need to use the OnLookup on the form in correct way to make the form call OnValidate and OnAfterValidate:

  CLEAR(MyLocationLookup);
  IF MyLocation.GET THEN
  MyLocationLookup.SETRECORD(MyLocation);
  
  MyLocationLookup.LOOKUPMODE := TRUE;
  IF MyLocationLookup.RUNMODAL = ACTION::LookupOK THEN BEGIN
    MyLocationLookup.GETRECORD(MyLocation);
    Text := MyLocation.Code;
    Exit(True);
  End Else
    Exit(False);
  

  
  The trigger has one parameter "Text" and return value of type boolean - was something selected or it was canceled...

  Kamil Sacek
  MVP - Dynamics NAV
  My BLOG
  NAVERTICA a.s.

  0
• Options

  Grant Member Posts: 30

  2008-05-08

  Thanks for the feedback - I copied & pasted the Lookup code from the Table to the Form, should have caught there was a return code on the Form (there isn't on the Table). So no problem validating when code is at the form level.
  
  Original "problem" still remains - Form-level Validations do not fire when coding custom lookups at the Table level, and I really don't want to relocate my lookup code to the Form level.

  0