application.getMethodTriggerFormName() gives me different results depending on the scope of the method, form or global.
All methods in the following explanation are triggered via onRecordSave.
-
If I attach a form method to the ‘onRecordSave’ trigger and perform gMTFN(), the function reports the correct form name. ![Neutral :|]()
-
If I attach a global method to the ‘onRecordSave’ trigger and perform gMTFN(), the function reports an incorrect form name. The form name reported seems to be a parent in a relationship (conCustomers_to_conAddresses) but that could be a coincidence. ![Confused :?]()
-
Like 1) I attach a form method to the onRecordSave trigger and then call the global method which performs gMTFN. gMTFN within the global method now reports the correct form name ![Shocked :shock:]()
I had a similar problem when combining it with addFoundSetFilterParam. Maybe try testing this by triggering with a button rather than onRecordSave. since that will make sure it isn’t something to do with what constitues a saved record event.
yes i already fixed this for 2.2b3 please retest it when it comes out and let me know if you still find strange things in this area
I have written a sample solution where the anomaly is no longer occuring.
That being said, I still experience problems with my main solution in a related area. I had to rebuild forms (partialy or complete) before to eliminate unexpected bahaviour. This doesn’t suprise me too much, considering that the repository format has been changed a couple of times since I started.
I’ll report back.