No more exporting Environment Variable Values
Next month, the default experience will no longer export environment variable values in your solution.
This makes it easier to follow best practices and avoid inadvertent mistakes.
A new “Export value” toggle within the environment variable settings will allow you to opt-in to exporting the value, if needed.
I never understood why a solution export would also export the Environment Variable values, but glad it is going to be solved.
Power Platform Advisor
Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.
Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).
Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.
Services:
– Strategy and tactics advise
– Automating and integrating
A daily newsletter on automation and eliminating friction
I see your comment. And I see AI fingerprints all over it. You know the ones where you think: Bro... did you even read my post? 😅 I get it. We want engagement. We want the algorithm to give us more eyeballs. But fake engagement is still fake. Here’s what happens when...
Abstract the abstraction 🤯. .NET devs, we love our patterns... maybe too much. For a simple CRUD app, I've seen: Repositories – because obviously we can't query directly, that's too mainstream UnitOfWork – like transactions, but now with extra ceremony Services –...
Just blogged 📢: Building a ServiceClient Factory for Multi-Tenant Dynamics 365 / Dataverse Apps Struggling with multi-tenant Dynamics 365/Dataverse apps in Azure? Creating a ServiceClient factory that makes managing connections easier! 😎...