Bring down record #

Depending on the design of your process, then you can remove that as a lookup field, and you can just populate the Related WO in Notes at creation based on the Related WO in Jobs. 

This is made simpler if you keep both fields in Notes, and run an action or automation that will set the WO Number inside of Notes based on the WO Number from Job when the Related Job value inside of Notes changes.

If you want to do it based on the change inside of Job, then you can set up an automation to set the WO Number inside of Notes, based on the Related Job being equal to the Key from the Job table.

Let me know if you have any more questions or issues.

------------------------------
John Crosland
------------------------------

Andrew,

Since your Notes table has two potential parents where one can be inherited from the other, you are going to have to do some gymnastics.   

The cleanest thing is to use Triggers from Juiced Tech.   www.juicedtech.com

They have a great Search function that lets you look through other tables, capture the Record ID# and then you can write it to your table giving you the complete relationship.

Another way to tackle this is with the Look Up fields from each potential Parent and then use a Formula Numeric Field to rationalize it:

[Work Order ID FN] 
if ( isnull([Related Work Order])=false, [Related Work Order], [Job- Related Work Order])

Make sure you clear the check box on the field [Related Work Order] "Treat blank values as "0" in calculations.  You need the reference field to be Null when it is empty and not a zero value.

Now you can use a Report Link field and have it Match to the [Work Order ID FN] 



------------------------------
Don Larson
Paasporter
Westlake OH
------------------------------