Using environment variables in a flow’s Excel action
I had a scenario where a flow with an Excel connection had to be usable in different tenants. On top of this, ALM for the flow had to be based on managed solutions. That naturally means there’s no touching and editing the flow after it’s been imported. From the platform’s perspective, environment variables are a means of defining values that differ between environments and tenants. In this…
Continue Reading Antti Pajunen’s Article on their blog
Using environment variables in a flow’s Excel action
I had a scenario where a flow with an Excel connection had to be usable in different tenants. On top of this, ALM for the flow had to be based on managed solutions. That naturally means there’s no touching and editing the flow after it’s been imported.
Blog Syndicated with Antti Pajunen’s Permission
More About This Author
Array
Dyn365CE2023.02.10Using environment variables in a flow’s Excel action- Dyn365CE2023.01.22Dynamics 365 Project Operations: Approving time entries using the Project Approver Admin role
- Dyn365CE2022.12.27Time-zone agnostic price defaulting in Project Operations
- Dyn365CE2022.12.05External scheduling in Project Operations
