The problem with a more technical naming convention for flows are the ones that can be triggered by users (in Dynamics 365). That's why we opted for more plain language descriptive names. By the way: the constant quick zooming in and out is really annoying (to my personal taste 🙂)
The Hindi is so pure that people will get confused. For example it is also translating "Solution" as Samadhan. There is no need to translate this as it is a part of power automate.
Thanks for the feedback! Interesting and glad people are trying the other languages as we put a lot of work into them. We'll work on the literal translations.
![Power Automate Beginner to Pro Tutorial [Full Course]](http://i.ytimg.com/vi/1p5kI7SYz4Q/mqdefault.jpg)
Really great video! Can't find the guide in the description though.
The problem with a more technical naming convention for flows are the ones that can be triggered by users (in Dynamics 365). That's why we opted for more plain language descriptive names.
By the way: the constant quick zooming in and out is really annoying (to my personal taste 🙂)
The Hindi is so pure that people will get confused. For example it is also translating "Solution" as Samadhan. There is no need to translate this as it is a part of power automate.
Thanks for the feedback! Interesting and glad people are trying the other languages as we put a lot of work into them. We'll work on the literal translations.
🎉🎉
Great content but all of the unnecessary video production elements are distracting.
Totally agree. I loved the content and HATED the editing. Not sure who the intended audience is...
Thank you both for the feedback! We're working with some new editors and we asked them to up our game. In the process, we went too far it seems :)