Log edits without showing username/timestamp

Can you have the Action update a flag on the Shot ID to indicate that the Job ID has been logged.

Then have a condition on the Action to fire the Job UD log not to fire if it�s akready been fired once.

Note that an action can edit the record that triggered the Action. Ie the shot id table.

The trick is to create a Report link field that matches the record ID on the left side with same app same table /field [RecordID] on the right.

This is something I'm still struggling to understand.

So are you suggesting doing something like adding a checkbox field as a flag to the ShotID to indicate that it has been recorded to the Reshoot table already? And then use that to make sure that any subsequent edit of the ShotID is handled differently than the first?

Note that an action can edit the record that triggered the Action. Ie the shot id table.

I'm interested in this but I don't see how I can edit a record within the same table using an Action.

James, 

I was off cycling, so just catching up now with the Forum.  You can set up an Action to edit the record that triggered the action, by making a Report Link field. 

On the left side select Record ID# as the matching field and then on the right side navigate back to the app and then the same table and same Record ID# field.

Once you have created that Report link field it will be offered up when building the Action 

Hi,

I see now. I didn't know I could create a report link between the same field in the same table.

I've created a report link in Shots to link the Record ID with itself which now lets me use that link to modify a field in Shots called Reshoot, to which I write YES (indicating that the record is flagged as reshot).

I still can't get this to work though. I need the Action to add two new records the first time the Shot is modified - one record for the new entry and one record for the old entry. Then, for any subsequent modifications, only record the old record.

The problem I'm having is that in an Action I can't specify criteria BEFORE a record is modified, only after. So I can't say "if a Shot already has YES in the Reshoot field, do not fire the Action".

I can do this with Automation, but I can't add old records after modification using Automation. I can only add new records. I can't find a good balance between using an Action simultaneously with an Automation.

I'm only understanding about 75% of your setup so I'm offering suggestions that may give you ideas.

If you have an Action fire which updates a field [Reshoot] to yes,  if you change it from yes to yes, then that is not a change.  So if you have a 2nd Action setup to fire only when that Reshoot field changes, then it would not fire on the subsequent changes.  Does that help? 

Hi,

I know, sorry this is getting quite complicated. I really do appreciate your help so far, I feel like I'm getting closer to the solution.

This is the process I want to try and achieve:

1. When a ShotID has the JobID modified and the Reshoot field IS NOT set to YES, create two new records in the Reshoot table - one with the old JobID and one with the new JobID.

2. Write YES to the Reshoot field of the ShotID (using the Report Link for the RecordID#).

3. When a ShotID has the JobID modified and this time the Reshoot field IS set to YES, only create a new record of the new ShotID in the Reshoot table.

So, first time the JobID gets modified add two records, every other time only add one record.

I'm still getting the problem where it is adding the old and new JobID records every time the JobID is modified.

I think that you will need to use an Automation instead of an Action.  it has more flexibility in controlling when to fire and also it can then do many steps once the conditions have been met.

I feel so stupid but I suddenly had the most amazing thought! Instead of trying to handle when and how records are recorded to the Reshoot table, why not just set the JobID field in the Reshoot table to be unique. That way when the Action tries to record two new records it will only record the new one and not the old one, which already exists.

It works. I can't believe it took me 2 weeks to figure that out.