Public Profile
  • Make make.powerapps.com respect theme defined for environment

    In Microsoft Dataverse it is possible to specify a theme to use for the organization/environment. This is nice when a company brand can be implemented with color scheme and logo etc. Another extremely common use of the themes is to be able to quickly distinguish between Prod/Test/Dev/etc environments in the same tenant, helping you not to make customizations in production, and other unwanted mistakes. Since the move from the classic Solution Explorer to the Maker Experience, these themes are not reflected in any way. Please bring themes back to the customizers! 😊
  • Flag to lock production instance from customization

    Managed solutions in production is a great thing. Being able to mark solution components as uncustomizable is another great thing. But those concepts are not enough, there is always some way for admin users to mess with the system. We need a flag that can be set on production instances of Microsoft Dataverse to lock it down completely from customizations. Environment Variable Values and anything personal (views, flows, apps etc) are probably the only "customizations" that should be possible to touch. Many bad things and headaches and consultant hours have come from unmanaged messing with production environments.
  • Set ALL solution components uncustomizable

    The "Managed Properties" flags on solution components are a great way of preventing customizers in downstream environments or ISV customer environments from making customizations on top of what you are delivering in your managed solution. These flags are however by default set to "Customizable", meaning there is no lock. These flags must be set manually, component by component. In an ISV scenario, or even when you have core functionality that "shouldn't be messed with" in a custom implementation, it would be great to be able to specify on solution level that everything in this solution should be flagged as "Not customizable". We could always create another XrmToolBox tool looping through all components and setting/clearing that flag - but this would still not give the proper solution level indication of the customizable properties of the solution.