Share
ReportHi members,
I had this query. So earlier, as a part of development of power automate, I have been creating new connection references for every newly created solution. So you can say that every solution has it's own set of connection references.
Recently I got to know of a new best practice where, we store all the connection references in a single solution as standard connection reference. Instead of creating a new connection reference, what we can do is import that standard connection reference in the solution needed. Please let me know your thoughts if you are doing so.
Also the primary concern in later approach is that it creates a single point of failure (SPOF). If a single connection reference breaks down, all the solutions deployed will break down.
Also an additional query how do you go about managing environment variable is the similarly creating a single solution for all environment variables and importing them?
Thanks.
I had this query. So earlier, as a part of development of power automate, I have been creating new connection references for every newly created solution. So you can say that every solution has it's own set of connection references.
Recently I got to know of a new best practice where, we store all the connection references in a single solution as standard connection reference. Instead of creating a new connection reference, what we can do is import that standard connection reference in the solution needed. Please let me know your thoughts if you are doing so.
Also the primary concern in later approach is that it creates a single point of failure (SPOF). If a single connection reference breaks down, all the solutions deployed will break down.
Also an additional query how do you go about managing environment variable is the similarly creating a single solution for all environment variables and importing them?
Thanks.
Categories:
I have the same question (0)
All responses (
Answers (
618
