Error running Script in FMS Scheduler

September 8, 200817 yr

Hi,

I am running a simple update script from the FMServer Scheduler.

It finds some records and tries to do a Replace.

Runs fine from FMPro.

Here is the error in the event.log:

scripting error (301) at "Invoices Update Quote Forecasts : Replace Field Contents".

2008-09-08 12:10:40.974 -0800

Is "Replace" not a valid command to be run from the server?

I can't find a document on running FM Scripts from Server.

Also, it is frustrating because I don't get an error email when there was an error running the script....

Any help is appreciated. I still have my robot machine running other scripts the old way so maybe will just move this one back. Has anyone heard anything on enhancements to SASE. It's a great concept but not quite ready for prime-time.

Thanks.

September 8, 200817 yr

Replace Field Contents should be able to be used as a script step with FMS server side scripting. Error 301 means that a record was locked. Either another user is in the record or you are.

Make sure that you put in a commit [] after the replace field contents as well.

September 8, 200817 yr

Does the Replace command need to be run on a layout with the field present?

September 9, 200817 yr

Hi, Julie.

Check to be sure yu didn't leave the dialog to display on this step. That will invalidate the server side script.

Steven

September 9, 200817 yr

Does the Replace command need to be run on a layout with the field present?

Hi Vaughan,

If running Replace Field Contents manually then we need to be able to put our cursor in a field but not when scripted. I believe the behavior changed with vs. 7. Scripted RFCs can specify both the field to copy from and the field to replace. If it is used to set a related field, it will use the current parent found set and replace all the children with the related values.

If there is more than one parent value then it will set all related records with the last 'related' parent's value. If you run RFC through the child table, it will set all the related child records with the first parent value (because that's all it sees). It's pretty cool but it can also bite if one isn't clear on what it is setting behind the scenes. :wink2: