This is the first of many discussions into ALM strategy form Power Platform. In this installment I dive into the most fundamental question of any Power Platform ALM strategy:
How should I structure my solutions to enable a robust and reliable ALM strategy that enables and enhances the work of developers and functionals?
I have worked with two primary structuring methodoligies:
Users who are familiar with Dynamics and Power Platform Model Driven Apps expect a double-click action on grids and grid-like components. By default Power Apps portals does not provide a double-click action for entity lists that are rendered on a page, and as far as I am aware, there is no configuration option to enable this.
Does your Docusaurus front matter image path contain spaces? Is Docusaurus yelling at you during build?
Maybe I can help?
[ERROR] The following front matter:
---
title: My Blog Post
description: A sweet new blog post
slug: my-blog-post
authors: coreysutton
tags:
- Power Platform
image: /img/Power Platform/PowerAutomate_scalable.svg
---
contains invalid values for field(s): `image`.
- "image" does not look like a valid url (value='')
[ERROR] Error while parsing blog post file "{path}/2022-09-01-my-blog-post.mdx".
[ERROR] Processing of blog source file "{path}/2022-09-01-my-blog-post.mdx" failed.
[ERROR] ValidationError: "image" does not look like a valid url (value='')
Azure Static Web Apps build and deploy Action Azure/static-web-apps-deploy@v1 appers to be fixed to Node.js 14.x, which throws errors when build against the latest version of Docusaurus (v2.0.1) which requires >=16.14.
> docusaurus build
[ERROR] Minimum Node.js version not met :(
[INFO] You are using Node.js v14.19.1, Requirement: Node.js >=16.14.
...
---End of Oryx build logs---
Oryx has failed to build the solution.
If your work across a range of customer who add your primary Azure AD account to their Azure AD Tenant as a guest, then you're likely familiar with forcing a resouce to detect and use the correct account.