Trigger validation rule in parent record
I have an issue with validation rules that I would appreciate some help with. I have two tables for timesheets ? one for header (date, employee, shift) and another for line item details ? job,...
Forum Discussion
Hi Alex
I tried that, but the value doesn't get passed back to the child record until after the child is saved - by which time it's too late.
I tried that, but the value doesn't get passed back to the child record until after the child is saved - by which time it's too late.
Ah. Okay.
Well, if that workflow's not malleable, you can engineer solutions from that point.
Instead of 'SAVE' on the child record, display 'CHECK HOURS'. Have 'CHECK HOURS' pass the hours value up and back down the chain, as well as invisibly dirty the record, and don't allow saving an un-dirtied record.
It's not a GOOD solution but it seems that without changes to workflow, there may not be good ones left. As Mark suggests below, social engineering is also always an option in circumstances like these.
Well, if that workflow's not malleable, you can engineer solutions from that point.
Instead of 'SAVE' on the child record, display 'CHECK HOURS'. Have 'CHECK HOURS' pass the hours value up and back down the chain, as well as invisibly dirty the record, and don't allow saving an un-dirtied record.
It's not a GOOD solution but it seems that without changes to workflow, there may not be good ones left. As Mark suggests below, social engineering is also always an option in circumstances like these.