You’re offline. This is a read only version of the page.
Hi Everyone,
I need your input on an automated process I’m developing for the HR Clearance function.
Here’s a brief overview of the workflow:
Employees/Trainees submit their Clearance Form through Microsoft Forms.
The request is routed to the respective Head/Manager for approval via Microsoft Teams.
Upon approval, notification emails are automatically sent to the relevant departments.
If the request is rejected, an email notification is sent to both the employee and HR.
Currently, I’ve configured the form submissions to populate a Central List, and I’m using a Switch condition to handle three different locations. For testing purposes, I’ve implemented the Karachi branch logic first, which is functioning as expected — approvals, rejections, and list updates are all working properly, and duplicate records are being avoided.
The issue arises with the Central List:
Initially, when I used the Get Items action for the Central List (similar to how it’s used for Karachi), it resulted in duplicate entries being created.
To address this, I tried using the Delete Item action within an Apply to Each loop. However, this approach ended up deleting the record entirely — so neither the old nor the new record remained in the Central List.
My objective is to ensure that while each location maintains its individual list, the Central List is updated simultaneously and accurately — without creating duplicates or deleting records unintentionally.
I would appreciate any guidance or suggestions on how to achieve this.
Share
Report
All responses (
Answers (
699
