# getMethodTriggerFormName()

**URL:** <https://forum.servoy.com/t/getmethodtriggerformname/3448>\
**Category:** Classic Servoy\
**Created:** [January 12, 2005, 10:00pm UTC](https://forum.servoy.com/t/getmethodtriggerformname/3448 "2005-01-12T22:00:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![thertzler](https://avatars.discourse-cdn.com/v4/letter/t/a3d4f5/32.png) [@thertzler](https://forum.servoy.com/u/thertzler)\
**Post date:** [January 12, 2005, 10:00pm UTC](https://forum.servoy.com/t/getmethodtriggerformname/3448/1 "2005-01-12T22:00:28Z")

</div>

I have used it before but now I have run into a problem.

On record save (onRecordSave) I call a global method which inquires about the name of the trigger form (getMethodTriggerFormName).

```auto
var f = application.getMethodTriggerFormName();

```

Unfortunately it reports not the form ‘conAddresses’ as it should but one that is the parent in a relation ship ‘conCustomerList’.

Both forms ('conCustomersList, ‘conAddresses’) are tabbed into a master form ‘conCustomers’.

Is this a known issue or I am missing something?

---

<div class="post-metadata">

**Author:** ![jcompagner](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.servoy.com/jcompagner/32/4889_2.png) [@jcompagner](https://forum.servoy.com/u/jcompagner)\
**Post date:** [January 13, 2005, 6:15pm UTC](https://forum.servoy.com/t/getmethodtriggerformname/3448/2 "2005-01-13T18:15:45Z")

</div>

yes there was a problem with form events and global methods.  
should be fixed in 2.2b3

---

<div class="post-metadata">

**Author:** ![thertzler](https://avatars.discourse-cdn.com/v4/letter/t/a3d4f5/32.png) [@thertzler](https://forum.servoy.com/u/thertzler)\
**Post date:** [January 13, 2005, 7:17pm UTC](https://forum.servoy.com/t/getmethodtriggerformname/3448/3 "2005-01-13T19:17:38Z")

</div>

Good to know. I am holding off on that portion of my solution then, because I am having more problems with a

```auto
var value = forms[form].controller.getDataProviderValue(element)

```

statement which might be associated with this one. In some case it reports a ‘undefined’ when it really shouldn’t.  
Let me know if you want to hear more about this.