http://powerwiki.net/api.php?action=feedcontributions&feedformat=atom&user=Benedikt Power Wiki - User contributions [en] 2026-04-23T20:54:04Z User contributions MediaWiki 1.35.1 http://powerwiki.net/index.php?title=2023_Release_Wave_2&diff=6251 2023 Release Wave 2 2023-08-14T04:34:29Z <p>Benedikt: </p> <hr /> <div>== Official documentation ==<br /> === Release Wave Plans ===<br /> * [https://learn.microsoft.com/en-us/power-platform/release-plan/2023wave2/ Power Platform 2023 Release Wave 2 plan]<br /> * [https://learn.microsoft.com/en-us/dynamics365/release-plan/2023wave2/ Dynamics 365 &amp; more 2023 Release Wave 2 plan]<br /> * [https://learn.microsoft.com/en-us/dynamics365/release-plan/2023wave2/ Microsoft Cloud for Industry 2023 Release Wave 2 plan]<br /> <br /> === Blog posts ===<br /> *[https://cloudblogs.microsoft.com/dynamics365/bdm/2023/07/18/2023-release-wave-2-plans-for-microsoft-dynamics-365-and-power-platform-now-available/ 2023 release wave 2 plans for Dynamics 365 and Power Platform - Microsoft Dynamics 365 Blog]<br /> <br /> === Videos ===<br /> * [https://www.youtube.com/playlist?list=PLcakwueIHoT_2g8Kw6n4ujiKbdolXzZnY Release Wave 2 Highlights on YouTube]<br /> <br /> == Community Summaries ==<br /> === Podcasts ===<br /> * [https://powerplatformboost.buzzsprout.com/2147912/13178139 2023 Release Wave 2 - Power Platform Boost Podcast by Nick Doelman &amp; Ulrikke Akerbæk]<br /> * [https://crmrocks.com/2023/08/14/2023-release-wave-2-with-benedikt-bergmann/ 2023 2023 Release wave 2 with Benedikt Bergmann by Markus Erlandsson]<br /> <br /> === Videos ===<br /> * [https://www.youtube.com/watch?v=JXGjOObcNow Power Platform Wave 2 2023 Release: Top 10 Features You Need to Know! by Lisa Crosbie]<br /> * [https://www.youtube.com/watch?v=dH3TRerTEAw Dynamics 365 Wave 2 2023: Top 10 Features You Need to Know! by Lisa Crosbie]<br /> * [https://www.youtube.com/watch?v=kuJYmPk5RCI Power Platform 2023 Wave 2 Release Notes Highlights by David Yack (365.Training)]<br /> <br /> === Blog posts ===<br /> * [https://www.dancingwithcrm.com/top-things-from-2023-release-wave-2/ Top 7 things from Power Platform 2023 release wave 2 by Oleksandr Olashyn]<br /> * [https://michelcarlo.com/2023/07/22/my-top-power-platform-2023-release-wave-2-plan-features/ My top Power Platform 2023 release wave 2 plan features by Michel Mendes]<br /> * [https://www.bendenblanken.com/top-9-waves-to-catch-this-power-platform-release-wave/ Top 9 Waves to catch this Power Platform Release Wave by Ben den Blanken]<br /> * [https://benediktbergmann.eu/2023/07/18/release-2023-wave-2-summary/ Release 2023 Wave 2 Summary by Benedikt Bergmann]<br /> * [https://d365goddess.com/2023-wave-2-release-notes-d365-field-service/ 2023 Wave 2 Release Notes: D365 Field Service by Dian Taylor]<br /> * [https://d365goddess.com/2023-wave-2-release-notes-d365-customer-service/ 2023 Wave 2 Release Notes: D365 Customer Service by Dian Taylor]<br /> * [https://wilmeralcivar.com/power-platform-release-wave-2-2023/ Power Platform Release wave 2 2023 by Wilmer Alcivar]</div> Benedikt http://powerwiki.net/index.php?title=Community_Events&diff=6099 Community Events 2022-08-01T12:16:59Z <p>Benedikt: </p> <hr /> <div>This page contains a list of events brought to you by the community.<br /> <br /> === Event Websites ===<br /> {|<br /> ! Name<br /> ! Description<br /> |-<br /> | [https://nordicsummit.info/ Nordic Summit] || Visit the Event page for more information.<br /> |-<br /> | [https://events.powercommunity.com/ 365 Saturday Power Community] || Past and upcoming 365 Saturday events.<br /> |-<br /> | [https://powerchallenge.altitude365.com/ Scottish Summit] || Past and upcoming Scottish Summit events. Also have a look at the Power Wiki [[Scottish Summit]] page!<br /> |- <br /> | [https://dynamicscon.com/ DynamicsCon] || Microsoft Dynamics 365 &amp; Power Platform User Professionals.<br /> |- <br /> |[https://www.southcoastsummit.com/ South Coast Summit] || A Microsoft Cloud Technology Community Conference, focusing on the entire Microsoft stack.<br /> |-<br /> | [https://portal.collab365.com/collab365-globalcon5-2020/globalcon5-agenda/ GlobalCon] || Microsoft 365 Virtual Conference<br /> |-<br /> | [https://bizzsummit.es/en/ Bizz Summit ES] || Spanish in-person Business Application Summit.<br /> |-<br /> | [https://en.powerplatformfrenchsummit.com/ Power Platform French Summit] || French in-person Power Platform Summit.<br /> |-<br /> | [https://www.iberiansummit.com/index.html Iberian Technology Summit] || First summit of its kind across the border of Portugal and Spain.<br /> |}<br /> <br /> === See also ===<br /> <br /> * The [[Call for Speakers]] page if you would like to be a speaker.<br /> * The [[Microsoft Events]] page for information about events held by Microsoft. <br /> <br /> [[Category:Community]]</div> Benedikt http://powerwiki.net/index.php?title=Call_for_Speakers&diff=6098 Call for Speakers 2022-08-01T12:14:33Z <p>Benedikt: </p> <hr /> <div>This page contains a list of call for speakers for events brought to you by the community.<br /> <br /> {|<br /> ! Name<br /> ! Type<br /> ! Description<br /> ! Event date<br /> ! Deadline for submission<br /> |-<br /> | [https://sessionize.com/ppfs2022/ Power Platform French Summit] || Hybrid || The Francophone event of the year around Microsoft Power Platform bringing together the 3 Microsoft Clouds: Azure, Dynamics 365 and Microsoft 365 || 2022-11-17 and 2022-11-18 || 2022-10-09<br /> |-<br /> | [https://sessionize.com/iberian-technology-summit/ Iberian Technology Summit] || in-person || Iberian Technology Summit is the first of its kind with a clear goal to achieve. Cross the borders of peninsula and help to empower the community of professionals, workers and businesses to grow stronger together. A completely free-of-charge two-days event for a vast variety of interests offers an insight on how technology and optimisation can impact a business growth. || 2023-04-28 - 2023-04-30 || 2022-10-03<br /> |-<br /> |}<br /> <br /> <br /> [[Category:Community]]</div> Benedikt http://powerwiki.net/index.php?title=Call_for_Speakers&diff=6097 Call for Speakers 2022-08-01T12:14:12Z <p>Benedikt: </p> <hr /> <div>This page contains a list of call for speakers for events brought to you by the community.<br /> <br /> {|<br /> ! Name<br /> ! Type<br /> ! Description<br /> ! Event date<br /> ! Deadline for submission<br /> |-<br /> | [https://sessionize.com/ppfs2022/ Power Platform French Summit] || Hybrid || The Francophone event of the year around Microsoft Power Platform bringing together the 3 Microsoft Clouds: Azure, Dynamics 365 and Microsoft 365 || 2022-11-17 and 2022-11-18 || 2022-10-09<br /> |-<br /> | [https://sessionize.com/iberian-technology-summit/ Iberian Technology Summit] || in-person || Iberian Technology Summit is the first of its kind with a clear goal to achieve. Cross the borders of peninsula and help to empower the community of professionals, workers and businesses to grow stronger together.<br /> A completely free-of-charge two-days event for a vast variety of interests offers an insight on how technology and optimisation can impact a business growth. || 2023-04-28 - 2023-04-30 || 2022-10-03<br /> |-<br /> |}<br /> <br /> <br /> [[Category:Community]]</div> Benedikt http://powerwiki.net/index.php?title=Community_Events&diff=6096 Community Events 2022-08-01T12:06:49Z <p>Benedikt: </p> <hr /> <div>This page contains a list of events brought to you by the community.<br /> <br /> === Event Websites ===<br /> {|<br /> ! Name<br /> ! Description<br /> |-<br /> | [https://nordicsummit.info/ Nordic Summit] || Visit the Event page for more information.<br /> |-<br /> | [https://events.powercommunity.com/ 365 Saturday Power Community] || Past and upcoming 365 Saturday events.<br /> |-<br /> | [https://powerchallenge.altitude365.com/ Scottish Summit] || Past and upcoming Scottish Summit events. Also have a look at the Power Wiki [[Scottish Summit]] page!<br /> |- <br /> | [https://dynamicscon.com/ DynamicsCon] || Microsoft Dynamics 365 &amp; Power Platform User Professionals.<br /> |- <br /> |[https://www.southcoastsummit.com/ South Coast Summit] || A Microsoft Cloud Technology Community Conference, focusing on the entire Microsoft stack.<br /> |-<br /> | [https://portal.collab365.com/collab365-globalcon5-2020/globalcon5-agenda/ GlobalCon] || Microsoft 365 Virtual Conference<br /> |-<br /> | [https://bizzsummit.es/en/ Bizz Summit ES] || Spanish in-person Business Application Summit.<br /> |-<br /> | [https://en.powerplatformfrenchsummit.com/ Power Platform French Summit] || French in-person Power Platform Summit.<br /> |}<br /> <br /> === See also ===<br /> <br /> * The [[Call for Speakers]] page if you would like to be a speaker.<br /> * The [[Microsoft Events]] page for information about events held by Microsoft. <br /> <br /> [[Category:Community]]</div> Benedikt http://powerwiki.net/index.php?title=Community_Events&diff=6095 Community Events 2022-08-01T12:04:57Z <p>Benedikt: </p> <hr /> <div>This page contains a list of events brought to you by the community.<br /> <br /> === Event Websites ===<br /> {|<br /> ! Name<br /> ! Description<br /> |-<br /> | [https://nordicsummit.info/ Nordic Summit] || Visit the Event page for more information.<br /> |-<br /> | [https://events.powercommunity.com/ 365 Saturday Power Community] || Past and upcoming 365 Saturday events.<br /> |-<br /> | [https://powerchallenge.altitude365.com/ Scottish Summit] || Past and upcoming Scottish Summit events. Also have a look at the Power Wiki [[Scottish Summit]] page!<br /> |- <br /> | [https://dynamicscon.com/ DynamicsCon] || Microsoft Dynamics 365 &amp; Power Platform User Professionals.<br /> |- <br /> |[https://www.southcoastsummit.com/ South Coast Summit] || A Microsoft Cloud Technology Community Conference, focusing on the entire Microsoft stack.<br /> |-<br /> | [https://portal.collab365.com/collab365-globalcon5-2020/globalcon5-agenda/ GlobalCon5] || Microsoft 365 Virtual Conference 2021<br /> |-<br /> | [https://bizzsummit.es/en/ Bizz Summit ES] || Spanish Business Application Summit.<br /> |}<br /> <br /> === See also ===<br /> <br /> * The [[Call for Speakers]] page if you would like to be a speaker.<br /> * The [[Microsoft Events]] page for information about events held by Microsoft. <br /> <br /> [[Category:Community]]</div> Benedikt http://powerwiki.net/index.php?title=Community_Events&diff=6094 Community Events 2022-08-01T12:03:52Z <p>Benedikt: </p> <hr /> <div>This page contains a list of events brought to you by the community.<br /> <br /> === Event Websites ===<br /> {|<br /> ! Name<br /> ! Description<br /> |-<br /> | [https://nordicsummit.info/ Nordic Summit] || Visit the Event page for more information.<br /> |-<br /> | [https://events.powercommunity.com/ 365 Saturday Power Community] || Past and upcoming 365 Saturday events.<br /> |-<br /> | [https://powerchallenge.altitude365.com/ Scottish Summit] || Past and upcoming Scottish Summit events. Also have a look at the Power Wiki [[Scottish Summit]] page!<br /> |- <br /> | [https://dynamicscon.com/ DynamicsCon] || Microsoft Dynamics 365 &amp; Power Platform User Professionals.<br /> |- <br /> |[https://www.southcoastsummit.com/ South Coast Summit] || A Microsoft Cloud Technology Community Conference, focusing on the entire Microsoft stack.<br /> |-<br /> | [https://portal.collab365.com/collab365-globalcon5-2020/globalcon5-agenda/ GlobalCon5] || Microsoft 365 Virtual Conference 2021<br /> |<br /> |-<br /> | [https://bizzsummit.es/en/ Bizz Summit ES] || Spanish Business Application Summit.<br /> |<br /> }<br /> <br /> === See also ===<br /> <br /> * The [[Call for Speakers]] page if you would like to be a speaker.<br /> * The [[Microsoft Events]] page for information about events held by Microsoft. <br /> <br /> [[Category:Community]]</div> Benedikt http://powerwiki.net/index.php?title=Application_Lifecycle_Management&diff=5715 Application Lifecycle Management 2021-12-22T22:04:50Z <p>Benedikt: </p> <hr /> <div>Application lifecycle management is the lifecycle management of applications and includes governance, development and maintenance. For everyone working with [[Power Platform]] ALM includes setting up [[environment]] strategies, managing [[Solutions]], automating deployment e.g. with [[pipelines]] in DevOps etc. Related to this is the [[Center of Excellence]] (CoE) Starter Kit which is a set of templates provided by Microsoft which you can use in order to set up your own Center of Excellence. <br /> <br /> == Basic Process ==<br /> A basic ALM process could contain the following 3 pipelines, for more information, also see the page [[Pipelines]].<br /> <br /> === Create Export from DEV ===<br /> This build pipeline would:<br /> * Export the solution from DEV<br /> * Do some Quality Gates (for example run solution Checker)<br /> * Unpack the solution<br /> * Check it into source control<br /> <br /> It could also handle stuff like:<br /> * Set correct version<br /> * Deploy code components (JS, Plugins, PCFs, ...) before exporting<br /> * ... <br /> <br /> === Build Managed Solution ===<br /> The second build pipeline would create a managed solution from the repository and publish it as an artefact.<br /> <br /> {{<br /> PWBoxInfo<br /> | title = Run in one<br /> | text = The first two pipelines could also be run in one. <br /> }}<br /> {{<br /> PWBoxWarning<br /> | title = JIT-Build Environment<br /> | text = There might be problems with creating a JIT-Build Environment on the fly. See the post in Community Resources which contains more information on that.<br /> }}<br /> <br /> === Deploy to Downstream environments === <br /> The last part of a basic process would be a Release Pipeline to deploy the created artefact to the downstream environments.<br /> <br /> == Related content ==<br /> === Power Wiki ===<br /> * [[How to set Environment Variables value]] <br /> * [[Environment Variables]]<br /> <br /> === Microsoft Resources === <br /> * [https://docs.microsoft.com/power-platform/alm/?WT.mc_id=DX-MVP-5003780 Application lifecycle management (ALM) with Microsoft Power Platform]<br /> * [https://powerapps.microsoft.com/en-us/blog/key-alm-updates/ ALM Key Updates - March 2021]<br /> <br /> === Community Resources ===<br /> * [https://github.com/rpothin/PowerPlatform-ALM-Learning-Resources PowerPlatform-ALM-Learning-Resources] GitHub repository gathering ALM resources<br /> * [https://github.com/Power-Platform-DevOps/Power-Platform-ALM-Starter-Kit Power Platform ALM Starter Kit]<br /> * [https://benediktbergmann.eu/2020/02/10/cds-basic-alm-process/ CDS - Basic ALM Process] by Benedikt Bergmann<br /> * [https://benediktbergmann.eu/2020/06/14/quality-gates-for-check-ins/ Quality Gate for check-ins] by Benedikt Bergmann<br /> <br /> === External Resources ===<br /> * [https://en.wikipedia.org/wiki/Application_lifecycle_management ALM on Wikipedia]<br /> <br /> [[Category: ALM]]</div> Benedikt http://powerwiki.net/index.php?title=How_to_work_with_Solution_Patches&diff=5714 How to work with Solution Patches 2021-12-22T22:03:48Z <p>Benedikt: </p> <hr /> <div>Sometimes you might not need a full deployment of the whole solution, that's where patches come in. <br /> <br /> == What is a patch ==<br /> When you create a patch from a solution the system will create an empty solution tied to the base solution. You can then include only the parts you would need rather than having the whole solution.<br /> This will increase deployment speed but brings other downsides (which will be explained later).<br /> <br /> As mentioned a patch is tied to a base solution, to be more specific even to a certain version of it.<br /> This means the source environment and the target environment need to have the same version of the base solution installed to be able to install a patch.<br /> <br /> Whenever you create or install a new version of the base solution all patches will be rolled up into the base solution.<br /> <br /> == Use case ==<br /> Imagine you have your solution live in production, started development of new features already and a bug is detected.<br /> You can't do a full deployment since you would deploy changes that aren't tested or approved yet. In this case, you could create a patch, only containing your hotfix, and deploy that.<br /> <br /> Another problem could arise though. Usually, the version of your solution has been changed already when you come to that point, which makes the created patch unusable (because of the mentioned version constraints). A solution to that would be a hotfix environment that contains the same version of your solution as production. Either you have this environment always running or create it when needed from an unmanaged solution which should be stored in your repo (see [[ALM]]).<br /> <br /> == ALM ==<br /> As mentioned there are restrictions when it comes to the solution version. Another problem with ALM and patches is that every patch has a unique name which makes it hard to automate the export of it.<br /> Those reasons make it nearly impossible to handle patches in an automated ALM process. Patches are therefore mostly usable when handled manually in certain limited use cases.<br /> <br /> == Related Content ==<br /> === Microsoft Resources ===<br /> * [https://docs.microsoft.com/en-us/power-platform/alm/create-patches-simplify-solution-updates Create patches to simplify solution updates]<br /> <br /> === Community Resources ===<br /> * [https://benediktbergmann.eu/2021/02/28/how-to-handle-hotfixes-in-dataverse/ How to handle hotfixes in Dataverse] by Benedikt Bergmann</div> Benedikt http://powerwiki.net/index.php?title=How_to_work_with_Solution_Patches&diff=5713 How to work with Solution Patches 2021-12-22T22:03:25Z <p>Benedikt: </p> <hr /> <div>Sometimes you might not need a full deployment of the whole solution, that's where patches come in. <br /> <br /> == What is a patch ==<br /> When you create a patch from a solution the system will create an empty solution tied to the base solution. You can then include only the parts you would need rather than having the whole solution.<br /> This will increase deployment speed but brings other downsides (which will be explained later).<br /> <br /> As mentioned a patch is tied to a base solution, to be more specific even to a certain version of it.<br /> This means the source environment and the target environment need to have the same version of the base solution installed to be able to install a patch.<br /> <br /> Whenever you create or install a new version of the base solution all patches will be rolled up into the base solution.<br /> <br /> == Use case ==<br /> Imagine you have your solution live in production, started development of new features already and a bug is detected.<br /> You can't do a full deployment since you would deploy changes that aren't tested or approved yet. In this case, you could create a patch, only containing your hotfix, and deploy that.<br /> <br /> Another problem could arise though. Usually, the version of your solution has been changed already when you come to that point, which makes the created patch unusable (because of the mentioned version constraints). A solution to that would be a hotfix environment that contains the same version of your solution as production. Either you have this environment always running or create it when needed from an unmanaged solution which should be stored in your repo (see {{ALM}}).<br /> <br /> == ALM ==<br /> As mentioned there are restrictions when it comes to the solution version. Another problem with ALM and patches is that every patch has a unique name which makes it hard to automate the export of it.<br /> Those reasons make it nearly impossible to handle patches in an automated ALM process. Patches are therefore mostly usable when handled manually in certain limited use cases.<br /> <br /> == Related Content ==<br /> === Microsoft Resources ===<br /> * [https://docs.microsoft.com/en-us/power-platform/alm/create-patches-simplify-solution-updates Create patches to simplify solution updates]<br /> <br /> === Community Resources ===<br /> * [https://benediktbergmann.eu/2021/02/28/how-to-handle-hotfixes-in-dataverse/ How to handle hotfixes in Dataverse] by Benedikt Bergmann</div> Benedikt http://powerwiki.net/index.php?title=How_to_document_your_solutions&diff=5706 How to document your solutions 2021-12-21T12:29:25Z <p>Benedikt: </p> <hr /> <div>This page gathers information about what documentation is needed for your Power Platform solutions. <br /> <br /> == General ==<br /> So you have created a Power Platform solution and users are now using it in a production environment. In order to be able to maintain the solution over time it is important to establish and maintain documentation as well. <br /> <br /> Examples of what documentation that is useful to have:<br /> <br /> * Best Practice and naming conventions - Best to figure this out before you start with your project in order to establish a common way of working.<br /> * Entity Relationship Diagram (ERD) visualizing the essential OOTB Tables that make up your solution as well as all custom tables and the relationships in between. <br /> * Environments that are used and settings specific for each environment (that are not deployed through solutions, e.g. search settings or configuration data).<br /> * ALM and deploy procedure - info about pipelines, the setup and who is responsible for deploys. <br /> * Solution Components - Description of Tables, relationships in between, Business Rules, Business Process Flows (BPF), Cloud flows, Plugins etc. <br /> * For Canvas Apps - Data Sources<br /> * Integrations - What integrations there are, diagram illustrating integration flows, integration techniques, mappings. <br /> * Functional description<br /> <br /> If Azure DevOps is used, a Project Wiki can be used to store information about environments, settings and pipelines. If Microsoft Teams is used, a OneNote can be used as wiki. <br /> <br /> == Tools ==<br /> There are some tools to be used as part of creating documentation for your solutions. <br /> <br /> * [https://www.xrmtoolbox.com/plugins/LinkeD365.ERDVisioBuilder/ XTB - ERD Visio Builder]<br /> * [https://www.xrmtoolbox.com/plugins/LinkeD365.FlowToVisio/ XTB - Flow to Visio]<br /> * [https://www.xrmtoolbox.com/plugins/ExportSecurityRole/ XTB - Role Documenter]<br /> * [https://www.xrmtoolbox.com/plugins/MsCrmTools.MetadataDocumentGenerator/ XTB - Metadata Document Generator]<br /> * [https://www.xrmtoolbox.com/plugins/LinkeD365.BotToVisio/ XTB - PVA to Visio Builder] (In progress)<br /> * [https://github.com/modery/PowerDocu Power Docu] to document Flows</div> Benedikt http://powerwiki.net/index.php?title=Environment_Variables&diff=5669 Environment Variables 2021-12-19T14:35:37Z <p>Benedikt: </p> <hr /> <div>Environment Variables (EnvVars) can be used to retrieve a value based on the current environment.<br /> <br /> == General ==<br /> Environment Variables can return a value based on the environment the requesting application is in.<br /> EnvVars are solution aware and can therefore be &quot;transported&quot; with a usual Deployment (see [[ALM]]]).<br /> <br /> {{<br /> PWBoxInfo<br /> | title = Be aware<br /> | text = Local values should not be included in a solution. Otherwise, it will be impossible to override the value in a downstream environment.<br /> }}<br /> <br /> === Structure ===<br /> EnvVars are built with two tables:<br /> * Environment Variable Definition<br /> * Environment Variable Value<br /> <br /> ==== Environment Variable Definition ====<br /> As the name suggests posts in this table contain the definition of an environment variable. This contains<br /> * DiplayName<br /> * SchemaName<br /> * Description<br /> * Data Type<br /> * Default Value<br /> <br /> ==== Environment Variable Value ====<br /> Also called &quot;Local Value&quot;. A post in this table is always related to some definition and should never be included in a solution.<br /> It overrides the default value of a definition and is the value of the current environment.<br /> <br /> === Use case ===<br /> Use cases could for example be<br /> * URL's<br /> * Canvas App Ids<br /> * Record Ids<br /> * Switches<br /> * Connections<br /> * Other Configuration<br /> <br /> === How to create ===<br /> Environment Variables are, as mentioned, Solution components and should be created from a solution as well.<br /> First, the definition has to be created. After you save the first time you can add a local value. This local value should then be removed from the solution (via the ... besides it).<br /> <br /> === How to use ===<br /> Power Automate has a native integration with EnvVars. All the available EnvVars will be shown in the list of dynamic values.<br /> {{<br /> PWBoxInfo<br /> | title = Be aware<br /> | text = If you use this approach EnvVars are cached. When you change the value you have to turn all the flows off and on to get the new value.<br /> }}<br /> <br /> If you would like to use EnvVars in any other way (Plugins, JS, ...) you have to handle them yourself. This means getting the rows and deciding whether to use the default or local value.<br /> <br /> == History ==<br /> * 2019-11-04 - Announcing public Preview ([https://powerapps.microsoft.com/en-us/blog/environment-variables-available-in-preview/ MS announcement])<br /> * 2020-09-15 - Announcing GA and new Solution import experience ([https://powerapps.microsoft.com/en-us/blog/announcing-the-new-solution-import-experience-with-connections-and-environment-variables/ MS announcement])<br /> * 2021-04-14 - Announcing Type Data Source ([https://powerapps.microsoft.com/en-us/blog/announcing-data-source-environment-variables/ MS announcement])<br /> * 2021-08-19 - Announcing public Preview of Environment Variables Support in Power Platform Build Tools ([https://powerapps.microsoft.com/en-us/blog/announcing-the-public-preview-for-connection-references-support-in-power-platforms-tools/ MS announcement])<br /> * 2021-12-15 - Announcing GA of Environment Variables Support in Power Platform Build Tools ([https://powerapps.microsoft.com/en-us/blog/power-platform-developer-tools-november-refresh/ MS announcement])<br /> <br /> == Related Content ==<br /> === PowerWiki ===<br /> * [[How to set Environment Variables value]]<br /> * [[Model-driven apps Settings]]<br /> <br /> === Microsoft Resources ===<br /> * [https://docs.microsoft.com/en-us/powerapps/maker/data-platform/environmentvariables Use Environment Variables]<br /> * [https://docs.microsoft.com/en-us/power-platform/alm/devops-build-tool-tasks#power-platform-import-solution Import Solution Task] of Power Platform Build Tools<br /> <br /> === Community Content ===<br /> * [https://sharepains.com/2021/05/26/environment-variables-in-power-automate/ Environment Variables in Power Automate] by Pieter Veenstra<br /> * [https://iiu.dk/2021/05/12/power-platform-environment-variables/ Now it is time to be Curious about Power Platform Environment Variables!] by Jens Kofod<br /> * [https://www.powerplatformunicorn.com/2021/08/30/power-platform-data-source-environment-variables/ Power Platform Data Source Environment Variables] by Rebekka Aalbers<br /> * [https://www.inogic.com/blog/2021/02/using-environment-variables-in-dynamics-365-crm-part-1/ Using Environment Variables in Dynamics 365 CRM – Part 1] by Inogic<br /> * [https://crmtipoftheday.com/1363/get-environment-variables-in-power-automate-and-power-apps/ Tip #1363: Get Environment Variables in Power Automate (and Power Apps)] by CRM Tip of the Day<br /> * [https://github.com/drivardxrm/Dataverse-CustomApis Dataverse CustomAPIs to get EnvVar Value] by David Rivard</div> Benedikt http://powerwiki.net/index.php?title=Environment_Variables&diff=5668 Environment Variables 2021-12-19T14:34:56Z <p>Benedikt: </p> <hr /> <div>Environment Variables (EnvVars) can be used to retrieve a value based on the current environment.<br /> <br /> == General ==<br /> Environment Variables can return a value based on the environment the requesting application is in.<br /> EnvVars are solution aware and can therefore be &quot;transported&quot; with a usual Deployment (see [[ALM]]]).<br /> <br /> {{<br /> PWBoxInfo<br /> | title = Be aware<br /> | text = Local values should not be included in a solution. Otherwise, it will be impossible to override the value in a downstream environment.<br /> }}<br /> <br /> === Structure ===<br /> EnvVars are built with two tables:<br /> * Environment Variable Definition<br /> * Environment Variable Value<br /> <br /> ==== Environment Variable Definition ====<br /> As the name suggests posts in this table contain the definition of an environment variable. This contains<br /> * DiplayName<br /> * SchemaName<br /> * Description<br /> * Data Type<br /> * Default Value<br /> <br /> ==== Environment Variable Value ====<br /> Also called &quot;Local Value&quot;. A post in this table is always related to some definition and should never be included in a solution.<br /> It overrides the default value of a definition and is the value of the current environment.<br /> <br /> === Use case ===<br /> Use cases could for example be<br /> * URL's<br /> * Canvas App Ids<br /> * Record Ids<br /> * Switches<br /> * Connections<br /> * Other Configuration<br /> <br /> === How to create ===<br /> Environment Variables are, as mentioned, Solution components and should be created from a solution as well.<br /> First, the definition has to be created. After you save the first time you can add a local value. This local value should then be removed from the solution (via the ... besides it).<br /> <br /> === How to use ===<br /> Power Automate has a native integration with EnvVars. All the available EnvVars will be shown in the list of dynamic values.<br /> {{<br /> PWBoxInfo<br /> | title = Be aware<br /> | text = If you use this approach EnvVars are cached. When you change the value you have to turn all the flows off and on to get the new value.<br /> }}<br /> <br /> If you would like to use EnvVars in any other way (Plugins, JS, ...) you have to handle them yourself. This means getting the rows and deciding whether to use the default or local value.<br /> <br /> == History ==<br /> * 2019-11-04 - Announcing public Preview ([https://powerapps.microsoft.com/en-us/blog/environment-variables-available-in-preview/ link to MS announcement])<br /> * 2020-09-15 - Announcing GA and new Solution import experience ([https://powerapps.microsoft.com/en-us/blog/announcing-the-new-solution-import-experience-with-connections-and-environment-variables/ link to MS announcement])<br /> * 2021-04-14 - Announcing Type Data Source ([https://powerapps.microsoft.com/en-us/blog/announcing-data-source-environment-variables/ link to MS announcement])<br /> * 2021-08-19 - Announcing public Preview of Environment Variables Support in Power Platform Build Tools ([https://powerapps.microsoft.com/en-us/blog/announcing-the-public-preview-for-connection-references-support-in-power-platforms-tools/ link to MS announcement])<br /> * 2021-12-15 - Announcing GA of Environment Variables Support in Power Platform Build Tools ([https://powerapps.microsoft.com/en-us/blog/power-platform-developer-tools-november-refresh/ link to MS announcement])<br /> <br /> == Related Content ==<br /> === PowerWiki ===<br /> * [[How to set Environment Variables value]]<br /> * [[Model-driven apps Settings]]<br /> <br /> === Microsoft Resources ===<br /> * [https://docs.microsoft.com/en-us/powerapps/maker/data-platform/environmentvariables Use Environment Variables]<br /> * [https://docs.microsoft.com/en-us/power-platform/alm/devops-build-tool-tasks#power-platform-import-solution Import Solution Task] of Power Platform Build Tools<br /> <br /> === Community Content ===<br /> * [https://sharepains.com/2021/05/26/environment-variables-in-power-automate/ Environment Variables in Power Automate] by Pieter Veenstra<br /> * [https://iiu.dk/2021/05/12/power-platform-environment-variables/ Now it is time to be Curious about Power Platform Environment Variables!] by Jens Kofod<br /> * [https://www.powerplatformunicorn.com/2021/08/30/power-platform-data-source-environment-variables/ Power Platform Data Source Environment Variables] by Rebekka Aalbers<br /> * [https://www.inogic.com/blog/2021/02/using-environment-variables-in-dynamics-365-crm-part-1/ Using Environment Variables in Dynamics 365 CRM – Part 1] by Inogic<br /> * [https://crmtipoftheday.com/1363/get-environment-variables-in-power-automate-and-power-apps/ Tip #1363: Get Environment Variables in Power Automate (and Power Apps)] by CRM Tip of the Day<br /> * [https://github.com/drivardxrm/Dataverse-CustomApis Dataverse CustomAPIs to get EnvVar Value] by David Rivard</div> Benedikt http://powerwiki.net/index.php?title=Environment_Variables&diff=5667 Environment Variables 2021-12-19T14:33:42Z <p>Benedikt: </p> <hr /> <div>Environment Variables (EnvVars) can be used to retrieve a value based on the current environment.<br /> <br /> == General ==<br /> Environment Variables can return a value based on the environment the requesting application is in.<br /> EnvVars are solution aware and can therefore be &quot;transported&quot; with a usual Deployment (see [[ALM]]]).<br /> <br /> {{<br /> PWBoxInfo<br /> | title = Be aware<br /> | text = Local values should not be included in a solution. Otherwise, it will be impossible to override the value in a downstream environment.<br /> }}<br /> <br /> === Structure ===<br /> EnvVars are built with two tables:<br /> * Environment Variable Definition<br /> * Environment Variable Value<br /> <br /> ==== Environment Variable Definition ====<br /> As the name suggests posts in this table contain the definition of an environment variable. This contains<br /> * DiplayName<br /> * SchemaName<br /> * Description<br /> * Data Type<br /> * Default Value<br /> <br /> ==== Environment Variable Value ====<br /> Also called &quot;Local Value&quot;. A post in this table is always related to some definition and should never be included in a solution.<br /> It overrides the default value of a definition and is the value of the current environment.<br /> <br /> === Use case ===<br /> Use cases could for example be<br /> * URL's<br /> * Canvas App Ids<br /> * Record Ids<br /> * Switches<br /> * Connections<br /> * Other Configuration<br /> <br /> === How to create ===<br /> Environment Variables are, as mentioned, Solution components and should be created from a solution as well.<br /> First, the definition has to be created. After you save the first time you can add a local value. This local value should then be removed from the solution (via the ... besides it).<br /> <br /> === How to use ===<br /> Power Automate has a native integration with EnvVars. All the available EnvVars will be shown in the list of dynamic values.<br /> {{<br /> PWBoxInfo<br /> | title = Be aware<br /> | text = If you use this approach EnvVars are cached. When you change the value you have to turn all the flows off and on to get the new value.<br /> }}<br /> <br /> If you would like to use EnvVars in any other way (Plugins, JS, ...) you have to handle them yourself. This means getting the rows and deciding whether to use the default or local value.<br /> <br /> == History ==<br /> * 2019-11-04 - Announcing public Preview ([https://powerapps.microsoft.com/en-us/blog/environment-variables-available-in-preview/ link to MS announcement])<br /> * 2020-09-15 - Announcing GA and new Solution import experience ([https://powerapps.microsoft.com/en-us/blog/announcing-the-new-solution-import-experience-with-connections-and-environment-variables/ link to MS announcement])<br /> * 2021-04-14 - Announcing Type Data Source ([https://powerapps.microsoft.com/en-us/blog/announcing-data-source-environment-variables/ link to MS announcement])<br /> * 2021-08-19 - Announcing public Preview of Environment Variables Support in Power Platform Build Tools ([https://powerapps.microsoft.com/en-us/blog/announcing-the-public-preview-for-connection-references-support-in-power-platforms-tools/ link to MS announcement])<br /> * 2021-12-15 - Announcing GA of Environment Variables Support in Power Platform Build Tools ([https://powerapps.microsoft.com/en-us/blog/power-platform-developer-tools-november-refresh/ link to MS announcement])<br /> <br /> == Related Content ==<br /> === PowerWiki ===<br /> * [[How to set Environment Variables value]]<br /> * [[Model-driven apps Settings]]<br /> <br /> === Microsoft Resources ===<br /> * [https://docs.microsoft.com/en-us/powerapps/maker/data-platform/environmentvariables Use Environment Variables]<br /> * [docs.microsoft.com/en-us/power-platform/alm/devops-build-tool-tasks#power-platform-import-solution Import Solution Task] of Power Platform Build Tools<br /> <br /> === Community Content ===<br /> * [https://sharepains.com/2021/05/26/environment-variables-in-power-automate/ Environment Variables in Power Automate] by Pieter Veenstra<br /> * [https://iiu.dk/2021/05/12/power-platform-environment-variables/ Now it is time to be Curious about Power Platform Environment Variables!] by Jens Kofod<br /> * [https://www.powerplatformunicorn.com/2021/08/30/power-platform-data-source-environment-variables/ Power Platform Data Source Environment Variables] by Rebekka Aalbers<br /> * [https://www.inogic.com/blog/2021/02/using-environment-variables-in-dynamics-365-crm-part-1/ Using Environment Variables in Dynamics 365 CRM – Part 1] by Inogic<br /> * [https://crmtipoftheday.com/1363/get-environment-variables-in-power-automate-and-power-apps/ Tip #1363: Get Environment Variables in Power Automate (and Power Apps)] by CRM Tip of the Day<br /> * [github.com/drivardxrm/Dataverse-CustomApis Dataverse CustomAPIs to get EnvVar Value] by David Rivard</div> Benedikt http://powerwiki.net/index.php?title=Call_for_Speakers&diff=5537 Call for Speakers 2021-12-14T21:39:01Z <p>Benedikt: </p> <hr /> <div>This page contains a list of call for speakers for events brought to you by the community.<br /> <br /> {|<br /> ! Name<br /> ! Type<br /> ! Description<br /> ! Event date<br /> ! Deadline for submission<br /> |-<br /> | [https://events.powercommunity.com/azure-integration-bootcamp-2022/ Integration Summit] || Hybrid || We are Excited to Announce the Azure Integration Bootcamp taking place on the 29th January 2022 for Beginner to Advanced Deep Dive Sessions on Azure Integration Solutions. || 2022-01-29 ||<br /> |-<br /> | [https://events.powercommunity.com/global-power-automate-bootcamp/ Intergalactic Automation Summit] || Hybrid || We are Excited to Announce the largest Global Automation Bootcamp taking place on the 5th February 2022 for Beginner to Advanced Deep Dive Sessions focused on Power Automate. || 2022-02-05 ||<br /> |-<br /> | [https://events.powercommunity.com/power-platform-alm-devops-bootcamp/ Power Platform ALM Bootcamp] || Hybrid || We are Excited to Announce the Power Platform ALM Bootcamp taking place on the 12th February 2022 for Beginner to Advanced Deep Dive Sessions on Power Platform ALM || 2022-02-12 ||<br /> |-<br /> | [https://events.powercommunity.com/calgary-power-challenge/ Calgary Power Challenge] || In-Person || The event will be held at [https://www.winsport.ca/ Canada’s Olympic Park] in Calgary. Sessions will be focused on Power Apps and Power Platform Development. || 2022-03-05 || <br /> |-<br /> | [https://dynamicscon.com/ DynamicsCon] || Online || DynamicsCon is calling all Microsoft Business Applications Professionals for the 4th virtual DynamicsCon event! || 2022-03-15 - 2022-03-17 || 2022-01-07<br /> |-<br /> | [https://sessionize.com/power-platform-24-mar22 Power Platform 24] || Online || Power Platform 24 is the 24-hour virtual conference focused on the Power Platform and Dynamics 365. Join Power Platform enthusiasts and Microsoft dignitaries from around the world for a full day of sessions about Microsoft Business Applications. No matter where you are in the world, this is in your time zone. || 2022-03-15 - 2022-03-16 || 2022-02-15<br /> |}<br /> <br /> <br /> [[Category:Community]]</div> Benedikt http://powerwiki.net/index.php?title=Call_for_Speakers&diff=5536 Call for Speakers 2021-12-14T21:37:59Z <p>Benedikt: </p> <hr /> <div>This page contains a list of call for speakers for events brought to you by the community.<br /> <br /> {|<br /> ! Name<br /> ! Type<br /> ! Description<br /> ! Event date<br /> ! Deadline for submission<br /> |-<br /> | [https://dynamicscon.com/ DynamicsCon] || Online || DynamicsCon is calling all Microsoft Business Applications Professionals for the 4th virtual DynamicsCon event! || 2022-03-15 - 2022-03-17 || 2022-01-07<br /> |-<br /> | [https://events.powercommunity.com/azure-integration-bootcamp-2022/ Integration Summit] || Hybrid || We are Excited to Announce the Azure Integration Bootcamp taking place on the 29th January 2022 for Beginner to Advanced Deep Dive Sessions on Azure Integration Solutions. || 2022-01-29 ||<br /> |-<br /> | [https://events.powercommunity.com/global-power-automate-bootcamp/ Intergalactic Automation Summit] || Hybrid || We are Excited to Announce the largest Global Automation Bootcamp taking place on the 5th February 2022 for Beginner to Advanced Deep Dive Sessions focused on Power Automate. || 2022-02-05 ||<br /> |-<br /> | [https://events.powercommunity.com/power-platform-alm-devops-bootcamp/ Power Platform ALM Bootcamp] || Hybrid || We are Excited to Announce the Power Platform ALM Bootcamp taking place on the 12th February 2022 for Beginner to Advanced Deep Dive Sessions on Power Platform ALM || 2022-02-12 ||<br /> |-<br /> | [https://sessionize.com/power-platform-24-mar22 Power Platform 24] || Online || Power Platform 24 is the 24-hour virtual conference focused on the Power Platform and Dynamics 365. Join Power Platform enthusiasts and Microsoft dignitaries from around the world for a full day of sessions about Microsoft Business Applications. No matter where you are in the world, this is in your time zone. || 2022-03-15 - 2022-03-16 || 2022-02-15<br /> |-<br /> | [https://events.powercommunity.com/calgary-power-challenge/ Calgary Power Challenge] || In-Person || The event will be held at [https://www.winsport.ca/ Canada’s Olympic Park] in Calgary. Sessions will be focused on Power Apps and Power Platform Development. || 2022-03-05 || <br /> |}<br /> <br /> <br /> [[Category:Community]]</div> Benedikt http://powerwiki.net/index.php?title=Call_for_Speakers&diff=5319 Call for Speakers 2021-12-07T13:01:30Z <p>Benedikt: </p> <hr /> <div>This page contains a list of call for speakers for events brought to you by the community.<br /> <br /> {|<br /> ! Name<br /> ! Type<br /> ! Description<br /> ! Link<br /> ! Deadline for submission<br /> |-<br /> | Power Platform 24 || Online || Power Platform 24 is the 24-hour virtual conference focused on the Power Platform and Dynamics 365. Join Power Platform enthusiasts and Microsoft dignitaries from around the world for a full day of sessions about Microsoft Business Applications. No matter where you are in the world, this is in your time zone. || [https://sessionize.com/power-platform-24-mar22 CFS Page] || 2022-02-15<br /> |-<br /> | Power Platform ALM Bootcamp || Hybrid || We are Excited to Announce the Power Platform ALM Bootcamp taking place on the 12th February 2022 for Beginner to Advanced Deep Dive Sessions on Power Platform ALM || [https://events.powercommunity.com/power-platform-alm-devops-bootcamp/ Event Page] || <br /> |-<br /> | Intergalactic Automation Summit || Hybrid || We are Excited to Announce the largest Global Automation Bootcamp taking place on the 5th February 2022 for Beginner to Advanced Deep Dive Sessions focused on Power Automate || [https://events.powercommunity.com/global-power-automate-bootcamp/ Event Page] || <br /> |-<br /> | Integration Summit || Hybrid || We are Excited to Announce the Azure Integration Bootcamp taking place on the 29th January 2022 for Beginner to Advanced Deep Dive Sessions on Azure Integration Solutions || [https://events.powercommunity.com/azure-integration-bootcamp-2022/ Event Page] || <br /> |}<br /> <br /> [[Category:Community]]</div> Benedikt http://powerwiki.net/index.php?title=TypeScript&diff=5296 TypeScript 2021-12-07T08:04:27Z <p>Benedikt: </p> <hr /> <div>[https://www.typescriptlang.org TypeScript] is a superset of JavaScript. It is strongly typed and makes development much easier.<br /> <br /> == Strongly typed ==<br /> <br /> Since TypeScript is strongly typed the job of writing it gets a lot easier. If you use a proper IDE (Visual Studio Code for example) it will show you type errors while developing.<br /> <br /> == Backward compatibility ==<br /> <br /> In the end, TypeScript has to be transpiled/compiled to JavaScript. This could, for example, be done via the “tsc” command, which will transpile the TS file to the configured target ECMAScript version (ECMAScript is a standard to define JavaScript. You can read more about that [https://www.w3schools.com/Js/js_versions.asp here] as well as about the browser support [http://kangax.github.io/compat-table/es6/ here]). With the ability to target different/older versions of the standard the TS will get automatically transpiled into a JS file that is compatible with older browser versions. This means one can write readable code without thinking about compatibility. When transpiled it gets something that is compatible. Of course, it’s not always that easy. In the screenshot below you can see a part of our transpiled demo file.<br /> <br /> == Tests &amp; Debugging ==<br /> <br /> With TypeScript it is much easier to create tests that could be run automatically in a pipeline. Another big plus is that it is possible to debug the code with the help of source map files.<br /> <br /> == Community Content ==<br /> * [https://learn.develop1.net/courses/building-javascript-web-resources-using-typescript Free Course on TypeScript] by Scott Durow<br /> * [https://www.youtube.com/playlist?list=PLqJfvq4Fy1P5Q5l19fFUTS3QchwsmdxPZ YouTube Playlist of TypeScript for Dataverse Mentoring Program] by Danish Naglekar<br /> * [https://develop1.net/public/post/2018/06/09/Lets-start-TypeScript-Part-1 Let’s start TypeScript – Part 1] by Scott Durow<br /> * [https://www.oliverflint.co.uk/2020/03/07/D365-Typescript-Webresources-Part-1/ D365 TypeScript Web Resources - Part 1 - Basics] by Oliver Flint<br /> * [https://benediktbergmann.eu/2020/11/01/how-to-call-xrm-webapi-using-typescript/ Setting up a TypeScript project for Dataverse] by Benedikt Bergmann<br /> <br /> [[Category:Developer]]</div> Benedikt http://powerwiki.net/index.php?title=TypeScript&diff=5295 TypeScript 2021-12-07T08:02:08Z <p>Benedikt: </p> <hr /> <div>[https://www.typescriptlang.org TypeScript] is a superset of JavaScript. It is strongly typed and makes development much easier.<br /> <br /> == Strongly typed ==<br /> <br /> Since TypeScript is strongly typed the job of writing it gets a lot easier. If you use a proper IDE (Visual Studio Code for example) it will show you type errors while developing.<br /> <br /> == Backward compatibility ==<br /> <br /> In the end, TypeScript has to be transpiled/compiled to JavaScript. This could, for example, be done via the “tsc” command, which will transpile the TS file to the configured target ECMAScript version (ECMAScript is a standard to define JavaScript. You can read more about that [https://www.w3schools.com/Js/js_versions.asp here] as well as about the browser support [http://kangax.github.io/compat-table/es6/ here]). With the ability to target different/older versions of the standard the TS will get automatically transpiled into a JS file that is compatible with older browser versions. This means one can write readable code without thinking about compatibility. When transpiled it gets something that is compatible. Of course, it’s not always that easy. In the screenshot below you can see a part of our transpiled demo file.<br /> <br /> == Tests &amp; Debugging ==<br /> <br /> With TypeScript it is much easier to create tests that could be run automatically in a pipeline. Another big plus is that it is possible to debug the code with the help of source map files.<br /> <br /> == Community Content ==<br /> * [https://learn.develop1.net/courses/building-javascript-web-resources-using-typescript Free Course on TypeSCript] by Scott Durow<br /> * [https://develop1.net/public/post/2018/06/09/Lets-start-TypeScript-Part-1 Let’s start TypeScript – Part 1] by Scott Durow<br /> * [https://www.oliverflint.co.uk/2020/03/07/D365-Typescript-Webresources-Part-1/ D365 TypeScript Web Resources - Part 1 - Basics] by Oliver Flint<br /> * [https://benediktbergmann.eu/2020/11/01/how-to-call-xrm-webapi-using-typescript/ Setting up a TypeScript project for Dataverse] by Benedikt Bergmann<br /> <br /> [[Category:Developer]]</div> Benedikt http://powerwiki.net/index.php?title=Template:Quote&diff=5289 Template:Quote 2021-12-06T22:55:19Z <p>Benedikt: </p> <hr /> <div>&lt;div class=&quot;PWCite&quot;&gt;<br /> &lt;blockquote&gt;{{{text}}}&lt;/blockquote&gt;<br /> &lt;cite&gt;{{{author}}}&lt;/cite&gt;<br /> &lt;/div&gt;</div> Benedikt http://powerwiki.net/index.php?title=MediaWiki:Common.css&diff=5288 MediaWiki:Common.css 2021-12-06T22:49:40Z <p>Benedikt: </p> <hr /> <div>/* For the Top banner on Start Page */<br /> <br /> #pw-bottombanner {<br /> clear: both;<br /> position: relative;<br /> box-sizing: border-box;<br /> width: 100%;<br /> margin-top: 0em;<br /> min-width: 47em;<br /> border-color: #ddd;<br /> background-color: #f9f9f9;<br /> white-space: nowrap;<br /> }<br /> <br /> #mp-topbanner {<br /> clear: both;<br /> position: relative;<br /> box-sizing: border-box;<br /> width: 100%;<br /> margin-top: 1.2em;<br /> margin-bottom: 0em;<br /> min-width: 47em;<br /> border-color: #ddd;<br /> background-color: #f9f9f9;<br /> white-space: nowrap;<br /> }<br /> <br /> .mp-bordered,<br /> .pw-bordered,<br /> .mp-h2,<br /> body.skin-timeless .mp-h2 { /* Timeless needs a higher specificity */<br /> border-width: 1px;<br /> border-style: solid;<br /> }<br /> <br /> #mp-topbanner,<br /> .mp-h2,<br /> #mp-left {<br /> color: #000;<br /> }<br /> <br /> #mp-welcomecount {<br /> margin: 0.4em;<br /> width: 22em;<br /> text-align: center;<br /> }<br /> <br /> #mp-welcome {<br /> font-size: 162%;<br /> padding: 0.1em;<br /> }<br /> <br /> #mp-free {<br /> font-size: 95%;<br /> }<br /> <br /> #articlecount {<br /> font-size: 85%;<br /> }<br /> <br /> #mp-portals {<br /> position: absolute;<br /> right: -1em;<br /> top: 50%;<br /> margin-top: -2.4em;<br /> width: 38%;<br /> min-width: 25em;<br /> font-size: 95%;<br /> }<br /> <br /> #mp-portals li {<br /> position: absolute;<br /> left: 0;<br /> top: 0;<br /> }<br /> <br /> #mp-portals .portal-hmid {<br /> left: 33%;<br /> }<br /> <br /> #mp-portals .portal-hright {<br /> left: 66%;<br /> }<br /> <br /> #mp-portals .portal-vmid {<br /> top: 1.6em;<br /> }<br /> <br /> #mp-portals .portal-vbot {<br /> top: 3.2em;<br /> }<br /> <br /> .portal-hright.portal-vbot {<br /> font-weight: bold;<br /> }<br /> <br /> #mp-banner {<br /> margin-top: 4px;<br /> padding: 0.5em;<br /> background-color: #fffaf5;<br /> border-color: #f2e0ce;<br /> }<br /> <br /> .mp-h2,<br /> body.skin-timeless .mp-h2 { /* Timeless needs a higher specificity */<br /> margin: 0.5em;<br /> padding: 0.2em 0.4em;<br /> font-size: 120%;<br /> font-weight: bold;<br /> font-family: inherit;<br /> }<br /> <br /> h2.mp-h2::after { /* Remove borders in Timeless */ <br /> border: none;<br /> }<br /> <br /> .mp-later {<br /> font-size: 85%;<br /> font-weight: normal;<br /> }<br /> <br /> /* End of Top banner on Start Page */<br /> <br /> /* For the rest of the Start Page */<br /> <br /> .mainpage_row {<br /> display: flex;<br /> flex-direction: row;<br /> flex-flow: row wrap;<br /> justify-content: space-between;<br /> padding: 0;<br /> margin: 0 -5px 0 -5px;<br /> }<br /> .mainpage_box {<br /> flex: 1;<br /> margin: 5px;<br /> min-width: 210px;<br /> border: 1px solid #CCC;<br /> padding: 0 10px 10px 10px;<br /> box-shadow: 0 2px 2px rgba(0,0,0,0.1);<br /> }<br /> .mainpage_box h3 {<br /> /* Reset padding so is equal across skins */<br /> padding: 0;<br /> margin: 0.5em 0;<br /> <br /> }<br /> .mainpage_box h3 .header_icon {<br /> float: left;<br /> margin-right: 5px;<br /> <br /> }<br /> .mainpage_box .items {<br /> border-top: 1px solid #CCC;<br /> padding-top: 0.5em;<br /> }<br /> .mainpage_box p:last-child {<br /> margin-bottom: 0;<br /> }<br /> .mainpage_boxcontents_small {<br /> font-size: 95%;<br /> }<br /> <br /> @media screen and (max-width: 719px) {<br /> .thumb {<br /> float: none;<br /> }<br /> .thumb, .thumbinner {<br /> margin-left: auto;<br /> margin-right: auto;<br /> }<br /> }<br /> <br /> .pw-ui-button, .pw-ui-progressive {<br /> border-radius: 4px !important;<br /> border: 1px solid #40798C !important;<br /> color: #40798C !important;<br /> background: #fff !important;<br /> text-shadow: 0px 0px 0px;<br /> }<br /> <br /> .pw-ui-button.pw-ui-progressive:hover, .pw-ui-button.pw-ui-progressive:focus, .pw-ui-button.pw-ui-progressive:active, .pw-ui-button:hover, .pw-ui-progressive:hover, .pw-ui-button:focus, .pw-ui-progressive:focus {<br /> box-shadow: 0px 0px 0px !important;<br /> text-shadow: 0px 0px 0px !important;<br /> border: 1px solid #40798C !important;<br /> }<br /> <br /> /* End for the Start Page */<br /> <br /> <br /> body {<br /> font-family: &quot;Helvetica Neue&quot;, Helvetica, Arial, sans-serif !important;<br /> background: #fff !important;<br /> }<br /> <br /> p {<br /> font-weight: 300 !important;<br /> line-height: 1.9 !important;<br /> }<br /> <br /> <br /> table, td, th {<br /> border: 0px !important;<br /> border-collapse: collapse !important;<br /> padding: 5px !important;<br /> }<br /> <br /> <br /> ul, li {<br /> background: transparent !important;<br /> border: 0px !important;<br /> line-height: 1.8 !important;<br /> font-size: 14px !important;<br /> font-weight: 300 !important;<br /> }<br /> <br /> li span {<br /> background: transparent !important;<br /> border: 0px !important;<br /> font-size: 14px !important;<br /> }<br /> <br /> .referencetooltip {<br /> background-color: #EEE !important;<br /> }<br /> <br /> dl {<br /> font-weight: 300 !important;<br /> }<br /> <br /> dt {<br /> font-style: italic;<br /> font-size: 16px !important;<br /> margin-top: 10px !important;<br /> }<br /> <br /> dd {<br /> font-size: 15px !important;<br /> }<br /> <br /> .mw-wiki-logo {<br /> padding-left: 15px !important;<br /> padding-top: 10px !important;<br /> border: none !important;<br /> }<br /> <br /> /*#p-logo a {<br /> background-image: url('https://i.imgur.com/ur4m5Ia.png') !important;<br /> }*/<br /> <br /> code {<br /> padding: 3px !important;<br /> background: transparent !important;<br /> color: #39892f !important;<br /> }<br /> <br /> tt {<br /> font-family: 'Source Code Pro', 'Lucida Sans Unicode', 'Courier New' !important;<br /> font-size: 16px !important;<br /> }<br /> <br /> .new, .new:link, .new:visited {<br /> color: #cd5b45 !important;<br /> }<br /> <br /> blockquote {<br /> border: 0px !important;<br /> font-style: italic !important;<br /> font-size: 20px !important;<br /> margin: 35px 75px !important;<br /> line-height: 1.5 !important;<br /> font-weight: 300 !important;<br /> background: transparent !important;<br /> }<br /> <br /> select {<br /> padding: 0px 10px;<br /> }<br /> <br /> .mw-ui-button, .mw-ui-progressive {<br /> border-radius: 4px !important;<br /> border: 1px solid #347Bff !important;<br /> color: #347Bff !important;<br /> background: #fff !important;<br /> text-shadow: 0px 0px 0px;<br /> }<br /> <br /> .mw-ui-button.mw-ui-progressive:hover, .mw-ui-button.mw-ui-progressive:focus, .mw-ui-button.mw-ui-progressive:active, .mw-ui-button:hover, .mw-ui-progressive:hover, .mw-ui-button:focus, .mw-ui-progressive:focus {<br /> box-shadow: 0px 0px 0px !important;<br /> text-shadow: 0px 0px 0px !important;<br /> border: 1px solid #347Bff !important;<br /> }<br /> <br /> #wpSave, #wpPreview, #wpDiff {<br /> border-radius: 4px !important;<br /> border: 1px solid #347Bff !important;<br /> color: #347Bff !important;<br /> background: #fff !important;<br /> text-shadow: 0px 0px 0px;<br /> padding: 0.5em 1em;<br /> cursor: pointer;<br /> }<br /> <br /> #wpSave:hover, #wpPreview:hover, #wpDiff:hover {<br /> color: rgba(52, 123, 255, 0.5) !important;<br /> ;<br /> }<br /> <br /> /* Search */<br /> <br /> #simpleSearch {<br /> background: transparent !important;<br /> border-color: #ccc !important;<br /> }<br /> <br /> #searchInput {<br /> background: transparent !important;<br /> }<br /> <br /> .mw-ui-input {<br /> border: 1px solid #347Bff !important;<br /> color: #000 !important;<br /> background: #fff !important;<br /> font-size: 16px !important;<br /> }<br /> <br /> .mw-ui-input:focus {<br /> box-shadow: 0px 0px 0px !important;<br /> }<br /> <br /> .mw-content-ltr pre {<br /> font-family: &quot;Courier New&quot;, Lucida Console, sans-serif !important;<br /> color: #000d26 !important;<br /> }<br /> <br /> .suggestions {<br /> font-weight: 300 !important;<br /> font-size: 15px !important;<br /> max-width: 300px !important;<br /> margin-top: 15px !important;<br /> border: 0px !important;<br /> box-shadow: 2px 2px 10px 2px rgba(0, 0, 0, 0.5);<br /> }<br /> <br /> .suggestions-results {<br /> border: 0px !important;<br /> }<br /> <br /> .suggestions-result {<br /> padding: 10px !important;<br /> }<br /> <br /> .imeselector, #searchEngines {<br /> display: none !important;<br /> }<br /> <br /> .mw-search-formheader {<br /> border: 0px !important;<br /> background: transparent !important;<br /> }<br /> <br /> .central-featured-logo {<br /> background-image: url('https://i.imgur.com/nRDTbeb.png') !important;<br /> }<br /> <br /> .mw-search-result-heading, .searchresult, .searchmatch {<br /> font-size: 14px !important;<br /> font-weight: 400 !important;<br /> padding: 3px 0px !important;<br /> }<br /> <br /> .searchmatch {<br /> font-weight: 700 !important;<br /> }<br /> <br /> /*<br /> .mw-search-result-data, .mw-search-createlink {<br /> display: none;<br /> }<br /> */<br /> <br /> #mw-page-base, .vectorTabs {<br /> background: transparent !important;<br /> border: 0px !important;<br /> }<br /> <br /> #content {<br /> border: 0px !important;<br /> margin-left: 215px !important;<br /> }<br /> <br /> .portal {<br /> background: transparent !important;<br /> }<br /> <br /> #mw-panel {<br /> width: 200px !important;<br /> border-right: 1px solid #bbb;<br /> background: white !important;<br /> padding-left: 10px !important;<br /> }<br /> <br /> #p-logo {<br /> left: 0px;<br /> padding-left: 10px;<br /> background-color: white;<br /> }<br /> <br /> #p-logo a {<br /> padding-left: 40px;<br /> background-color: white;<br /> left: 0px;<br /> border-right: 1px solid #aaa;<br /> }<br /> <br /> #p-logo a:hover {<br /> opacity: 1.0;<br /> }<br /> <br /> #mw-head {<br /> background-color: #f9f9f9;<br /> opacity: 1.0;<br /> box-shadow: 0px 1px 2px #aaa;<br /> -webkit-transition-property: opacity !important;<br /> -moz-transition-property: opacity !important;<br /> -o-transition-property: opacity !important;<br /> -ms-transition-property: opacity !important;<br /> transition-property: opacity !important;<br /> -webkit-transition-duration: 0.5s !important;<br /> -moz-transition-duration: 0.5s !important;<br /> -o-transition-duration: 0.5s !important;<br /> -ms-transition-duration: 0.5s !important;<br /> transition-duration: 0.25s !important;<br /> <br /> }<br /> <br /> #mw-head:hover {<br /> opacity: 1.0 !important;<br /> }<br /> <br /> .uls-settings-trigger {<br /> display: none !important;<br /> }<br /> <br /> #left-navigation {<br /> margin-left: 233px !important;<br /> }<br /> <br /> .wikitable {<br /> font-weight: 300 !important;<br /> }<br /> <br /> .wikitable td, .wikitable th {<br /> border: 1px dashed rgba(0, 0, 0, 0.07) !important;<br /> }<br /> <br /> pre {<br /> line-height: 1.3 !important;<br /> font-family: &quot;Courier New&quot;, Lucida Console, sans-serif !important;<br /> border: 0px !important;<br /> background: 0px !important;<br /> font-size: 16px !important;<br /> }<br /> <br /> .mw-code {<br /> border: 0px !important;<br /> padding: 17px !important;<br /> background: 0px !important;<br /> font-size: 16px !important;<br /> }<br /> <br /> .toc {<br /> background: transparent !important;<br /> border-style: dashed !important;<br /> display: block !important;<br /> max-width: 300px !important;<br /> }<br /> <br /> .toctoggle {<br /> display: none !important;<br /> }<br /> <br /> .thumbinner, .thumb, .toccolours, .graytable {<br /> background: transparent !important;<br /> border: 0px !important;<br /> font-size: 16px !important;<br /> }<br /> <br /> .thumbimage {<br /> border: 0px !important;<br /> }<br /> <br /> .thumbcaption {<br /> font-style: italic !important;<br /> margin: 7px 0px !important;<br /> }<br /> <br /> .thumbimage:hover {<br /> opacity: 0.85 !important;<br /> }<br /> <br /> .dablink {<br /> margin: 14px 0px !important;<br /> font-weight: 300 !important;<br /> font-size: 18px !important;<br /> }<br /> <br /> #siteSub, .flaggedrevs_preview {<br /> display: none !important;<br /> }<br /> <br /> .ambox, .tmbox, .Note, .informationbox {<br /> margin: 5px 0px !important;<br /> font-size: 18px !important;<br /> font-weight: 700 !important;<br /> line-height: 1.5 !important;<br /> border: 1px dashed #aaa !important;<br /> max-width: 550px !important;<br /> font-weight: 300 !important;<br /> }<br /> <br /> .ambox td, .tmbox td {<br /> padding: 10px !important;<br /> }<br /> <br /> .ambox-text-small, .mbox-text, .Note td {<br /> font-size: 14px !important;<br /> font-weight: 300 !important;<br /> color: #000 !important;<br /> }<br /> <br /> .ambox-image, .mbox-image {<br /> display: none;<br /> }<br /> <br /> #request_for_deletion, .ambox-serious {<br /> background: rgba(255, 0, 0, 0.1) !important;<br /> border: 1px dashed rgba(255, 0, 0, 0.15) !important;<br /> color: #a00000 !important;<br /> }<br /> <br /> .tmbox-notice, .tmbox-move, .Note {<br /> background: rgba(150, 75, 0, 0.1) !important;<br /> border: 1px dashed rgba(150, 75, 0, 0.15) !important;<br /> }<br /> <br /> .informationbox {<br /> background: #fff !important;<br /> padding: 10px !important;<br /> font-size: 14px !important;<br /> }<br /> <br /> .editOptions {<br /> background: #fff !important;<br /> border: 0px !important;<br /> }<br /> <br /> .catlinks {<br /> background: transparent !important;<br /> border: 1px dashed #aaa !important;<br /> font-size: 16px !important;<br /> }<br /> <br /> .infobox, .tright, .toccolours {<br /> border: 0px !important;<br /> background: transparent !important;<br /> border-collapse: collapse !important;<br /> }<br /> <br /> .infobox td, .infobox th, .tright td, .tright th, .toccolours td, .toccolours th {<br /> padding: 5px !important;<br /> background: transparent !important;<br /> font-weight: 400 !important;<br /> border: 1px dashed rgba(0, 0, 0, 0.07) !important;<br /> }<br /> <br /> .image img:hover {<br /> opacity: 0.85 !important;<br /> }<br /> <br /> .globegris {<br /> background: transparent !important;<br /> }<br /> <br /> .mw-editsection-bracket, .references-small b, .mw-cite-backlink, .plainlinksneverexpand {<br /> display: none !important;<br /> }<br /> <br /> #floating_object {<br /> display: none;<br /> }<br /> <br /> .navbox, .nowraplinks {<br /> margin: 10px 0px !important;<br /> border-collapse: collapse !important;<br /> }<br /> <br /> .navbox td, .navbox th, .nowraplinks td, .nowraplinks th {<br /> padding: 9px 6px !important;<br /> font-size: 14px !important;<br /> font-weight: 300 !important;<br /> border: 1px solid #fff !important;<br /> }<br /> <br /> .NavFrame {<br /> border: 0px !important;<br /> background: transparent !important;<br /> padding: 0px !important;<br /> }<br /> <br /> .NavHead {<br /> margin: 10px 0px !important;<br /> padding: 12px !important;<br /> font-size: 16px !important;<br /> font-weight: 700 !important;<br /> background: transparent !important;<br /> }<br /> <br /> .Boxmerge {<br /> border: 0px !important;<br /> }<br /> <br /> #coordinates {<br /> display: none !important;<br /> }<br /> <br /> #mw-fr-revisiontag, #mw-fr-reviewnotice {<br /> display: none !important;<br /> }<br /> <br /> div#footer {<br /> margin-left: 14em !important;<br /> padding: 1.25em 1.5em 1.5em !important;<br /> }<br /> <br /> .mw-footer {<br /> margin-left: 14em !important;<br /> padding: 1.25em 1.5em 1.5em !important;<br /> }<br /> <br /> <br /> /* General styling */<br /> <br /> :root {<br /> --primary-color: #742774;<br /> --primary-color-light:#c5b7c5;<br /> --primary-color-light2: #e9e4e9;<br /> --secondary-color: #236767;<br /> --dark-color: #0B2027;<br /> <br /> --success-color: #11620B;<br /> --success-color-light: #D2FBD0;<br /> <br /> --warning-color: #b88a00;<br /> --warning-color-light: #FFEED8;<br /> <br /> --error-color: #CC0000;<br /> --error-color-light: #E5B4B4;<br /> <br /> --grey-light-1: #F9F9F9;<br /> <br /> --powerautomate-primary-color: #356CDA;<br /> --powervirtualagent-primary-color: #327B8F;<br /> --powerbi-primary-color: #E1AD34;<br /> }<br /> <br /> <br /> /******* Styling headers *******/<br /> h1, h2, h3, h4, h5, h6 {<br /> color: var(--primary-color);<br /> border: 0px;<br /> font-family: 'Arial';<br /> }<br /> <br /> h1 {<br /> font-weight: 700;<br /> font-size: 36px;<br /> }<br /> <br /> h2 {<br /> font-weight: 400;<br /> font-size: 26px;<br /> }<br /> <br /> h3 {<br /> font-weight: 400;<br /> font-size: 16px;<br /> }<br /> <br /> /******* Styling links *******/<br /> a:not(.image), a:not(.image):visited {<br /> color: black !important;<br /> }<br /> <br /> a:not(.image):hover, a:not(.image):visited:hover{<br /> color: var(--primary-color) !important;<br /> }<br /> <br /> #bodyContent a:not(.image), #bodyContent a:not(.image):visited{<br /> text-decoration: underline !important;<br /> }<br /> <br /> #bodyContent a:not(.image):hover, #bodyContent a:not(.image):visited:hover {<br /> text-decoration: none !important;<br /> color: var(--primary-color) !important;<br /> }<br /> <br /> .mw-cookiewarning-container a, .mw-cookiewarning-container a:visited{<br /> color: white !important;<br /> }<br /> <br /> .mw-cookiewarning-container a:hover, .mw-cookiewarning-container input:hover{<br /> color: white !important;<br /> text-decoration: underline;<br /> }<br /> <br /> /******* Tables *******/<br /> table {<br /> margin: 2em 0;<br /> }<br /> <br /> table, td, th{<br /> border: 1px solid var(--primary-color) !important;<br /> }<br /> <br /> tr:nth-child(odd) {<br /> background-color: var(--primary-color-light2);<br /> }<br /> <br /> th {<br /> text-align:left;<br /> background-color: var(--primary-color-light);<br /> }<br /> <br /> /******* PW Boxes *******/<br /> #bodyContent .pw-box{<br /> margin: 1em 0;<br /> padding: 1em;<br /> border-width: 1px;<br /> border-left-width: 5px;<br /> border-style: solid;<br /> border-color: black;<br /> border-radius: 6px;<br /> font-size: inherit !important;<br /> }<br /> <br /> #bodyContent .pw-box.infobox-present{<br /> /*<br /> 300px = width of infobox<br /> 5em = 1x margin of infobox + 2x padding of infobox + 2x padding of PWBox<br /> 8px = 5px left border of PWBox + 1px right border of PWBox + 2 pixel (left and right) border of InfoBox<br /> */<br /> width:calc(100% - 300px - 5em - 8px);<br /> max-width:calc(100% - 300px - 5em - 8px);<br /> }<br /> <br /> #bodyContent .pw-box h3{<br /> margin-top: 0;<br /> font-weight:bold;<br /> }<br /> <br /> #bodyContent .pw-box.info{<br /> border-color: var(--primary-color);<br /> color: var(--primary-color);<br /> background-color: var(--primary-color-light);<br /> }<br /> #bodyContent .pw-box.info h3{<br /> color: var(--primary-color);<br /> }<br /> <br /> #bodyContent .pw-box.info a,<br /> #bodyContent .pw-box.info a:visited{<br /> color: var(--primary-color) !important;<br /> }<br /> <br /> #bodyContent .pw-box.warning{<br /> border-color: var(--warning-color);<br /> color: var(--warning-color);<br /> background-color: var(--warning-color-light);<br /> }<br /> #bodyContent .pw-box.warning h3{<br /> color: var(--warning-color);<br /> }<br /> <br /> #bodyContent .pw-box.warning a,<br /> #bodyContent .pw-box.warning a:visited{<br /> color: var(--warning-color) !important;<br /> }<br /> <br /> #bodyContent .pw-box.error{<br /> border-color: var(--error-color);<br /> color: var(--error-color);<br /> background-color: var(--error-color-light);<br /> }<br /> <br /> #bodyContent .pw-box.error h3{<br /> color: var(--error-color);<br /> }<br /> <br /> #bodyContent .pw-box.error a,<br /> #bodyContent .pw-box.error a:visited{<br /> color: var(--error-color) !important;<br /> }<br /> <br /> #bodyContent .pw-box.success{<br /> border-color: var(--success-color);<br /> color: var(--success-color);<br /> background-color: var(--success-color-light);<br /> }<br /> <br /> #bodyContent .pw-box.success h3{<br /> color: var(--primary-success);<br /> }<br /> <br /> #bodyContent .pw-box.success a,<br /> #bodyContent .pw-box.success a:visited{<br /> color: var(--success-color) !important;<br /> }<br /> <br /> #bodyContent .mw-ui-button, #bodyContent .mw-ui-progressive{<br /> border-color: var(--primary-color) !important;<br /> color: var(--primary-color) !important;<br /> }<br /> <br /> /******* Infobox *******/<br /> .pw-infobox {<br /> background-color: var(--grey-light-1);<br /> border: 1px solid #aaa;<br /> float: right;<br /> margin: 0 0 1em 1em;<br /> width: 300px;<br /> max-width: 300px;<br /> min-width: 300px;<br /> }<br /> <br /> .pw-infobox .pw-infobox-title {<br /> padding: 1em;<br /> font-size: 1.5em;<br /> text-align: center;<br /> font-family: 'Linux Libertine','Georgia','Times',serif;<br /> font-weight:bold;<br /> background-color: var(--primary-color);<br /> color: white;<br /> }<br /> <br /> .pw-infobox .pw-infobox-content {<br /> padding: 1em;<br /> }<br /> <br /> .pw-infobox .pw-infobox-content .pw-infobox-image {<br /> text-align: center;<br /> }<br /> <br /> .pw-infobox .pw-infobox-content table {<br /> margin: inherate;<br /> }<br /> <br /> .pw-infobox .pw-infobox-content table,<br /> .pw-infobox .pw-infobox-content td,<br /> .pw-infobox .pw-infobox-content th{<br /> border: 0 !important;<br /> }<br /> <br /> .pw-infobox .pw-infobox-content tr:nth-child(odd) {<br /> background-color: transparent;<br /> }<br /> <br /> .pw-infobox .pw-infobox-content th {<br /> text-align: left;<br /> vertical-align: top;<br /> width: 130px;<br /> background-color: transparent;<br /> color: var(--primary-color);<br /> }<br /> <br /> .pw-infobox .pw-infobox-content td {<br /> vertical-align: top;<br /> }<br /> <br /> /** Power Automate **/<br /> .pw-infobox.PowerAutomate .pw-infobox-title {<br /> background-color: var(--powerautomate-primary-color);<br /> }<br /> <br /> .pw-infobox.PowerAutomate .pw-infobox-content th {<br /> color: var(--powerautomate-primary-color);<br /> }<br /> <br /> /** Power Virtual Agent **/<br /> .pw-infobox.PowerVirtualAgent .pw-infobox-title {<br /> background-color: var(--powervirtualagent-primary-color);<br /> }<br /> <br /> .pw-infobox.PowerVirtualAgent .pw-infobox-content th {<br /> color: var(--powervirtualagent-primary-color);<br /> }<br /> <br /> /** Power BI **/<br /> .pw-infobox.PowerBI .pw-infobox-title {<br /> background-color: var(--powerbi-primary-color);<br /> color:black;<br /> }<br /> <br /> .pw-infobox.PowerBI .pw-infobox-content th {<br /> color: var(--powerbi-primary-color);<br /> }<br /> <br /> /******* Delete lines between menu entries in top horizontal menu *******/<br /> .vector-menu-tabs, .vector-menu-tabs a{<br /> background:none;<br /> }<br /> <br /> /******* Cite *******/<br /> .PWCite blockquote {<br /> font-weight: 100;<br /> font-size: 2rem;<br /> max-width: 600px;<br /> line-height: 1.4;<br /> position: relative;<br /> margin: 0;<br /> padding: .5rem;<br /> }<br /> <br /> .PWCite blockquote:before,<br /> .PWCite blockquote:after {<br /> position: absolute;<br /> color: #f1efe6;<br /> font-size: 8rem;<br /> width: 4rem;<br /> height: 4rem;<br /> }<br /> <br /> .PWCite blockquote:before {<br /> content: '“';<br /> left: -5rem;<br /> top: -2rem;<br /> }<br /> <br /> .PWCite blockquote:after {<br /> content: '”';<br /> right: -5rem;<br /> bottom: 1rem;<br /> }<br /> <br /> .PWCite cite {<br /> line-height: 3;<br /> text-align: left;<br /> }<br /> <br /> /******* Advent Calendar *******/<br /> table.calendar { margin: 0; padding: 10px;}<br /> table.calendar td { margin: 0; padding: 2px; vertical-align: top;}<br /> table.calendar th { padding: 2px; text-align: center; font-size: 300%; font-weight: bold; border: none; }<br /> table.month { border: 2px solid #717d8a; }<br /> table.month .dow th { text-align: center; font-size: 150%; }<br /> table.month .heading th { text-align: center; color: #fff; background-color: #742774; font-size: 150%;}<br /> table.month td {<br /> border: none;<br /> margin: 0;<br /> padding: 1pt 1.5pt;<br /> font-weight: bold;<br /> font-size: 25pt;<br /> text-align: center;<br /> }<br /> table.month td.day-active {}<br /> table.month td.day-empty {}<br /> table.month td.today {}</div> Benedikt http://powerwiki.net/index.php?title=Structure_of_projects&diff=5285 Structure of projects 2021-12-06T22:26:17Z <p>Benedikt: </p> <hr /> <div>The folder structure of a [[Dataverse]] project is important. It should be set correctly at the beginning of a project, otherwise, a lot of moving, merging and refactoring has to be done to get an existing project to a new structure.<br /> No project is exactly like the other, still, a certain consistency and standard within a company should be established. This makes it easier for employees to move between projects and even hop into a project for just a few days to implement a small part.<br /> <br /> A possible structure could look like the following:<br /> <br /> [[File:FileStructure.png]]<br /> <br /> == Community Content ==<br /> * [https://benediktbergmann.eu/2021/04/27/folder-structure-of-a-dataverse-project/ Folder structure of a Dataverse project] by Benedikt Bergmann</div> Benedikt http://powerwiki.net/index.php?title=Structure_of_projects&diff=5284 Structure of projects 2021-12-06T22:26:04Z <p>Benedikt: </p> <hr /> <div>The folder structure of a [[Dataverse]] project is important. It should be set correctly at the beginning of a project, otherwise, a lot of moving, merging and refactoring has to be done to get an existing project to a new structure.<br /> No project is exactly like the other, still, a certain consistency and standard within a company should be established. This makes it easier for employees to move between projects and even hop into a project for just a few days to implement a small part.<br /> <br /> A possible structure could look like the following:<br /> [[File:FileStructure.png]]<br /> <br /> == Community Content ==<br /> * [https://benediktbergmann.eu/2021/04/27/folder-structure-of-a-dataverse-project/ Folder structure of a Dataverse project] by Benedikt Bergmann</div> Benedikt http://powerwiki.net/index.php?title=Structure_of_projects&diff=5283 Structure of projects 2021-12-06T22:25:34Z <p>Benedikt: </p> <hr /> <div>The folder structure of a [[Dataverse]] project is important. It should be set correctly at the beginning of a project, otherwise, a lot of moving, merging and refactoring has to be done to get an existing project to a new structure.<br /> No project is exactly like the other, still, a certain consistency and standard within a company should be established. This makes it easier for employees to move between projects and even hop into a project for just a few days to implement a small part.<br /> <br /> A possible structure could look like the following:<br /> [[File:FolderStructure.png]]<br /> <br /> == Community Content ==<br /> * [https://benediktbergmann.eu/2021/04/27/folder-structure-of-a-dataverse-project/ Folder structure of a Dataverse project] by Benedikt Bergmann</div> Benedikt http://powerwiki.net/index.php?title=File:FileStructure.png&diff=5282 File:FileStructure.png 2021-12-06T22:25:18Z <p>Benedikt: </p> <hr /> <div></div> Benedikt http://powerwiki.net/index.php?title=Template:Code&diff=5253 Template:Code 2021-12-06T15:02:35Z <p>Benedikt: </p> <hr /> <div>{{#tag:syntaxhighlight|{{{code|{{{1}}}}}}|lang={{{lang|{{{2|text}}}}}}|class={{{class|}}}|id={{{id|}}}|style={{{style|}}}|inline=1}}</div> Benedikt http://powerwiki.net/index.php?title=Structure_of_projects&diff=5252 Structure of projects 2021-12-06T15:02:28Z <p>Benedikt: </p> <hr /> <div>The folder structure of a [[Dataverse]] project is important. It should be set correctly at the beginning of a project, otherwise, a lot of moving, merging and refactoring has to be done to get an existing project to a new structure.<br /> No project is exactly like the other, still, a certain consistency and standard within a company should be established. This makes it easier for employees to move between projects and even hop into a project for just a few days to implement a small part.<br /> <br /> A possible structure could look like the following:<br /> {{code | language=text | root<br /> ├── Development<br /> <br /> │ ├── Azure<br /> <br /> │ ├── Back-end<br /> <br /> │ │ ├── Applications<br /> <br /> │ │ ├── Plugins<br /> <br /> │ │ ├── Shared<br /> <br /> │ │ ├── Workflows<br /> <br /> │ ├── Front-end<br /> <br /> │ │ ├── PCF<br /> <br /> │ │ ├── ts<br /> <br /> │ │ │ ├── src<br /> <br /> │ │ │ │ ├── code<br /> <br /> │ │ │ │ │ ├── utils<br /> <br /> │ │ │ │ │ ├── tables<br /> <br /> │ │ │ │ │ ├── ribbon<br /> <br /> │ │ │ ├── test<br /> <br /> │ │ ├── Webresources<br /> <br /> │ │ │ ├── HTML<br /> <br /> │ │ │ ├── CSS<br /> <br /> │ │ │ ├── images<br /> <br /> │ │ │ ├── js<br /> <br /> │ ├── spkl<br /> <br /> ├── PowerPlatform<br /> <br /> │ ├── CanvasApps<br /> <br /> │ ├── Config<br /> <br /> │ │ ├── Schema<br /> <br /> │ │ ├── Data<br /> <br /> │ ├── Solutions<br /> <br /> │ ├── (Tools)<br /> <br /> ├── Pipelines}}<br /> <br /> <br /> == Community Content ==<br /> * [https://benediktbergmann.eu/2021/04/27/folder-structure-of-a-dataverse-project/ Folder structure of a Dataverse project] by Benedikt Bergmann</div> Benedikt http://powerwiki.net/index.php?title=Template:Code&diff=5251 Template:Code 2021-12-06T15:00:56Z <p>Benedikt: Created page with &quot;{{#if:{{{inline|}}}|&lt;code {{#if:{{{class|}}}|class=&quot;{{{class}}}&quot;}} {{#if:{{{id|}}}|id=&quot;{{{id}}}&quot;}} {{#if:{{{style|}}}|style=&quot;{{{style}}}&quot;}}&gt;{{#tag:syntaxhighlight|{{{code|{{{1...&quot;</p> <hr /> <div>{{#if:{{{inline|}}}|&lt;code {{#if:{{{class|}}}|class=&quot;{{{class}}}&quot;}} {{#if:{{{id|}}}|id=&quot;{{{id}}}&quot;}} {{#if:{{{style|}}}|style=&quot;{{{style}}}&quot;}}&gt;{{#tag:syntaxhighlight|{{{code|{{{1}}}}}}|lang=&quot;{{{lang|{{{2|text}}}}}}&quot;|inline=true}}&lt;/code&gt;|{{#if:{{{header|}}}|&lt;u&gt;&lt;small&gt;{{{header}}}&lt;/small&gt;&lt;/u&gt;}}{{#tag:syntaxhighlight<br /> |{{{code|{{{1}}}}}}<br /> |lang={{{lang|{{{2|bash}}}}}}<br /> }}}}</div> Benedikt http://powerwiki.net/index.php?title=Structure_of_projects&diff=5250 Structure of projects 2021-12-06T15:00:06Z <p>Benedikt: </p> <hr /> <div>The folder structure of a [[Dataverse]] project is important. It should be set correctly at the beginning of a project, otherwise, a lot of moving, merging and refactoring has to be done to get an existing project to a new structure.<br /> No project is exactly like the other, still, a certain consistency and standard within a company should be established. This makes it easier for employees to move between projects and even hop into a project for just a few days to implement a small part.<br /> <br /> A possible structure could look like the following:<br /> {{code | language=text | &quot;root<br /> ├── Development<br /> <br /> │ ├── Azure<br /> <br /> │ ├── Back-end<br /> <br /> │ │ ├── Applications<br /> <br /> │ │ ├── Plugins<br /> <br /> │ │ ├── Shared<br /> <br /> │ │ ├── Workflows<br /> <br /> │ ├── Front-end<br /> <br /> │ │ ├── PCF<br /> <br /> │ │ ├── ts<br /> <br /> │ │ │ ├── src<br /> <br /> │ │ │ │ ├── code<br /> <br /> │ │ │ │ │ ├── utils<br /> <br /> │ │ │ │ │ ├── tables<br /> <br /> │ │ │ │ │ ├── ribbon<br /> <br /> │ │ │ ├── test<br /> <br /> │ │ ├── Webresources<br /> <br /> │ │ │ ├── HTML<br /> <br /> │ │ │ ├── CSS<br /> <br /> │ │ │ ├── images<br /> <br /> │ │ │ ├── js<br /> <br /> │ ├── spkl<br /> <br /> ├── PowerPlatform<br /> <br /> │ ├── CanvasApps<br /> <br /> │ ├── Config<br /> <br /> │ │ ├── Schema<br /> <br /> │ │ ├── Data<br /> <br /> │ ├── Solutions<br /> <br /> │ ├── (Tools)<br /> <br /> ├── Pipelines&quot;}}<br /> <br /> <br /> == Community Content ==<br /> * [https://benediktbergmann.eu/2021/04/27/folder-structure-of-a-dataverse-project/ Folder structure of a Dataverse project] by Benedikt Bergmann</div> Benedikt http://powerwiki.net/index.php?title=Structure_of_projects&diff=5249 Structure of projects 2021-12-06T14:58:52Z <p>Benedikt: </p> <hr /> <div>The folder structure of a [[Dataverse]] project is important. It should be set correctly at the beginning of a project, otherwise, a lot of moving, merging and refactoring has to be done to get an existing project to a new structure.<br /> No project is exactly like the other, still, a certain consistency and standard within a company should be established. This makes it easier for employees to move between projects and even hop into a project for just a few days to implement a small part.<br /> <br /> A possible structure could look like the following:<br /> {{code |<br /> root<br /> ├── Development<br /> <br /> │ ├── Azure<br /> <br /> │ ├── Back-end<br /> <br /> │ │ ├── Applications<br /> <br /> │ │ ├── Plugins<br /> <br /> │ │ ├── Shared<br /> <br /> │ │ ├── Workflows<br /> <br /> │ ├── Front-end<br /> <br /> │ │ ├── PCF<br /> <br /> │ │ ├── ts<br /> <br /> │ │ │ ├── src<br /> <br /> │ │ │ │ ├── code<br /> <br /> │ │ │ │ │ ├── utils<br /> <br /> │ │ │ │ │ ├── tables<br /> <br /> │ │ │ │ │ ├── ribbon<br /> <br /> │ │ │ ├── test<br /> <br /> │ │ ├── Webresources<br /> <br /> │ │ │ ├── HTML<br /> <br /> │ │ │ ├── CSS<br /> <br /> │ │ │ ├── images<br /> <br /> │ │ │ ├── js<br /> <br /> │ ├── spkl<br /> <br /> ├── PowerPlatform<br /> <br /> │ ├── CanvasApps<br /> <br /> │ ├── Config<br /> <br /> │ │ ├── Schema<br /> <br /> │ │ ├── Data<br /> <br /> │ ├── Solutions<br /> <br /> │ ├── (Tools)<br /> <br /> ├── Pipelines<br /> }}<br /> <br /> <br /> == Community Content ==<br /> * [https://benediktbergmann.eu/2021/04/27/folder-structure-of-a-dataverse-project/ Folder structure of a Dataverse project] by Benedikt Bergmann</div> Benedikt http://powerwiki.net/index.php?title=Structure_of_projects&diff=5248 Structure of projects 2021-12-06T14:58:42Z <p>Benedikt: </p> <hr /> <div>The folder structure of a [[Dataverse]] project is important. It should be set correctly at the beginning of a project, otherwise, a lot of moving, merging and refactoring has to be done to get an existing project to a new structure.<br /> No project is exactly like the other, still, a certain consistency and standard within a company should be established. This makes it easier for employees to move between projects and even hop into a project for just a few days to implement a small part.<br /> <br /> A possible structure could look like the following:<br /> {{code<br /> root<br /> ├── Development<br /> <br /> │ ├── Azure<br /> <br /> │ ├── Back-end<br /> <br /> │ │ ├── Applications<br /> <br /> │ │ ├── Plugins<br /> <br /> │ │ ├── Shared<br /> <br /> │ │ ├── Workflows<br /> <br /> │ ├── Front-end<br /> <br /> │ │ ├── PCF<br /> <br /> │ │ ├── ts<br /> <br /> │ │ │ ├── src<br /> <br /> │ │ │ │ ├── code<br /> <br /> │ │ │ │ │ ├── utils<br /> <br /> │ │ │ │ │ ├── tables<br /> <br /> │ │ │ │ │ ├── ribbon<br /> <br /> │ │ │ ├── test<br /> <br /> │ │ ├── Webresources<br /> <br /> │ │ │ ├── HTML<br /> <br /> │ │ │ ├── CSS<br /> <br /> │ │ │ ├── images<br /> <br /> │ │ │ ├── js<br /> <br /> │ ├── spkl<br /> <br /> ├── PowerPlatform<br /> <br /> │ ├── CanvasApps<br /> <br /> │ ├── Config<br /> <br /> │ │ ├── Schema<br /> <br /> │ │ ├── Data<br /> <br /> │ ├── Solutions<br /> <br /> │ ├── (Tools)<br /> <br /> ├── Pipelines<br /> }}<br /> <br /> <br /> == Community Content ==<br /> * [https://benediktbergmann.eu/2021/04/27/folder-structure-of-a-dataverse-project/ Folder structure of a Dataverse project] by Benedikt Bergmann</div> Benedikt http://powerwiki.net/index.php?title=Structure_of_projects&diff=5247 Structure of projects 2021-12-06T14:54:47Z <p>Benedikt: </p> <hr /> <div>The folder structure of a [[Dataverse]] project is important. It should be set correctly at the beginning of a project, otherwise, a lot of moving, merging and refactoring has to be done to get an existing project to a new structure.<br /> No project is exactly like the other, still, a certain consistency and standard within a company should be established. This makes it easier for employees to move between projects and even hop into a project for just a few days to implement a small part.<br /> <br /> A possible structure could look like the following:<br /> root<br /> ├── Development<br /> <br /> │ ├── Azure<br /> <br /> │ ├── Back-end<br /> <br /> │ │ ├── Applications<br /> <br /> │ │ ├── Plugins<br /> <br /> │ │ ├── Shared<br /> <br /> │ │ ├── Workflows<br /> <br /> │ ├── Front-end<br /> <br /> │ │ ├── PCF<br /> <br /> │ │ ├── ts<br /> <br /> │ │ │ ├── src<br /> <br /> │ │ │ │ ├── code<br /> <br /> │ │ │ │ │ ├── utils<br /> <br /> │ │ │ │ │ ├── tables<br /> <br /> │ │ │ │ │ ├── ribbon<br /> <br /> │ │ │ ├── test<br /> <br /> │ │ ├── Webresources<br /> <br /> │ │ │ ├── HTML<br /> <br /> │ │ │ ├── CSS<br /> <br /> │ │ │ ├── images<br /> <br /> │ │ │ ├── js<br /> <br /> │ ├── spkl<br /> <br /> ├── PowerPlatform<br /> <br /> │ ├── CanvasApps<br /> <br /> │ ├── Config<br /> <br /> │ │ ├── Schema<br /> <br /> │ │ ├── Data<br /> <br /> │ ├── Solutions<br /> <br /> │ ├── (Tools)<br /> <br /> ├── Pipelines<br /> <br /> <br /> == Community Content ==<br /> * [https://benediktbergmann.eu/2021/04/27/folder-structure-of-a-dataverse-project/ Folder structure of a Dataverse project] by Benedikt Bergmann</div> Benedikt http://powerwiki.net/index.php?title=Structure_of_projects&diff=5246 Structure of projects 2021-12-06T14:54:00Z <p>Benedikt: Created page with &quot;The folder structure of a Dataverse project is important. It should be set correctly at the beginning of a project, otherwise, a lot of moving, merging and refactoring has...&quot;</p> <hr /> <div>The folder structure of a [[Dataverse]] project is important. It should be set correctly at the beginning of a project, otherwise, a lot of moving, merging and refactoring has to be done to get an existing project to a new structure.<br /> No project is exactly like the other, still, a certain consistency and standard within a company should be established. This makes it easier for employees to move between projects and even hop into a project for just a few days to implement a small part.<br /> <br /> A possible structure could look like the following:<br /> root<br /> ├── Development<br /> │ ├── Azure<br /> │ ├── Back-end<br /> │ │ ├── Applications<br /> │ │ ├── Plugins<br /> │ │ ├── Shared<br /> │ │ ├── Workflows<br /> │ ├── Front-end<br /> │ │ ├── PCF<br /> │ │ ├── ts<br /> │ │ │ ├── src<br /> │ │ │ │ ├── code<br /> │ │ │ │ │ ├── utils<br /> │ │ │ │ │ ├── tables<br /> │ │ │ │ │ ├── ribbon<br /> │ │ │ ├── test<br /> │ │ ├── Webresources<br /> │ │ │ ├── html<br /> │ │ │ ├── css<br /> │ │ │ ├── images<br /> │ │ │ ├── js<br /> │ ├── spkl<br /> ├── PowerPlatform<br /> │ ├── CanvasApps<br /> │ ├── Config<br /> │ │ ├── Schema<br /> │ │ ├── Data<br /> │ ├── Solutions<br /> │ ├── (Tools)<br /> ├── Pipelines<br /> <br /> == Community Content ==<br /> * [https://benediktbergmann.eu/2021/04/27/folder-structure-of-a-dataverse-project/ Folder structure of a Dataverse project] by Benedikt Bergmann</div> Benedikt http://powerwiki.net/index.php?title=TypeScript&diff=5245 TypeScript 2021-12-06T14:49:24Z <p>Benedikt: </p> <hr /> <div>[https://www.typescriptlang.org TypeScript] is a superset of JavaScript. It is strongly typed and makes development much easier.<br /> <br /> == Strongly typed ==<br /> <br /> Since TypeScript is strongly typed the job of writing it gets a lot easier. If you use a proper IDE (Visual Studio Code for example) it will show you type errors while developing.<br /> <br /> == Backward compatibility ==<br /> <br /> In the end, TypeScript has to be transpiled/compiled to JavaScript. This could, for example, be done via the “tsc” command, which will transpile the TS file to the configured target ECMAScript version (ECMAScript is a standard to define JavaScript. You can read more about that here as well as about the browser support here). With the ability to target different/older versions of the standard the TS will get automatically transpiled into a JS file that is compatible with older browser versions. This means one can write readable code without thinking about compatibility. When transpiled it gets something that is compatible. Of course, it’s not always that easy. In the screenshot below you can see a part of our transpiled demo file.<br /> <br /> == Tests &amp; Debugging ==<br /> <br /> With TypeScript it is much easier to create tests that could be run automatically in a pipeline. Another big plus is that it is possible to debug the code with the help of source map files.<br /> <br /> == Community Content ==<br /> * [https://learn.develop1.net/courses/building-javascript-web-resources-using-typescript Free Course on TypeSCript] by Scott Durow<br /> * [https://develop1.net/public/post/2018/06/09/Lets-start-TypeScript-Part-1 Let’s start TypeScript – Part 1] by Scott Durow<br /> * [https://www.oliverflint.co.uk/2020/03/07/D365-Typescript-Webresources-Part-1/ D365 TypeScript Web Resources - Part 1 - Basics] by Oliver Flint<br /> * [https://benediktbergmann.eu/2020/11/01/how-to-call-xrm-webapi-using-typescript/ Setting up a TypeScript project for Dataverse] by Benedikt Bergmann</div> Benedikt http://powerwiki.net/index.php?title=TypeScript&diff=5244 TypeScript 2021-12-06T14:49:13Z <p>Benedikt: Created page with &quot;[https://www.typescriptlang.org TypeScript] is a superset of JavaScript. It is strongly typed and makes development much easier. == Strongly typed == Since TypeScript is str...&quot;</p> <hr /> <div>[https://www.typescriptlang.org TypeScript] is a superset of JavaScript. It is strongly typed and makes development much easier.<br /> <br /> == Strongly typed ==<br /> <br /> Since TypeScript is strongly typed the job of writing it gets a lot easier. If you use a proper IDE (Visual Studio Code for example) it will show you type errors while developing.<br /> <br /> == Backward compatibility ==<br /> <br /> In the end, TypeScript has to be transpiled/compiled to JavaScript. This could, for example, be done via the “tsc” command, which will transpile the TS file to the configured target ECMAScript version (ECMAScript is a standard to define JavaScript. You can read more about that here as well as about the browser support here). With the ability to target different/older versions of the standard the TS will get automatically transpiled into a JS file that is compatible with older browser versions. This means one can write readable code without thinking about compatibility. When transpiled it gets something that is compatible. Of course, it’s not always that easy. In the screenshot below you can see a part of our transpiled demo file.<br /> <br /> <br /> == Tests &amp; Debugging ==<br /> <br /> With TypeScript it is much easier to create tests that could be run automatically in a pipeline. Another big plus is that it is possible to debug the code with the help of source map files.<br /> <br /> == Community Content ==<br /> * [https://learn.develop1.net/courses/building-javascript-web-resources-using-typescript Free Course on TypeSCript] by Scott Durow<br /> * [https://develop1.net/public/post/2018/06/09/Lets-start-TypeScript-Part-1 Let’s start TypeScript – Part 1] by Scott Durow<br /> * [https://www.oliverflint.co.uk/2020/03/07/D365-Typescript-Webresources-Part-1/ D365 TypeScript Web Resources - Part 1 - Basics] by Oliver Flint<br /> * [https://benediktbergmann.eu/2020/11/01/how-to-call-xrm-webapi-using-typescript/ Setting up a TypeScript project for Dataverse] by Benedikt Bergmann</div> Benedikt http://powerwiki.net/index.php?title=Application_Lifecycle_Management&diff=5243 Application Lifecycle Management 2021-12-06T14:41:05Z <p>Benedikt: </p> <hr /> <div>Application lifecycle management is the lifecycle management of applications and includes governance, development and maintenance. For everyone working with [[Power Platform]] ALM includes setting up [[environment]] strategies, managing [[Solutions]], automating deployment e.g. with [[pipelines]] in DevOps etc. Related to this is the [[Center of Excellence]] (CoE) Starter Kit which is a set of templates provided by Microsoft which you can use in order to set up your own Center of Excellence. <br /> <br /> == Basic Process ==<br /> A basic ALM process could contain the following 3 pipelines<br /> <br /> === Create Export from DEV ===<br /> This build pipeline would:<br /> * Export the solution from DEV<br /> * Do some Quality Gates (for example run solution Checker)<br /> * Unpack the solution<br /> * Check it into source control<br /> <br /> It could also handle stuff like:<br /> * Set correct version<br /> * Deploy code components (JS, Plugins, PCFs, ...) before exporting<br /> * ... <br /> <br /> === Build Managed Solution ===<br /> The second build pipeline would create a managed solution from the repository and publish it as an artefact.<br /> <br /> {{<br /> PWBoxInfo<br /> | title = Run in one<br /> | text = The first two pipelines could also be run in one. <br /> }}<br /> {{<br /> PWBoxWarning<br /> | title = JIT-Build Environment<br /> | text = There might be problems with creating a JIT-Build Environment on the fly. See the post in Community Resources which contains more information on that.<br /> }}<br /> <br /> === Deploy to Downstream environments === <br /> The last part of a basic process would be a Release Pipeline to deploy the created artefact to the downstream environments.<br /> <br /> == Microsoft Resources == <br /> <br /> * [https://docs.microsoft.com/power-platform/alm/?WT.mc_id=DX-MVP-5003780 Application lifecycle management (ALM) with Microsoft Power Platform]<br /> * [https://powerapps.microsoft.com/en-us/blog/key-alm-updates/ ALM Key Updates - March 2021]<br /> <br /> == Community Resources ==<br /> * [https://github.com/rpothin/PowerPlatform-ALM-Learning-Resources PowerPlatform-ALM-Learning-Resources] GitHub repository gathering ALM resources<br /> * [https://github.com/Power-Platform-DevOps/Power-Platform-ALM-Starter-Kit Power Platform ALM Starter Kit]<br /> * [https://benediktbergmann.eu/2020/02/10/cds-basic-alm-process/ CDS - Basic ALM Process] by Benedikt Bergmann<br /> <br /> == External Resources ==<br /> * [https://en.wikipedia.org/wiki/Application_lifecycle_management ALM on Wikipedia]<br /> <br /> [[Category: ALM]]</div> Benedikt http://powerwiki.net/index.php?title=Application_Lifecycle_Management&diff=5242 Application Lifecycle Management 2021-12-06T14:40:18Z <p>Benedikt: </p> <hr /> <div>Application lifecycle management is the lifecycle management of applications and includes governance, development and maintenance. For everyone working with [[Power Platform]] ALM includes setting up [[environment]] strategies, managing [[Solutions]], automating deployment e.g. with [[pipelines]] in DevOps etc. Related to this is the [[Center of Excellence]] (CoE) Starter Kit which is a set of templates provided by Microsoft which you can use in order to set up your own Center of Excellence. <br /> <br /> == Basic Process ==<br /> A basic ALM process could contain the following 3 pipelines<br /> <br /> === Create Export from DEV ===<br /> This build pipeline would:<br /> * Export the solution from DEV<br /> * Do some Quality Gates (for example run solution Checker)<br /> * Unpack the solution<br /> * Check it into source control<br /> <br /> It could also handle stuff like:<br /> * Set correct version<br /> * Deploy code components (JS, Plugins, PCFs, ...) before exporting<br /> * ... <br /> <br /> === Build Managed Solution ===<br /> The second build pipeline would create a managed solution from the repository and publish it as an artefact.<br /> <br /> {{<br /> PWBoxInformation<br /> | title = Run in one<br /> | text = The first two pipelines could also be run in one. <br /> }}<br /> {{<br /> PWBoxWarning<br /> | title = JIT-Build Environment<br /> | text = There might be problems with creating a JIT-Build Environment on the fly. See the post in Community Resources which contains more information on that.<br /> }}<br /> <br /> === Deploy to Downstream environments === <br /> The last part of a basic process would be a Release Pipeline to deploy the created artefact to the downstream environments.<br /> <br /> == Microsoft Resources == <br /> <br /> * [https://docs.microsoft.com/power-platform/alm/?WT.mc_id=DX-MVP-5003780 Application lifecycle management (ALM) with Microsoft Power Platform]<br /> * [https://powerapps.microsoft.com/en-us/blog/key-alm-updates/ ALM Key Updates - March 2021]<br /> <br /> == Community Resources ==<br /> * [https://github.com/rpothin/PowerPlatform-ALM-Learning-Resources PowerPlatform-ALM-Learning-Resources] GitHub repository gathering ALM resources<br /> * [https://github.com/Power-Platform-DevOps/Power-Platform-ALM-Starter-Kit Power Platform ALM Starter Kit]<br /> * [https://benediktbergmann.eu/2020/02/10/cds-basic-alm-process/ CDS - Basic ALM Process] by Benedikt Bergmann<br /> <br /> == External Resources ==<br /> * [https://en.wikipedia.org/wiki/Application_lifecycle_management ALM on Wikipedia]<br /> <br /> [[Category: ALM]]</div> Benedikt http://powerwiki.net/index.php?title=Pipelines&diff=5241 Pipelines 2021-12-06T14:34:28Z <p>Benedikt: </p> <hr /> <div>Pipelines are a way of automatic how different components are deployed to the downstream [[environment]]s.<br /> Both Azure DevOps and GitHub (where they are called Actions) provide the functionality of pipelines to achieve higher automation within a given project.<br /> <br /> == Types ==<br /> There are 2 different types of Pipelines within Azure DevOps:<br /> <br /> === Build Pipelines (aka Pipelines) ===<br /> Build pipelines are used to build your source code and create/package releasable artefacts.<br /> Another use case for Build pipelines would be to test your code before a Pull Request is allowed to be merged (as a Quality Gate). See Community Resources for more information.<br /> <br /> === Release Pipelines (aka Release) ===<br /> A Release Pipeline takes artefacts, created by a build(s) pipeline, and deploys them to the downstream [[environment]]s.<br /> <br /> == Triggers ==<br /> Pipelines could be started with various triggers or on various occasions. Some examples are:<br /> * Manual<br /> * Scheduled<br /> * When a preceding pipeline is ready<br /> * When different events happen in Azure DevOps or other applications<br /> ** Pull Request gets merged<br /> ** Commit to repo<br /> <br /> == Components ==<br /> Within a pipeline one could basically deploy any component they desire (as long as Azure DevOps can reach the destination).<br /> In most Power Platform projects those are<br /> * Dynamics 365/Power Platform Solution<br /> * Azure Components<br /> ** Azure functions<br /> ** Logic Apps<br /> ** Web Jobs<br /> ** and more<br /> <br /> <br /> == Community Resources ==<br /> See the [[ALM]] page for a list of community resources on this topic.<br /> * [https://benediktbergmann.eu/2020/06/14/quality-gates-for-check-ins/ Quality Gate for check-ins] by Benedikt Bergmann<br /> <br /> [[Category: ALM]]</div> Benedikt http://powerwiki.net/index.php?title=Application_Lifecycle_Management&diff=5240 Application Lifecycle Management 2021-12-06T14:21:58Z <p>Benedikt: </p> <hr /> <div>Application lifecycle management is the lifecycle management of applications and includes governance, development and maintenance. For everyone working with [[Power Platform]] ALM includes setting up [[environment]] strategies, managing [[Solutions]], automating deployment e.g. with [[pipelines]] in DevOps etc. Related to this is the [[Center of Excellence]] (CoE) Starter Kit which is a set of templates provided by Microsoft which you can use in order to set up your own Center of Excellence. <br /> <br /> == Microsoft Resources == <br /> <br /> * [https://docs.microsoft.com/power-platform/alm/?WT.mc_id=DX-MVP-5003780 Application lifecycle management (ALM) with Microsoft Power Platform]<br /> * [https://powerapps.microsoft.com/en-us/blog/key-alm-updates/ ALM Key Updates - March 2021]<br /> <br /> == Community Resources ==<br /> * [https://github.com/rpothin/PowerPlatform-ALM-Learning-Resources PowerPlatform-ALM-Learning-Resources] GitHub repository gathering ALM resources<br /> * [https://github.com/Power-Platform-DevOps/Power-Platform-ALM-Starter-Kit Power Platform ALM Starter Kit]<br /> * [https://benediktbergmann.eu/2020/02/10/cds-basic-alm-process/ CDS - Basic ALM Process] by Benedikt Bergmann<br /> <br /> == External Resources ==<br /> * [https://en.wikipedia.org/wiki/Application_lifecycle_management ALM on Wikipedia]<br /> <br /> [[Category: ALM]]</div> Benedikt http://powerwiki.net/index.php?title=Application_Lifecycle_Management&diff=5239 Application Lifecycle Management 2021-12-06T14:20:29Z <p>Benedikt: </p> <hr /> <div>Application lifecycle management is the lifecycle management of applications and includes governance, development and maintenance. For everyone working with [[Power Platform]] ALM includes setting up [[environment]] strategies, managing [[Solutions]], automating deployment e.g. with [[pipelines]] in DevOps etc. Related to this is the [[Center of Excellence]] (CoE) Starter Kit which is a set of templates provided by Microsoft which you can use in order to set up your own Center of Excellence. <br /> <br /> == Microsoft Resources == <br /> <br /> * [https://docs.microsoft.com/power-platform/alm/?WT.mc_id=DX-MVP-5003780 Application lifecycle management (ALM) with Microsoft Power Platform]<br /> * [https://powerapps.microsoft.com/en-us/blog/key-alm-updates/ ALM Key Updates - March 2021]<br /> <br /> == Community Resources ==<br /> * [https://github.com/rpothin/PowerPlatform-ALM-Learning-Resources PowerPlatform-ALM-Learning-Resources] GitHub repository gathering ALM resources<br /> * [https://github.com/Power-Platform-DevOps/Power-Platform-ALM-Starter-Kit Power Platform ALM Starter Kit]<br /> * [https://benediktbergmann.eu/2020/02/10/cds-basic-alm-process/ CDS - Basic ALM Process] by Benedikt Bergmann<br /> == External Resources ==<br /> * [https://en.wikipedia.org/wiki/Application_lifecycle_management ALM on Wikipedia]<br /> <br /> [[Category: ALM]]</div> Benedikt http://powerwiki.net/index.php?title=Application_Lifecycle_Management&diff=5238 Application Lifecycle Management 2021-12-06T14:19:56Z <p>Benedikt: </p> <hr /> <div>Application lifecycle management is the lifecycle management of applications and includes governance, development and maintenance. For everyone working with [[Power Platform]] ALM includes setting up [[environment]] strategies, managing [[Solutions]], automating deployment e.g. with pipelines in DevOps etc. Related to this is the [[Center of Excellence]] (CoE) Starter Kit which is a set of templates provided by Microsoft which you can use in order to set up your own Center of Excellence. <br /> <br /> == Microsoft Resources == <br /> <br /> * [https://docs.microsoft.com/power-platform/alm/?WT.mc_id=DX-MVP-5003780 Application lifecycle management (ALM) with Microsoft Power Platform]<br /> * [https://powerapps.microsoft.com/en-us/blog/key-alm-updates/ ALM Key Updates - March 2021]<br /> <br /> == Community Resources ==<br /> * [https://github.com/rpothin/PowerPlatform-ALM-Learning-Resources PowerPlatform-ALM-Learning-Resources] GitHub repository gathering ALM resources<br /> * [https://github.com/Power-Platform-DevOps/Power-Platform-ALM-Starter-Kit Power Platform ALM Starter Kit]<br /> * [https://benediktbergmann.eu/2020/02/10/cds-basic-alm-process/ CDS - Basic ALM Process] by Benedikt Bergmann<br /> == External Resources ==<br /> * [https://en.wikipedia.org/wiki/Application_lifecycle_management ALM on Wikipedia]<br /> <br /> [[Category: ALM]]</div> Benedikt http://powerwiki.net/index.php?title=Power_Fx&diff=4922 Power Fx 2021-11-29T22:03:03Z <p>Benedikt: </p> <hr /> <div>{{Infobox features<br /> |title = Power Fx<br /> |usecases = Create logic for different parts of Power Platform (Canvas apps today, in the future also for other parts of Power Platform)<br /> |publicpreview = <br /> |generalavailability = <br /> |msdocs = [https://docs.microsoft.com/en-us/power-platform/power-fx/overview/?WT.mc_id=DX-MVP-5003780 Power Fx Startpage]<br /> |mslearn = <br /> }}<br /> <br /> Microsoft Power Fx is the low code language for expressing logic across [[Power Platform]]. <br /> <br /> It is open source and is found on GitHub: [https://github.com/microsoft/Power-Fx https://github.com/microsoft/Power-Fx] <br /> <br /> == History ==<br /> These expressions have been used within [[Power Apps]] [[canvas apps]]. During Microsoft Ignite March 2021 these expressions got a name Power Fx. Power Fx was announced as a new language and a roadmap describing how Power Fx will be used in other parts of Power Platform in the future was presented. <br /> <br /> == Community Resources ==<br /> * [https://forwardforever.com/why-does-low-code-need-a-programming-language-like-power-fx/ Why does low-code need a programming language like Power Fx?] by Jukka Niiranen<br /> * [https://github.com/rajyraman/Power-Fx-.NET-Interactive PowerFx Kernel for .Net interactive notebook] by Natraj Yegnaraman<br /> <br /> == Microsoft Resources ==<br /> * [https://powerapps.microsoft.com/en-us/blog/what-is-microsoft-power-fx/ What is Power Fx?] Power Apps blog 2021-03-02<br /> * [https://powerapps.microsoft.com/en-us/blog/introducing-microsoft-power-fx-the-low-code-programming-language-for-everyone/ Introducing Microsoft Power Fx: the low-code programming language for everyone] Power Apps blog 2021-03-02<br /> * [https://docs.microsoft.com/en-us/power-platform/power-fx/overview/?WT.mc_id=DX-MVP-5003780 Power Fx in MS Docs]<br /> * [https://github.com/microsoft/Power-Fx Power Fx on GitHub]<br /> * [https://www.youtube.com/watch?v=1VcinGBJqmM Power Fx with Greg Lindhorst] (VIDEO)</div> Benedikt http://powerwiki.net/index.php?title=Power_Fx&diff=4921 Power Fx 2021-11-29T22:02:03Z <p>Benedikt: </p> <hr /> <div>{{Infobox features<br /> |title = Power Fx<br /> |usecases = Create logic for different parts of Power Platform (Canvas apps today, in the future also for other parts of Power Platform)<br /> |publicpreview = <br /> |generalavailability = <br /> |msdocs = [https://docs.microsoft.com/en-us/power-platform/power-fx/overview/?WT.mc_id=DX-MVP-5003780 Power Fx Startpage]<br /> |mslearn = <br /> }}<br /> <br /> Microsoft Power Fx is the low code language for expressing logic across [[Power Platform]]. <br /> <br /> It is open source and is found on GitHub: [https://github.com/microsoft/Power-Fx https://github.com/microsoft/Power-Fx] <br /> <br /> == History ==<br /> These expressions have been used within [[Power Apps]] [[canvas apps]]. During Microsoft Ignite March 2021 these expressions got a name Power Fx. Power Fx was announced as a new language and a roadmap describing how Power Fx will be used in other parts of Power Platform in the future was presented. <br /> <br /> == Community Resources ==<br /> [https://forwardforever.com/why-does-low-code-need-a-programming-language-like-power-fx/ Why does low-code need a programming language like Power Fx?] by Jukka Niiranen<br /> [https://github.com/rajyraman/Power-Fx-.NET-Interactive] by Natraj Yegnaraman<br /> <br /> == Microsoft Resources ==<br /> * [https://powerapps.microsoft.com/en-us/blog/what-is-microsoft-power-fx/ What is Power Fx?] Power Apps blog 2021-03-02<br /> * [https://powerapps.microsoft.com/en-us/blog/introducing-microsoft-power-fx-the-low-code-programming-language-for-everyone/ Introducing Microsoft Power Fx: the low-code programming language for everyone] Power Apps blog 2021-03-02<br /> * [https://docs.microsoft.com/en-us/power-platform/power-fx/overview/?WT.mc_id=DX-MVP-5003780 Power Fx in MS Docs]<br /> * [https://github.com/microsoft/Power-Fx Power Fx on GitHub]<br /> * [https://www.youtube.com/watch?v=1VcinGBJqmM Power Fx with Greg Lindhorst] (VIDEO)</div> Benedikt http://powerwiki.net/index.php?title=MediaWiki:Common.css&diff=4554 MediaWiki:Common.css 2021-03-05T08:15:01Z <p>Benedikt: </p> <hr /> <div>/* For the Top banner on Start Page */<br /> <br /> #pw-bottombanner {<br /> clear: both;<br /> position: relative;<br /> box-sizing: border-box;<br /> width: 100%;<br /> margin-top: 0em;<br /> min-width: 47em;<br /> border-color: #ddd;<br /> background-color: #f9f9f9;<br /> white-space: nowrap;<br /> }<br /> <br /> #mp-topbanner {<br /> clear: both;<br /> position: relative;<br /> box-sizing: border-box;<br /> width: 100%;<br /> margin-top: 1.2em;<br /> margin-bottom: 0em;<br /> min-width: 47em;<br /> border-color: #ddd;<br /> background-color: #f9f9f9;<br /> white-space: nowrap;<br /> }<br /> <br /> .mp-bordered,<br /> .pw-bordered,<br /> .mp-h2,<br /> body.skin-timeless .mp-h2 { /* Timeless needs a higher specificity */<br /> border-width: 1px;<br /> border-style: solid;<br /> }<br /> <br /> #mp-topbanner,<br /> .mp-h2,<br /> #mp-left {<br /> color: #000;<br /> }<br /> <br /> #mp-welcomecount {<br /> margin: 0.4em;<br /> width: 22em;<br /> text-align: center;<br /> }<br /> <br /> #mp-welcome {<br /> font-size: 162%;<br /> padding: 0.1em;<br /> }<br /> <br /> #mp-free {<br /> font-size: 95%;<br /> }<br /> <br /> #articlecount {<br /> font-size: 85%;<br /> }<br /> <br /> #mp-portals {<br /> position: absolute;<br /> right: -1em;<br /> top: 50%;<br /> margin-top: -2.4em;<br /> width: 38%;<br /> min-width: 25em;<br /> font-size: 95%;<br /> }<br /> <br /> #mp-portals li {<br /> position: absolute;<br /> left: 0;<br /> top: 0;<br /> }<br /> <br /> #mp-portals .portal-hmid {<br /> left: 33%;<br /> }<br /> <br /> #mp-portals .portal-hright {<br /> left: 66%;<br /> }<br /> <br /> #mp-portals .portal-vmid {<br /> top: 1.6em;<br /> }<br /> <br /> #mp-portals .portal-vbot {<br /> top: 3.2em;<br /> }<br /> <br /> .portal-hright.portal-vbot {<br /> font-weight: bold;<br /> }<br /> <br /> #mp-banner {<br /> margin-top: 4px;<br /> padding: 0.5em;<br /> background-color: #fffaf5;<br /> border-color: #f2e0ce;<br /> }<br /> <br /> .mp-h2,<br /> body.skin-timeless .mp-h2 { /* Timeless needs a higher specificity */<br /> margin: 0.5em;<br /> padding: 0.2em 0.4em;<br /> font-size: 120%;<br /> font-weight: bold;<br /> font-family: inherit;<br /> }<br /> <br /> h2.mp-h2::after { /* Remove borders in Timeless */ <br /> border: none;<br /> }<br /> <br /> .mp-later {<br /> font-size: 85%;<br /> font-weight: normal;<br /> }<br /> <br /> /* End of Top banner on Start Page */<br /> <br /> /* For the rest of the Start Page */<br /> <br /> .mainpage_row {<br /> display: flex;<br /> flex-direction: row;<br /> flex-flow: row wrap;<br /> justify-content: space-between;<br /> padding: 0;<br /> margin: 0 -5px 0 -5px;<br /> }<br /> .mainpage_box {<br /> flex: 1;<br /> margin: 5px;<br /> min-width: 210px;<br /> border: 1px solid #CCC;<br /> padding: 0 10px 10px 10px;<br /> box-shadow: 0 2px 2px rgba(0,0,0,0.1);<br /> }<br /> .mainpage_box h3 {<br /> /* Reset padding so is equal across skins */<br /> padding: 0;<br /> margin: 0.5em 0;<br /> <br /> }<br /> .mainpage_box h3 .header_icon {<br /> float: left;<br /> margin-right: 5px;<br /> <br /> }<br /> .mainpage_box .items {<br /> border-top: 1px solid #CCC;<br /> padding-top: 0.5em;<br /> }<br /> .mainpage_box p:last-child {<br /> margin-bottom: 0;<br /> }<br /> .mainpage_boxcontents_small {<br /> font-size: 95%;<br /> }<br /> <br /> @media screen and (max-width: 719px) {<br /> .thumb {<br /> float: none;<br /> }<br /> .thumb, .thumbinner {<br /> margin-left: auto;<br /> margin-right: auto;<br /> }<br /> }<br /> <br /> .pw-ui-button, .pw-ui-progressive {<br /> border-radius: 4px !important;<br /> border: 1px solid #40798C !important;<br /> color: #40798C !important;<br /> background: #fff !important;<br /> text-shadow: 0px 0px 0px;<br /> }<br /> <br /> .pw-ui-button.pw-ui-progressive:hover, .pw-ui-button.pw-ui-progressive:focus, .pw-ui-button.pw-ui-progressive:active, .pw-ui-button:hover, .pw-ui-progressive:hover, .pw-ui-button:focus, .pw-ui-progressive:focus {<br /> box-shadow: 0px 0px 0px !important;<br /> text-shadow: 0px 0px 0px !important;<br /> border: 1px solid #40798C !important;<br /> }<br /> <br /> /* End for the Start Page */<br /> <br /> <br /> body {<br /> font-family: &quot;Helvetica Neue&quot;, Helvetica, Arial, sans-serif !important;<br /> background: #fff !important;<br /> }<br /> <br /> p {<br /> font-weight: 300 !important;<br /> line-height: 1.9 !important;<br /> }<br /> <br /> <br /> table, td, th {<br /> border: 0px !important;<br /> border-collapse: collapse !important;<br /> padding: 5px !important;<br /> }<br /> <br /> <br /> ul, li {<br /> background: transparent !important;<br /> border: 0px !important;<br /> line-height: 1.8 !important;<br /> font-size: 14px !important;<br /> font-weight: 300 !important;<br /> }<br /> <br /> li span {<br /> background: transparent !important;<br /> border: 0px !important;<br /> font-size: 14px !important;<br /> }<br /> <br /> .referencetooltip {<br /> background-color: #EEE !important;<br /> }<br /> <br /> dl {<br /> font-weight: 300 !important;<br /> }<br /> <br /> dt {<br /> font-style: italic;<br /> font-size: 16px !important;<br /> margin-top: 10px !important;<br /> }<br /> <br /> dd {<br /> font-size: 15px !important;<br /> }<br /> <br /> .mw-wiki-logo {<br /> padding-left: 15px !important;<br /> padding-top: 10px !important;<br /> border: none !important;<br /> }<br /> <br /> /*#p-logo a {<br /> background-image: url('https://i.imgur.com/ur4m5Ia.png') !important;<br /> }*/<br /> <br /> code {<br /> padding: 3px !important;<br /> background: transparent !important;<br /> color: #39892f !important;<br /> }<br /> <br /> tt {<br /> font-family: 'Source Code Pro', 'Lucida Sans Unicode', 'Courier New' !important;<br /> font-size: 16px !important;<br /> }<br /> <br /> .new, .new:link, .new:visited {<br /> color: #cd5b45 !important;<br /> }<br /> <br /> blockquote {<br /> border: 0px !important;<br /> font-style: italic !important;<br /> font-size: 20px !important;<br /> margin: 35px 75px !important;<br /> line-height: 1.5 !important;<br /> font-weight: 300 !important;<br /> background: transparent !important;<br /> }<br /> <br /> select {<br /> padding: 0px 10px;<br /> }<br /> <br /> .mw-ui-button, .mw-ui-progressive {<br /> border-radius: 4px !important;<br /> border: 1px solid #347Bff !important;<br /> color: #347Bff !important;<br /> background: #fff !important;<br /> text-shadow: 0px 0px 0px;<br /> }<br /> <br /> .mw-ui-button.mw-ui-progressive:hover, .mw-ui-button.mw-ui-progressive:focus, .mw-ui-button.mw-ui-progressive:active, .mw-ui-button:hover, .mw-ui-progressive:hover, .mw-ui-button:focus, .mw-ui-progressive:focus {<br /> box-shadow: 0px 0px 0px !important;<br /> text-shadow: 0px 0px 0px !important;<br /> border: 1px solid #347Bff !important;<br /> }<br /> <br /> #wpSave, #wpPreview, #wpDiff {<br /> border-radius: 4px !important;<br /> border: 1px solid #347Bff !important;<br /> color: #347Bff !important;<br /> background: #fff !important;<br /> text-shadow: 0px 0px 0px;<br /> padding: 0.5em 1em;<br /> cursor: pointer;<br /> }<br /> <br /> #wpSave:hover, #wpPreview:hover, #wpDiff:hover {<br /> color: rgba(52, 123, 255, 0.5) !important;<br /> ;<br /> }<br /> <br /> /* Search */<br /> <br /> #simpleSearch {<br /> background: transparent !important;<br /> border-color: #ccc !important;<br /> }<br /> <br /> #searchInput {<br /> background: transparent !important;<br /> }<br /> <br /> .mw-ui-input {<br /> border: 1px solid #347Bff !important;<br /> color: #000 !important;<br /> background: #fff !important;<br /> font-size: 16px !important;<br /> }<br /> <br /> .mw-ui-input:focus {<br /> box-shadow: 0px 0px 0px !important;<br /> }<br /> <br /> .mw-content-ltr pre {<br /> font-family: &quot;Courier New&quot;, Lucida Console, sans-serif !important;<br /> color: #000d26 !important;<br /> }<br /> <br /> .suggestions {<br /> font-weight: 300 !important;<br /> font-size: 15px !important;<br /> max-width: 300px !important;<br /> margin-top: 15px !important;<br /> border: 0px !important;<br /> box-shadow: 2px 2px 10px 2px rgba(0, 0, 0, 0.5);<br /> }<br /> <br /> .suggestions-results {<br /> border: 0px !important;<br /> }<br /> <br /> .suggestions-result {<br /> padding: 10px !important;<br /> }<br /> <br /> .imeselector, #searchEngines {<br /> display: none !important;<br /> }<br /> <br /> .mw-search-formheader {<br /> border: 0px !important;<br /> background: transparent !important;<br /> }<br /> <br /> .central-featured-logo {<br /> background-image: url('https://i.imgur.com/nRDTbeb.png') !important;<br /> }<br /> <br /> .mw-search-result-heading, .searchresult, .searchmatch {<br /> font-size: 14px !important;<br /> font-weight: 400 !important;<br /> padding: 3px 0px !important;<br /> }<br /> <br /> .searchmatch {<br /> font-weight: 700 !important;<br /> }<br /> <br /> /*<br /> .mw-search-result-data, .mw-search-createlink {<br /> display: none;<br /> }<br /> */<br /> <br /> #mw-page-base, .vectorTabs {<br /> background: transparent !important;<br /> border: 0px !important;<br /> }<br /> <br /> #content {<br /> border: 0px !important;<br /> margin-left: 215px !important;<br /> }<br /> <br /> .portal {<br /> background: transparent !important;<br /> }<br /> <br /> #mw-panel {<br /> width: 200px !important;<br /> border-right: 1px solid #bbb;<br /> background: white !important;<br /> padding-left: 10px !important;<br /> }<br /> <br /> #p-logo {<br /> left: 0px;<br /> padding-left: 10px;<br /> background-color: white;<br /> }<br /> <br /> #p-logo a {<br /> padding-left: 40px;<br /> background-color: white;<br /> left: 0px;<br /> border-right: 1px solid #aaa;<br /> }<br /> <br /> #p-logo a:hover {<br /> opacity: 1.0;<br /> }<br /> <br /> #mw-head {<br /> background-color: #f9f9f9;<br /> opacity: 1.0;<br /> box-shadow: 0px 1px 2px #aaa;<br /> -webkit-transition-property: opacity !important;<br /> -moz-transition-property: opacity !important;<br /> -o-transition-property: opacity !important;<br /> -ms-transition-property: opacity !important;<br /> transition-property: opacity !important;<br /> -webkit-transition-duration: 0.5s !important;<br /> -moz-transition-duration: 0.5s !important;<br /> -o-transition-duration: 0.5s !important;<br /> -ms-transition-duration: 0.5s !important;<br /> transition-duration: 0.25s !important;<br /> <br /> }<br /> <br /> #mw-head:hover {<br /> opacity: 1.0 !important;<br /> }<br /> <br /> .uls-settings-trigger {<br /> display: none !important;<br /> }<br /> <br /> #left-navigation {<br /> margin-left: 233px !important;<br /> }<br /> <br /> .wikitable {<br /> font-weight: 300 !important;<br /> }<br /> <br /> .wikitable td, .wikitable th {<br /> border: 1px dashed rgba(0, 0, 0, 0.07) !important;<br /> }<br /> <br /> pre {<br /> line-height: 1.3 !important;<br /> font-family: &quot;Courier New&quot;, Lucida Console, sans-serif !important;<br /> border: 0px !important;<br /> background: 0px !important;<br /> font-size: 16px !important;<br /> }<br /> <br /> .mw-code {<br /> border: 0px !important;<br /> padding: 17px !important;<br /> background: 0px !important;<br /> font-size: 16px !important;<br /> }<br /> <br /> .toc {<br /> background: transparent !important;<br /> border-style: dashed !important;<br /> display: block !important;<br /> max-width: 300px !important;<br /> }<br /> <br /> .toctoggle {<br /> display: none !important;<br /> }<br /> <br /> .thumbinner, .thumb, .toccolours, .graytable {<br /> background: transparent !important;<br /> border: 0px !important;<br /> font-size: 16px !important;<br /> }<br /> <br /> .thumbimage {<br /> border: 0px !important;<br /> }<br /> <br /> .thumbcaption {<br /> font-style: italic !important;<br /> margin: 7px 0px !important;<br /> }<br /> <br /> .thumbimage:hover {<br /> opacity: 0.85 !important;<br /> }<br /> <br /> .dablink {<br /> margin: 14px 0px !important;<br /> font-weight: 300 !important;<br /> font-size: 18px !important;<br /> }<br /> <br /> #siteSub, .flaggedrevs_preview {<br /> display: none !important;<br /> }<br /> <br /> .ambox, .tmbox, .Note, .informationbox {<br /> margin: 5px 0px !important;<br /> font-size: 18px !important;<br /> font-weight: 700 !important;<br /> line-height: 1.5 !important;<br /> border: 1px dashed #aaa !important;<br /> max-width: 550px !important;<br /> font-weight: 300 !important;<br /> }<br /> <br /> .ambox td, .tmbox td {<br /> padding: 10px !important;<br /> }<br /> <br /> .ambox-text-small, .mbox-text, .Note td {<br /> font-size: 14px !important;<br /> font-weight: 300 !important;<br /> color: #000 !important;<br /> }<br /> <br /> .ambox-image, .mbox-image {<br /> display: none;<br /> }<br /> <br /> #request_for_deletion, .ambox-serious {<br /> background: rgba(255, 0, 0, 0.1) !important;<br /> border: 1px dashed rgba(255, 0, 0, 0.15) !important;<br /> color: #a00000 !important;<br /> }<br /> <br /> .tmbox-notice, .tmbox-move, .Note {<br /> background: rgba(150, 75, 0, 0.1) !important;<br /> border: 1px dashed rgba(150, 75, 0, 0.15) !important;<br /> }<br /> <br /> .informationbox {<br /> background: #fff !important;<br /> padding: 10px !important;<br /> font-size: 14px !important;<br /> }<br /> <br /> .editOptions {<br /> background: #fff !important;<br /> border: 0px !important;<br /> }<br /> <br /> .catlinks {<br /> background: transparent !important;<br /> border: 1px dashed #aaa !important;<br /> font-size: 16px !important;<br /> }<br /> <br /> .infobox, .tright, .toccolours {<br /> border: 0px !important;<br /> background: transparent !important;<br /> border-collapse: collapse !important;<br /> }<br /> <br /> .infobox td, .infobox th, .tright td, .tright th, .toccolours td, .toccolours th {<br /> padding: 5px !important;<br /> background: transparent !important;<br /> font-weight: 400 !important;<br /> border: 1px dashed rgba(0, 0, 0, 0.07) !important;<br /> }<br /> <br /> .image img:hover {<br /> opacity: 0.85 !important;<br /> }<br /> <br /> .globegris {<br /> background: transparent !important;<br /> }<br /> <br /> .mw-editsection-bracket, .references-small b, .mw-cite-backlink, .plainlinksneverexpand {<br /> display: none !important;<br /> }<br /> <br /> #floating_object {<br /> display: none;<br /> }<br /> <br /> .navbox, .nowraplinks {<br /> margin: 10px 0px !important;<br /> border-collapse: collapse !important;<br /> }<br /> <br /> .navbox td, .navbox th, .nowraplinks td, .nowraplinks th {<br /> padding: 9px 6px !important;<br /> font-size: 14px !important;<br /> font-weight: 300 !important;<br /> border: 1px solid #fff !important;<br /> }<br /> <br /> .NavFrame {<br /> border: 0px !important;<br /> background: transparent !important;<br /> padding: 0px !important;<br /> }<br /> <br /> .NavHead {<br /> margin: 10px 0px !important;<br /> padding: 12px !important;<br /> font-size: 16px !important;<br /> font-weight: 700 !important;<br /> background: transparent !important;<br /> }<br /> <br /> .Boxmerge {<br /> border: 0px !important;<br /> }<br /> <br /> #coordinates {<br /> display: none !important;<br /> }<br /> <br /> #mw-fr-revisiontag, #mw-fr-reviewnotice {<br /> display: none !important;<br /> }<br /> <br /> div#footer {<br /> margin-left: 14em !important;<br /> padding: 1.25em 1.5em 1.5em !important;<br /> }<br /> <br /> .mw-footer {<br /> margin-left: 14em !important;<br /> padding: 1.25em 1.5em 1.5em !important;<br /> }<br /> <br /> <br /> /* General styling */<br /> <br /> :root {<br /> --primary-color: #742774;<br /> --primary-color-light:#c5b7c5;<br /> --primary-color-light2: #e9e4e9;<br /> --secondary-color: #236767;<br /> --dark-color: #0B2027;<br /> <br /> --success-color: #11620B;<br /> --success-color-light: #D2FBD0;<br /> <br /> --warning-color: #b88a00;<br /> --warning-color-light: #FFEED8;<br /> <br /> --error-color: #CC0000;<br /> --error-color-light: #E5B4B4;<br /> <br /> --grey-light-1: #F9F9F9;<br /> <br /> --powerautomate-primary-color: #356CDA;<br /> --powervirtualagent-primary-color: #327B8F;<br /> --powerbi-primary-color: #E1AD34;<br /> }<br /> <br /> <br /> /******* Styling headers *******/<br /> h1, h2, h3, h4, h5, h6 {<br /> color: var(--primary-color);<br /> border: 0px;<br /> font-family: 'Arial';<br /> }<br /> <br /> h1 {<br /> font-weight: 700;<br /> font-size: 36px;<br /> }<br /> <br /> h2 {<br /> font-weight: 400;<br /> font-size: 26px;<br /> }<br /> <br /> h3 {<br /> font-weight: 400;<br /> font-size: 16px;<br /> }<br /> <br /> /******* Styling links *******/<br /> a:not(.image), a:not(.image):visited {<br /> color: black !important;<br /> }<br /> <br /> a:not(.image):hover, a:not(.image):visited:hover{<br /> color: var(--primary-color) !important;<br /> }<br /> <br /> #bodyContent a:not(.image), #bodyContent a:not(.image):visited{<br /> text-decoration: underline !important;<br /> }<br /> <br /> #bodyContent a:not(.image):hover, #bodyContent a:not(.image):visited:hover {<br /> text-decoration: none !important;<br /> color: var(--primary-color) !important;<br /> }<br /> <br /> .mw-cookiewarning-container a, .mw-cookiewarning-container a:visited{<br /> color: white !important;<br /> }<br /> <br /> .mw-cookiewarning-container a:hover, .mw-cookiewarning-container input:hover{<br /> color: white !important;<br /> text-decoration: underline;<br /> }<br /> <br /> /******* Tables *******/<br /> table {<br /> margin: 2em 0;<br /> }<br /> <br /> table, td, th{<br /> border: 1px solid var(--primary-color) !important;<br /> }<br /> <br /> tr:nth-child(odd) {<br /> background-color: var(--primary-color-light2);<br /> }<br /> <br /> th {<br /> text-align:left;<br /> background-color: var(--primary-color-light);<br /> }<br /> <br /> /******* PW Boxes *******/<br /> #bodyContent .pw-box{<br /> margin: 1em 0;<br /> padding: 1em;<br /> border-width: 1px;<br /> border-left-width: 5px;<br /> border-style: solid;<br /> border-color: black;<br /> border-radius: 6px;<br /> font-size: inherit !important;<br /> }<br /> <br /> #bodyContent .pw-box.infobox-present{<br /> /*<br /> 300px = width of infobox<br /> 5em = 1x margin of infobox + 2x padding of infobox + 2x padding of PWBox<br /> 8px = 5px left border of PWBox + 1px right border of PWBox + 2 pixel (left and right) border of InfoBox<br /> */<br /> width:calc(100% - 300px - 5em - 8px);<br /> max-width:calc(100% - 300px - 5em - 8px);<br /> }<br /> <br /> #bodyContent .pw-box h3{<br /> margin-top: 0;<br /> font-weight:bold;<br /> }<br /> <br /> #bodyContent .pw-box.info{<br /> border-color: var(--primary-color);<br /> color: var(--primary-color);<br /> background-color: var(--primary-color-light);<br /> }<br /> #bodyContent .pw-box.info h3{<br /> color: var(--primary-color);<br /> }<br /> <br /> #bodyContent .pw-box.info a,<br /> #bodyContent .pw-box.info a:visited{<br /> color: var(--primary-color) !important;<br /> }<br /> <br /> #bodyContent .pw-box.warning{<br /> border-color: var(--warning-color);<br /> color: var(--warning-color);<br /> background-color: var(--warning-color-light);<br /> }<br /> #bodyContent .pw-box.warning h3{<br /> color: var(--warning-color);<br /> }<br /> <br /> #bodyContent .pw-box.warning a,<br /> #bodyContent .pw-box.warning a:visited{<br /> color: var(--warning-color) !important;<br /> }<br /> <br /> #bodyContent .pw-box.error{<br /> border-color: var(--error-color);<br /> color: var(--error-color);<br /> background-color: var(--error-color-light);<br /> }<br /> <br /> #bodyContent .pw-box.error h3{<br /> color: var(--error-color);<br /> }<br /> <br /> #bodyContent .pw-box.error a,<br /> #bodyContent .pw-box.error a:visited{<br /> color: var(--error-color) !important;<br /> }<br /> <br /> #bodyContent .pw-box.success{<br /> border-color: var(--success-color);<br /> color: var(--success-color);<br /> background-color: var(--success-color-light);<br /> }<br /> <br /> #bodyContent .pw-box.success h3{<br /> color: var(--primary-success);<br /> }<br /> <br /> #bodyContent .pw-box.success a,<br /> #bodyContent .pw-box.success a:visited{<br /> color: var(--success-color) !important;<br /> }<br /> <br /> #bodyContent .mw-ui-button, #bodyContent .mw-ui-progressive{<br /> border-color: var(--primary-color) !important;<br /> color: var(--primary-color) !important;<br /> }<br /> <br /> /******* Infobox *******/<br /> .pw-infobox {<br /> background-color: var(--grey-light-1);<br /> border: 1px solid #aaa;<br /> float: right;<br /> margin: 0 0 1em 1em;<br /> width: 300px;<br /> max-width: 300px;<br /> min-width: 300px;<br /> }<br /> <br /> .pw-infobox .pw-infobox-title {<br /> padding: 1em;<br /> font-size: 1.5em;<br /> text-align: center;<br /> font-family: 'Linux Libertine','Georgia','Times',serif;<br /> font-weight:bold;<br /> background-color: var(--primary-color);<br /> color: white;<br /> }<br /> <br /> .pw-infobox .pw-infobox-content {<br /> padding: 1em;<br /> }<br /> <br /> .pw-infobox .pw-infobox-content .pw-infobox-image {<br /> text-align: center;<br /> }<br /> <br /> .pw-infobox .pw-infobox-content table {<br /> margin: inherate;<br /> }<br /> <br /> .pw-infobox .pw-infobox-content table,<br /> .pw-infobox .pw-infobox-content td,<br /> .pw-infobox .pw-infobox-content th{<br /> border: 0 !important;<br /> }<br /> <br /> .pw-infobox .pw-infobox-content tr:nth-child(odd) {<br /> background-color: transparent;<br /> }<br /> <br /> .pw-infobox .pw-infobox-content th {<br /> text-align: left;<br /> vertical-align: top;<br /> width: 130px;<br /> background-color: transparent;<br /> color: var(--primary-color);<br /> }<br /> <br /> .pw-infobox .pw-infobox-content td {<br /> vertical-align: top;<br /> }<br /> <br /> /** Power Automate **/<br /> .pw-infobox.PowerAutomate .pw-infobox-title {<br /> background-color: var(--powerautomate-primary-color);<br /> }<br /> <br /> .pw-infobox.PowerAutomate .pw-infobox-content th {<br /> color: var(--powerautomate-primary-color);<br /> }<br /> <br /> /** Power Virtual Agent **/<br /> .pw-infobox.PowerVirtualAgent .pw-infobox-title {<br /> background-color: var(--powervirtualagent-primary-color);<br /> }<br /> <br /> .pw-infobox.PowerVirtualAgent .pw-infobox-content th {<br /> color: var(--powervirtualagent-primary-color);<br /> }<br /> <br /> /** Power BI **/<br /> .pw-infobox.PowerBI .pw-infobox-title {<br /> background-color: var(--powerbi-primary-color);<br /> color:black;<br /> }<br /> <br /> .pw-infobox.PowerBI .pw-infobox-content th {<br /> color: var(--powerbi-primary-color);<br /> }<br /> <br /> /******* Delete lines between menu entries in top horizontal menu *******/<br /> .vector-menu-tabs, .vector-menu-tabs a{<br /> background:none;<br /> }</div> Benedikt http://powerwiki.net/index.php?title=Template:PWBox&diff=4300 Template:PWBox 2021-02-01T18:47:01Z <p>Benedikt: </p> <hr /> <div>&lt;div class=&quot;pw-box {{{severity}}} {{{cssClasses}}}&quot;&gt;<br /> === {{{title}}} ===<br /> {{{text}}}<br /> &lt;/div&gt;</div> Benedikt http://powerwiki.net/index.php?title=Template:PWBox&diff=4296 Template:PWBox 2021-02-01T14:46:30Z <p>Benedikt: /* {{{title}}} */</p> <hr /> <div>&lt;div class=&quot;pw-box {{{severity}}} {{{cssClasses}}}&quot;&gt;<br /> &lt;div&gt;<br /> === {{{title}}} ===<br /> {{{text}}}<br /> &lt;/div&gt;</div> Benedikt http://powerwiki.net/index.php?title=Power_Wiki_Wishlist&diff=4295 Power Wiki Wishlist 2021-02-01T14:46:04Z <p>Benedikt: </p> <hr /> <div><br /> <br /> <br /> <br /> == Todo ==<br /> * Twitter-lista &quot;Recommended Twitter accounts to follow&quot;<br /> * Blogglista - tabell<br /> * YT-konton - tabell<br /> * Podcasts - tabell<br /> * Alla länkar - skippa att ha färg över länkarna. Låt det vara som i menyn.<br /> <br /> * Infobox till höger - färger.<br /> * Annan stil på annat än huvudfeatures?<br /> <br /> == Todo CC ==<br /> * Justera alla MS Docs-länkar - ta bort en-us.<br /> * In a Day - sida, ta bort de andra sidorna om detta.<br /> * Gå igenom alla sidor - uppdatera kategorier, lägga in infobox, länkar till olika blogginlägg och tipsa om hela bloggar, t ex omnichannel EY, dynamics HR - Ana och Malin. <br /> <br /> == Ideas == <br /> * Hur ska man lätt hitta content t ex om man är nybörjade, expert mm.? <br /> * Content: XrmToolBox - Tabell med alla verktyg samt länkar till Community Content.<br /> * Content: Dataverse for Teams<br /> * Content: Uppdatera Release Waves. Vad, När, Hur, Bra att veta. <br /> * Call for speakers.<br /> * Methodolody, Neil Benson. <br /> * Licenses.<br /> <br /> == Old ==<br /> For now - we use [https://coolors.co/0b2027-40798c-70a9a1-cfd7c7-f6f1d1 this colour scheme] <br /> Primary Colour: #40798C<br /> Second Colour: #70A9A1<br /> <br /> == Shit list == <br /> * CSS, logon page <br /> <br /> == Categories ==<br /> To be defined... T ex:<br /> * Best Practice<br /> * Maker, Techie, Business User<br /> * Beginner, Intermediate, Expert (levels 100. 200. 300. 400 etc.?)<br /> <br /> {{<br /> PWBoxInfo<br /> | title = Test Info<br /> | text = Test test test<br /> }}<br /> <br /> {{<br /> PWBoxTip<br /> | text = Test test test<br /> }}<br /> <br /> {{<br /> PWBoxWarning<br /> | title = Test Warning<br /> | text = Test test test<br /> }}<br /> <br /> {{<br /> PWBoxError<br /> | title = Test Error<br /> | text = Test test test<br /> }}<br /> <br /> {{<br /> PWBoxSuccess<br /> | title = Test Success<br /> | text = Test test test<br /> }}</div> Benedikt http://powerwiki.net/index.php?title=Licensing&diff=4294 Licensing 2021-02-01T14:45:13Z <p>Benedikt: </p> <hr /> <div>This page contains information about where to find resources about licensing. <br /> <br /> Related to licensing is [[API requests limits]]<br /> <br /> == Microsoft Resources ==<br /> * [https://docs.microsoft.com/en-us/power-platform/admin/pricing-billing-skus/?WT.mc_id=DX-MVP-5003780 Power Platform licensing in MS Docs]<br /> * [https://docs.microsoft.com/sv-se/power-platform/admin/powerapps-flow-licensing-faq/?WT.mc_id=DX-MVP-5003780 MS Docs Power Apps and Power Automate Licensing FAQ]<br /> <br /> == Community Resources ==<br /> * [https://youtu.be/f_GwhZrwNtI Power Apps Licensing Explained (Power Apps FAQ #1)] by Lisa Crosbie<br /> * [https://youtu.be/VyrjpdVm_Ko Power Apps Community Plan - Free Individual Environment for your Learning] by Steve Mordue<br /> * [https://youtu.be/2iyuSaSS2dk Power Apps - Licenses vs. Passes] by Steve Mordue<br /> <br /> {{<br /> PWBoxTip<br /> | text = Follow [https://jukkaniiranen.com/ Jukka Niiranen’s blog], he usually write great summaries about licensing.<br /> }}<br /> <br /> [[Category:Maker]]<br /> [[Category:Developer]]<br /> [[Category:Admin]]</div> Benedikt http://powerwiki.net/index.php?title=Licensing&diff=4293 Licensing 2021-02-01T14:44:56Z <p>Benedikt: </p> <hr /> <div>This page contains information about where to find resources about licensing. <br /> <br /> Related to licensing is [[API requests limits]]<br /> <br /> == Microsoft Resources ==<br /> * [https://docs.microsoft.com/en-us/power-platform/admin/pricing-billing-skus/?WT.mc_id=DX-MVP-5003780 Power Platform licensing in MS Docs]<br /> * [https://docs.microsoft.com/sv-se/power-platform/admin/powerapps-flow-licensing-faq/?WT.mc_id=DX-MVP-5003780 MS Docs Power Apps and Power Automate Licensing FAQ]<br /> <br /> == Community Resources ==<br /> * [https://youtu.be/f_GwhZrwNtI Power Apps Licensing Explained (Power Apps FAQ #1)] by Lisa Crosbie<br /> * [https://youtu.be/VyrjpdVm_Ko Power Apps Community Plan - Free Individual Environment for your Learning] by Steve Mordue<br /> * [https://youtu.be/2iyuSaSS2dk Power Apps - Licenses vs. Passes] by Steve Mordue<br /> <br /> {{<br /> PWBoxInfo<br /> | text = Follow [https://jukkaniiranen.com/ Jukka Niiranen’s blog], he usually write great summaries about licensing.<br /> }}<br /> <br /> [[Category:Maker]]<br /> [[Category:Developer]]<br /> [[Category:Admin]]</div> Benedikt http://powerwiki.net/index.php?title=Template:PWBoxTip&diff=4292 Template:PWBoxTip 2021-02-01T14:44:28Z <p>Benedikt: Created page with &quot;{{PWBox | title = Tip! | text = {{{text}}} | cssClasses = {{{cssClasses}}} | severity = info }}&quot;</p> <hr /> <div>{{PWBox<br /> | title = Tip!<br /> | text = {{{text}}}<br /> | cssClasses = {{{cssClasses}}}<br /> | severity = info<br /> }}</div> Benedikt