Bring down record #
I have three tables:
Work Orders
Jobs
Notes
I have the following relationships established between them: Work Orders < Jobs Work Orders < Notes Jobs < Notes The notes table is embedd...
Forum Discussion
John,
Thanks for the suggestion. I already had the Work Order record # coming down to the Job Table, but forgot to bring it down to the Notes Table from the Jobs table.
However, I now have two fields in my Notes table for basically the same thing: Work Order Record #. One via the relationship of Notes & Work Orders and the other via the relationship of Notes & Jobs.
That doesn't seem ideal to me .....
------------------------------
Andrew
[email protected]
------------------------------
Thanks for the suggestion. I already had the Work Order record # coming down to the Job Table, but forgot to bring it down to the Notes Table from the Jobs table.
However, I now have two fields in my Notes table for basically the same thing: Work Order Record #. One via the relationship of Notes & Work Orders and the other via the relationship of Notes & Jobs.
That doesn't seem ideal to me .....
------------------------------
Andrew
[email protected]
------------------------------
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
------------------------------
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
------------------------------
- John,
I like this idea, but am having some issues implementing it.
What I have so far for my automation is the following:
I am not getting the result I was hoping for.
Any thoughts?
------------------------------
Andrew
[email protected]
------------------------------- I think that I just fixed my issue.
I had to change the action part of it to capture the correct Note # (unique ID) rather than the Job-Work Order ID#. It seems to be working now!!
Thanks again for the suggestion.
------------------------------
Andrew
[email protected]
------------------------------ - Hi Andrew,
Glad that you're happy with the solution.
I noticed a couple of things. Your automation only runs when a record is added to the Notes Table. So, is it not possible for a user to add or change the linked job inside of an existing record? Also, in your current set up. You might be overwriting the user inputted WO Number linked to that Note (which might be different than the WO Number from the Job record). Unless your form has rules that says that you can't select a Job Number that isn't linked to the WO Number.
To allow for this operation to take place when the user changes the record, then also run the check on modfies a record as well.
To prevent overwriting data, then I would recommend checking the value of WO Number inside of the criteria (possibly create another automation that will run first)
Hope that helps some more,
John
------------------------------
John Crosland
Software Developer
Inglett & Stubbs
Mableton GA
------------------------------- John,
Thanks for the suggestions. The Job and WO numbers are the unique record numbers when a record is created. I just renamed them from "Record ID#" to "Job ID#" (alias of "Job#"), "Work Order ID# (alias of "WO#"), & "Note ID#" (alias of "Note#").
The user will not be inputting those numbers in any situation possible as they are generated at time of record creation.
As far as the automation only running when a record is added, yes, that is what I need it to be. Once the note has been input.
The only time that I might possible need to capture a modification to made to a Note, being re-assigned to a different job, is if the note was erroneously input for an incorrect job.
But in those cases, the user is not able to select which is the correct job, by design.
But your suggestions have given me some food for thought on how I might better the process, workflow, and automations.
Thanks a ton John!!
------------------------------
Andrew
[email protected]
------------------------------