Log edits without showing username/timestamp
Is there a way to use the Log Entry feature without it logging the user or time stamp? I have two fields, "Related Job" and "Job History" in a table. Any time the key field of the table is modified...
Forum Discussion
Yes, sorry. I got a little carried away. :)
I work in a fashion photo studio. We produce thousands of images a day. Our QB app tracks the movement of each of these images through a series of post production processes. Each image (or ShotID) is assigned a JobID to provide information about when and where the image was taken. Many ShotID's can have one JobID.
If an image is ever reshot, for example to update a garment, the ShotID remains the same (as the key field) and what happens in the app currently is that the JobID for the existing ShotID is replaced with the new one.
What I'd like to start doing is track how often an image gets reshot, because I suspect it is more than a couple of times. To do this, my idea was that if a ShotID has its JobID modified the JobID would get saved to a new field or maybe even a new table. The intention being that I would then be able to say, "this image has had 3 different JobID's and has therefore been shot 3 times".
I am close to this. I have created a new table call "Reshoot". If a ShotID has its JobID modified, an Action creates a new record in Reshoot of the ShotID and the old JobID before it was modified (by using "Copy the old value from JobID"). This works great for saving every old JobID because it will continue to create new records in Reshoot every time the JobID is modified.
However, there's one bit its not doing and I'm completely stuck on. In order to be able to say "this image has been shot 3 times" I need to know in the Reshoot table what the current ShotID's JobID is as well as the other 2 old JobID's. That's the part I need help with. I want these added as a separate record as well, but if I create an Action to do it, every time the JobID is modified it is creating new records with the new and old JobID.
I work in a fashion photo studio. We produce thousands of images a day. Our QB app tracks the movement of each of these images through a series of post production processes. Each image (or ShotID) is assigned a JobID to provide information about when and where the image was taken. Many ShotID's can have one JobID.
If an image is ever reshot, for example to update a garment, the ShotID remains the same (as the key field) and what happens in the app currently is that the JobID for the existing ShotID is replaced with the new one.
What I'd like to start doing is track how often an image gets reshot, because I suspect it is more than a couple of times. To do this, my idea was that if a ShotID has its JobID modified the JobID would get saved to a new field or maybe even a new table. The intention being that I would then be able to say, "this image has had 3 different JobID's and has therefore been shot 3 times".
I am close to this. I have created a new table call "Reshoot". If a ShotID has its JobID modified, an Action creates a new record in Reshoot of the ShotID and the old JobID before it was modified (by using "Copy the old value from JobID"). This works great for saving every old JobID because it will continue to create new records in Reshoot every time the JobID is modified.
However, there's one bit its not doing and I'm completely stuck on. In order to be able to say "this image has been shot 3 times" I need to know in the Reshoot table what the current ShotID's JobID is as well as the other 2 old JobID's. That's the part I need help with. I want these added as a separate record as well, but if I create an Action to do it, every time the JobID is modified it is creating new records with the new and old JobID.