Hi
Am trying to make a script to trigger on record load.
I have set the script in the trigger. But it keep looping the script..
If i start the script manually it works fine. So am guessing there is something wrong with the trigger it self ?
Or is there another way to make a script run every time a new record is entered ?
Am running Filemaker 14 Client on windows OS.
Hi Stigge
Maybe you could perform this script in your "New record" script if you have one? Then the script would run only when you create a new record.
Or do you want it to run when you enter new data in a record?
Chloé
I have created a change log. so i need to have it runned every time a new record is viewed. to create the fields values from start. so i can track all changes.
Perhaps an audit trail field would be a better solution for you. This can run automatically whenever a field value is changed, without any scripting—see for example NightWing's Ultralog Demo: NightWing Enterprises - UltraLog v2.x Audit Logging Demo for FileMaker Pro
Thats what am building myself. am not a big fan of using plugins.
Ultralog is not a plugin, it uses native FM including a custom function which comes with the demo file. Take a look. Why reinvent the wheel?
Becouse there is a cost to it =)
What about your script then? Do you go to another layout and come back to the one you're in? This would re-trigger OnRecordLoad.
Yes, that exacly what happends.
I might have solved it now.. by using an IF with a variable that i set to 1 after running the script. and inside that IF i have a exit script.. that seems to work..
also i needed the script to run when i enter next record. so that was a bit tricky.. but think i solved it now by using global variables that i set the values in other scripts aswell. that way i came around the issue..
I'm glad you found a way around. Can't you do the same without changing layout though? That way you could avoid the IF statement if the latter is preventing the OnRecordLoad trigger to work when you load the next record.
=)
Not sure if i can that.. :/ Havent really tested to controll another table from another table before to be honest....
Well it depends on what you're doing with your script
But if it's just setting the value of a field in a related record, I think you could do it via a relationship without changing record/layout.
am creating change logs.. so am creating new records and filling the log fields.. thats it..
Nice, had no idee =D thats going to help alot
I've implemented a very simple log, a bit like you do as the client didn't want a full log file.
Here is how I log the deletion of a portal row for example:
And this is the corresponding TOs in the database graph:
The "Allow creation of records..." is ticked for the log TO, so when I set a field in this table in the script, it creates a new record and set log_create to the auto-enter creation timestamp of the log record (it kind of does the relationship itself).
That's how you can log specific things without changing layout.
Hope this helps
Thank you !!
I have a question along this topic line.
I have a table with two types of transactions. Sold tokens to members and purchased token from mother organization.
I have this script to run on record load. This is to create a mask when browsing the records.
If it is sale to member a the proper layout is showed. If a purchase from mother organization the other layer.
This is fine when browsing the records, but causes a problem when creating a new record.
I need to figure a way to select the correct layout when I create a new record.
StampsQtySold is an auto enter which is created when the new record is created.
This is my way of knowing the record is a sale vs a purchase.
Thanks in advance.
I think I solved the issue.
I created a field "record type" with the option of sale or purchase.
I create two buttons.
Sale button which triggers a script to create anew record, set record type field to "sale" and brings me to the proper layout.
Purchase button which triggers a different script which sets the record type field to "purchase" and brings me to the other layout.
No my script above linked to a on record load bring the proper layout based on the transaction record.
Clunky but its doing what I need.
Thanks
I've implemented a very simple log, a bit like you do as the client didn't want a full log file.
Here is how I log the deletion of a portal row for example:
And this is the corresponding TOs in the database graph:
The "Allow creation of records..." is ticked for the log TO, so when I set a field in this table in the script, it creates a new record and set log_create to the auto-enter creation timestamp of the log record (it kind of does the relationship itself).
That's how you can log specific things without changing layout.
Hope this helps