Hi community,
Hope I'm in the right place - I have troubles figuring out how to set up multiple items in a 1:N relationship thru Power Automate.
Scenario: I have tasks. Each task can have a predecessor from the same entity "Tasks". So, I have a 1:N self-relationship in the entity with enabled "Hierarchy". This way I can have 1 task that is predecessor to another task. Value is stored in the relationship column tk_predecessor.
Now, I'm successfully setting up 1 task to have 1 predecessor with Power Automate. I just use /tk_tasks(TASK GUID) in the lookup reference field and all is ok.
Question is - if I have more than 1 tasks that need to be in the predecessor field, how can I set this using Power Automate?
Essentially I'm trying to build an automation that can properly setup hierarchy. Just to illustrate it - imagine we have 3 tasks - task 01, task 02, task 03. I want to indicate that task 03 has task 02 and task 01 as predecessors. Task 02 has task 01 as predecessor.
Is this the correct approach to tackle this or I need a different table setup? (maybe a separate table to store the relationships among items?)
Michael E. Gernaey
497
Super User 2025 Season 1
David_MA
436
Super User 2025 Season 1
Riyaz_riz11
244
Super User 2025 Season 1