Hi Community! I am just looking for the ability to either update a value on the Parent or Child when an quick action is execute from the child tab. When I use a run for child action in a quick action, I loose context of the parent record. This is a many to many N:N relationship, hence being so difficult to achieve my end result.
I have created a temp 1:1 relationship, If I can find a way to set this relationship via executing a quick action on the child tab of the parent record, this would be great!!!
I had a quick play and I do like a challenge, but not sure how to approach this one.
Thinking this may be possible if unlinked via a QA
Ideally the FusionLink table would be accessible within HEAT but unfortunately that doesn't appear to be the case.
I'll try and have another look if I get a chance this week but I am doubtful.
Hi DTurner, Yes, that was my train of thought also.
Since my relationship needs to be many to many, I would create a second 1:1 relationship strictly to be used for this process.
You initiate the process by pressing a 'Button' on the child tab to update a field to trigger a workflow or initiate a quick action.
Action 1 would be to search and link, and if I could JUST link the parent and highlighted child (without user input), then I would have both recId's I need (for another process I have not even mentioned yet) on the a single record (either the parent or child, what ever foreign key I set up on the relationship).
Come to think of it, it doesn't even need to be a relationship, just get the child recid that is highlighted and moved into a field at the parent record. \
In HEAT's predecessor product Frontrange ITSM, when you built a quick action that had the action 'Run for Child' you still had the parent record in context to reference data from... wish the new HEAT had this same functionality (Hint Hint)
I have it to where it saves the all the child RecIds on Link/Unlink but saves the previous value to another field.
So on Link a field could record IDs A, B, C, D.
B & C are unlinked.
The main field will now be A, D and another field will be populated with A, B, C, D.
I just don't know how to go about iterating through the values and saving any values that don't match :/
Might be going about this the wrong way - I will keep testing
Hi, did you manage to resolve this? I have a similar problem. I want to copy the denial reason to a field on the service req when an approval vote is denied.
Do these articles help with your use case?
Unfortunately not. The problem is that these methods pull the field from all of the record's grandchildren. What I need is to use the field from just one of them. I guess this means that the update needs to be triggered from that particular grandchild, but all those methods rely on using ForEachChild from the parent.