Hello,
That is because the case is not related to the incident in that regard, but instead is dependent upon the work order...which is subsequently related to an incident. So it's a child's dependency versus the parent (case) dependency on that incident. A bit of inception going on.
If the customer truly wants that, then what happens if you have multiple work orders and/or tasks that have dependency on an incident, the case can't fit more than one?
Anyways, I would recommend reviewing the customer's request again, think it over, think about scalability and the purpose behind that field and advising as to how you think.
If you MUST do this, then you can create a business rule on the work order table that if condition is that it's associated to a case and now has an incident associated, then echo the incident to the work order's case incident related record field (say that 5 times fast). So it "can" be done, but "should" it?
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
