There is no "Move" command so you will have to hard code the copying of data field by field from the Orders table to the Received table. There will also be many steps to get to your desired results so let us take it one step at a time.

First make sure you are in a DB that you can mess with as you will be testing out creation of records and deletion of records.

To test the creation of a new record in the Received table you can put something like this in a button on your Orders table:

let curRec := this;<--this line gathers all the data of the current record

let newReceived := (create Received);<--here we tell Ninox to create a new record in the Received table

   newReceived.(Field1 := curRec.Field1);<--now we tell Ninox to copy the data from our current record into the newly created record in the Received table

   newReceived.(Field2 := curRec.Field2)<--copy the next field, the last copy line does not need the semicolon.

If that works then you add the delete function. Again make sure you can safely delete this record. You can add the following to the above code:

delete curRec

I'll add the loop function in another post where it will look for 'Received by' and then run the code.

Hi Hardy -

A button is a "layout element". If you go to Edit Fields you will see on the right side Add layout element. From there you can add a button.

When you double click on the button field you will then add code to the On click section of the button.

Just wondering, did you create the same field and field names in the Received table?

The second post code doesn't work cause you have a semicolon after newReceived thus ending the line. What you wrote is telling Ninox to take the data in Paid and copy it to same Paid field.

what you wrote should work. i noticed that there is a space after "newReceived.". There shouldn't be any spaces.

let curRec := this;
let newReceived := (create Received);
newReceived.('Ordered by' := curRec.'Ordered by');

When you type newReceived. then start typing the name of the field does it bring up the field name for you to select?

Hardy

Depending on what the field (Receive by) is - ie text field

I would have though you could test for the script to run on trigger after update on that field.

so instead of having the code in button you put it in that field

and pre test it to say if 'required by' = 1 etc then run the script!

Hi Hardy -

Glad the button is working. What Mel suggest is still two steps away, I am breaking down the steps so you can understand what is going on. Plus it is always a good to test scripts like this in a button that you can control before applying it.

The next step is to add an if statement before the code so it will only create a new record when 'Received By' = 1 or 2 or 3.

We will stay with the button until the code is finished. Add the following:

if 'Received By' = 1 or 'Received By' = 2 or 'Received By' = 3 then

current code

end

If that all works then you can copy the button code to the Trigger after update part of the 'Received By' field, if that is when you want Ninox to check to see if it needs to copy the record. Otherwise put in the field that makes most sense for your workflow.

Good luck and let us know how it goes.

I forgot to answer your first question.

"Would I need to put each script in the respective field under trigger after update?"

I'm not sure what you mean by "each script".

If you have multiple scripts that do different things, it would all depend on when you need them to happen. You can put them at the field level or you can put them at the table level.

Hardy

I was just answering your question - ie Can you automate it rather than have it triggered by pressing a button. Which you can... by using the " if this fields data has changed can it do the copy record info etc"

However - I totally agree with FRED let him show you a walk through path first!. He is giving you really good advice.

What you will learn is there are many ways that you can achieve the same result for a given set circumstances.

are you putting the code we already worked on between the if and end?

You ask if you change 'Received by' to 1,2 or 3 will trigger the script. I'm guessing you have tested out each true scenario and a false (when 'Received by' = 4, or whatever a false is) and found that it worked to your satisfaction.

The next step is to put the code into the Trigger after Update of 'Receive by' and test it again. Change 'Received by' to a true and a false case and make sure it does what it is supposed to do.