![]() The default resolution of an unattended Power Automate Desktop flow is 1024 x 768. Believe it or not, developing on personal accounts can have an impact on how flows were/are licensed. During the rebuild of the flows, the implementation of service accounts played a crucial role for the foundational layer of the architecture (including the design of reusable components) as well as licensing. When members of the development team left the organisation, the flows that were associated to their accounts were lost when the developer profiles were deleted which resulted in the flows having to be rebuilt.Ī best practice for automation development is the use of service accounts to avoid the situation described above. The implementation in question was initially investigated by a different team who used their individual/personal accounts for the development of flows. This is by far the most important lesson learnt. Here’s a summarised list of lessons learnt and things I wish I knew before my ‘first’ enterprise level automation solution implementation with Power Automate flows. By sharing these lists, we better prepare the community of developers who may be facing similar challenges. There is a ‘first time’ for everything which comes with a list of lessons learnt. ![]() Any toolset comes with it’s own unique tricks and challenges. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |