In this video, we will use Power Automate to build an approval flow in Microsoft Dataverse for Teams.

We will extend our scenario around the Help desk solution built in our Part 1 Video which covers building Power Apps for Teams using Dataverse for Teams.

https://powerapps.microsoft.com/en-us/blog/reshape-the-future-of-work-with-microsoft-dataverse-for-teams-now-generally-available/

Microsoft Dataverse for Teams delivers a built-in low code data platform for Microsoft Teams, and provides relational data storage, rich data types, enterprise grade governance, and one-click solution deployment.
Ignite 2020 Announcement – https://powerapps.microsoft.com/en-us/blog/now-in-preview-customize-teams-with-built-in-power-platform-capabilities/

Learn Power Automate Approvals

Learn Power Automate Expressions

#PowerAutomate #MicrosoftDataverse #MicrosoftDataverseforTeams #ProjectOakdale #MicrosoftTeams

17 Comments
  1. Viipiin 12 months ago

    Informative 👍

  2. Sundra Pillay 12 months ago

    Thanks

  3. Marc Vanderstraeten 12 months ago

    Very fast and comprehensive, so I need to digest… but once again super helpfull!

  4. Aroh Shukla 12 months ago

    and you made this video so simple and crystal clear for us. Your teaching style is exceptional. Eagerly waiting for more excellent Project Oakdale videos'!!

  5. Desert Feather 12 months ago

    Thank you, Reza! By far the best video on this topic!

  6. Gustavo Monne 12 months ago

    Hi Reza, Great video as always. Quick question: How did you add the Approval Status choice column into the Tickets table?

  7. Babajide Bantale 12 months ago

    Thanks Reza. Good explanation. Can we connect the datasource to system entities on CDS like (accounts, leads, contacts)

  8. Jayaprakash Tatagari 12 months ago

    Nice topic. Thanks for sharing.

  9. xMiSTERMAYHEMx 12 months ago

    thanks again for all the content!

  10. Nigel Price 11 months ago

    @ProjectOakdale #ProjectOakdale unable to create new flows within PowerApps in ProjectOakdale – No publisher is found, assembly must be registered in isolation. Code: 0x80040256 InnerError: '

  11. Boutros Zalloua 11 months ago

    So just to confirm all you need from a licencing perspective to build this flow is a Microsoft 365 licence? And this is because in project oakdale, the CDS connector is considered to be standard connector? Do you see this changing in the future?

  12. Ketan Gandhi 11 months ago

    Thank you for sharing. Excellent presentation skills. Crystal clear and simple.

  13. Brandon Casey 11 months ago

    Great video! I am a bit frustrated that I cannot click "see all" until I have created an app. Even if all I want to do is make a table … kind of frustrating. Is there another way to get to that interface before making an app first?

  14. Ashish Jaiswal 10 months ago

    Hi Reza, Amazing videos. I don't have any knowledge of coding but I'm loving this.

    Request, please share a video link where you explain how to customize that gallery experience.

  15. Thijs St Martin 9 months ago

    Hi Reza, great video!
    I created the approval flow yesterday in Teams, but I still get the same error message (429 Cds Instance Provisioning Incomplete).
    As already more than 12 hours have passed, I wondered if there is any way I can fix this?
    Thank you

  16. ghui 8 months ago

    why do I see this "visual editor" in Power Apps in Teams but not in the regular Power Apps UI. Or is it hidden somewhere?

  17. Prasad Joshi 7 months ago

    I built my first Power Automate in Dataverse for Teams with an approval action and it was not working. I came here to check what was going wrong. The tip for Approval solution provisioning time really helped. Thanks for sharing

Leave a reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

©2021 TDG - We Are Back Baby!

CONTACT US

We're not around right now. But you can send us an email and we'll get back to you, asap.

Sending
or

Log in with your credentials

Forgot your details?