Building annual leave request flow

[harryhuckerby]

Hi, I'm in the midde of building an annual leave request flow. Currently it works fine having followed some useful suggestions and videos. However, I now want to make it so that once the request has been approved, an event is created and added to a sharepoint calendar for everyone to see. I'm wondering if this is at all possible and if someone can explain it to me please?

[annetoal]

Have a look at the action called Create a group event (V2) and see if that's useful to you. Post your code to give an idea of your progress.

Anne

[harryhuckerby]

Hi, 

I have been able to successfully build my flow, but I did it in 2 separate parts. i now want to combine them but when i do so, my flow gets stuck (it doesn't fail but it gets stuck trying to work) when I test it at the when an Item is created in sharepoint.

If you could be of any assistance it would be great. Flow posted below

[annetoal]

Could you provide a little more detail about what is meant by "stuck?" Error messages, outputs of a test run, etc.

[harryhuckerby]

Hi, yes I can. Essentially it doesn't go past this stage but then doesn't come up with an error at all?

[annetoal]

Please show what's going on inside the When an item is created step.

[harryhuckerby]

[annetoal]

I'm sorry, I wasn't very clear. I need to see the output of that step when you do a test run. 

Question: isn't that a trigger? What's it doing down there in the Flow?

[harryhuckerby]

So essentially what is going on is:

Someone submits an annual leave form on forms. This then creates an item in lists so that there is a calendar view of all holiday. 

Then from that, an approval email is then sent.

However, now I've just explained it, does it not make the 'when a new item is created' part to be voided because i could make it so once a form is submitted, this then triggers the email approval?

[annetoal]

In my experience, and this may purely be a reflection of the degree of my experience, the trigger is the first step in the Flow. I never heard of putting a trigger down in the Flow. So yes, I would agree that the trigger does not belong there.

[harryhuckerby]

So every part works fine, thank you. However the last bit I need to fix is the approval part on teams. I tested it with one of my colleagues completing a submission. Their name and details come up but on the teams approval which is sent to the manager, it says it is coming from me? Would you know why that might be?

[annetoal · Accepted solution]

It comes from you because your account is the one whose credentials are attached to the Teams connector in Flow. You can use a different account, and their name would come up on the approval. In my own experience, I have used a service account which doesn't have anyone's name attached to it. Depending on the security policies at your company, you may have to coordinate with the owner of the service account. You make the service account co-owner of the Flow--or maybe you make the service account the primary owner. The service account owner logs in and changes the connectors' credentials to those of the service account. 

Once the service account has done that, you can change the credentials back and forth between your own and the other account as much as you like.

[annetoal]

If this helped, please mark it as a solution and give it a thumbs up.

Anne

[harryhuckerby]

Have done so, thank you for your help