microsoftlearning/pl-400_microsoft-power-platform-developer

pl-400_microsoft-power-platform-developer's Issues

Lab04 Task-1 Outlook connection issue

Module: 04

Lab/Demo: 04

Task: 01

Step: 21

Not able to create connection with outlook connector.

Repro steps:

Trail Environment to be mentioned as Prod.

Module: 01

Lab/Demo: 00

Task: 01

Step: 03 and 04

Description of issue: In the steps, Trial Environment has been mentioned as Dev. However, it needs to be Prod env.

Repro steps:

3. Your Dev environment should now show in the list of Environments.
4. Your environment may take a few minutes to provision. Refresh the page if needed. When your environment is prepared, select your Dev environment by clicking on the ellipses next to its name to expand the drop down menu and select Settings.

PL-400 Issue

Module: All

Lab/Demo: 06

Task: 1

Step: b (Get the locked Permit Count and throw InvalidPluginExecutionException if the Count is more than 0)

Description of issue:

The lab instructions are incorrect.
The following references "tables" and does not generate the correct locker permits count: int lockedPermitCount = (int)((AliasedValue)response.Tables[0]["Count"]).Value

It should be: int lockedPermitCount = (int)((AliasedValue)response.Entities[0]["Count"]).Value;

This needs to be corrected as soon as possible. Thank you!

All Labs Importqant suggestions

All Lab Suggestion

Description of issue

Repro steps:

1. When copy-pasting code, paste to notepad first
2. When code is pasted check number of } braces at the end.
3. Check missing ',' at the end of statements
4. Check spelling of functions and classes.

Add more

Power Platform Trial Requires Credit Card

Module: 01

Lab 0 / Exercise 2

Task: 2.1

Step: 12

When you click "Try now" to activate the Power Apps Premium free trial, the Information Required dialog box pops up. It states "In order to start your trial subscription, we require a credit card payment method to be added to your account. This payment method will not be charged without your consent. After it is added, please retry activating your trial." The only option is the "Continue" button that takes you directly to the Payments Methods page.

These tenants are Microsoft property, I don't think that it is proper to ask students to provide their personal credit card information to the tenants that are owned by Microsoft.

Thanks for any help.

Developer Environment Cannot Be Created

Module: 01

Lab 0 / Exercise 3

Task: 3.1

Step: 8

Add Dataverse tab, which requires you to pick a language and currency. But neither dropdown boxes are getting populated correctly nor does it allow you to provide input. The save button remains greyed out.

Lab 5 Exercise 4 Task 1

Module: 07

Lab/Demo: 4

Task: Exercise #4: Command Button Function (Optional)

Step: Task #1: Create Custom API

Description of issue
step number 4 "Create custom API response parameter" is wrongly called "API response parameter" the right one is "Custom API Response Property" and this one doesn't have the "Is Optional" field

Lab 10 - checking in into the GIT repo does not work

Part of the Lab 10 - ALM is the check-in procedure for checking-in the unpacked Power Platform solution into the GIT repository in Azure DevOps. The procedure is implemented using a command line task in Azure DevOps. The steps are the following:

echo commit all changes
git config user.email "[email protected]"
git config user.name "Automatic Build"
git checkout master
git add --all
git commit -m "solution init"
echo push code to new repo
git -c http.extraheader="AUTHORIZATION: bearer $(System.AccessToken)" push origin master

There are actually 2 issues:

1. The steps must change the branch name "master" to "main", in alignment with the current functionality of Azure DevOps
2. Even after this change, the steps do not check - in anything into the GIT. Here is the whole execution log:

Starting: Command Line Script

Task : Command line
Description : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
Version : 2.182.0
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line

Generating script.
========================== Starting Command Output ===========================
"C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "D:\a_temp\7a375376-b7d2-4f2f-b87c-cd69c088a938.cmd""
commit all changes
Switched to a new branch 'main'
Branch 'main' set up to track remote branch 'main' from 'origin'.
On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean
push code to new repo
Everything up-to-date
Finishing: Command Line Script

Course screenshots old/obsolete: Specific recommendations for new screenshots in Lab 1 & 2

Module: 00

Lab/Demo: 01 & 02

Task: (various)

Step: (various)

Description of issue

• General recommendation to update screenshots throughout the course so as to show current terminology and features. Specific (high value) recommendations for screenshot updates here:

Lab 1, Exercise 1, Task 2, Step 2 -- Screen shot of publisher needs updating
Lab 1, Exercise 2, Task 1, Step 2 -- Screen shot needs updating to read Table
Lab 1, Exercise 2, Task 1, Step 3 -- Screen shot needs updating to read Columns
Lab 2, Exercise 1, Task 1, Steps 2-6 & 10 -- Update screenshots to current version. Old screenshots showing old terminology and features
Lab 2, Exercise 1, Task 3, Steps 2 & 10 -- Update screenshots to current version. Old screenshots showing old terminology and features
Lab 2, Exercise 2, Task 2, Steps 2 & 5 -- Update screenshots to current version. Old screenshots showing old terminology and features

Unable to push/publish Visual Studio Code file into Power Apps. Lab 5, exercise 2, task 1.

Lab: 05

Task: 1

Step: 3

Description of issue: After completing the rest of this lab multiple times to ensure accuracy, we are unable to use the command "pac pcf push --publisher-prefix contoso" without facing errors.

Errors:

• Error: Building temporary solution wrapper: failed. See obj\build.log for more details.
• The OutputPath property is not set for project 'PowerAppsTools_contoso.cdsproj'. Please check to make sure that you have specified a valid combination of Configuration and Platform for this project.

We also tried to run this before the publish command just to see if there were any steps missing that we could recommend adding but it didn't work for us: msbuild /p:configuration=Release 

We were trying to see if there was anyone else having the same issue and how we could resolve it, but we were not successful and all posts we found were related to old versions that we're not using at the moment. All posts were about version 1.16 but we're on latest (1.21.8). We tried switching between versions just in case but that didn't work either so we think it's probably something else that we're missing.

Repro steps:

1. In Visual Studio Code, within the SRC directory in the terminal, I enter "pac auth create --url " and authenticate successfully.
2. The next step as mentioned above, fails with the errors listed.

Minor type-o in Lab 3 - Canvas App

Lab: 3

Exercise: 2

Description of issue:

Just a minor type-o. Exercise #2 has Task 2.1, Task 2.2, and Task 2.4. Task 2.4 should be renamed to Task 2.3.

Lab 10 - Plugin

Module: 10 Plugins

Exercise 2: Create Custom Action Plugin

Task 2.1: Add a new plugin to the project

Step: 2

There is a typo in this line and it is not needed, I suggest removing it:

using ContosoPackagePoject;

PowerApps Trigger v1 is no longer available

Lab 5

Exercice 2

Step: 02

PowerApps V1 Trigger is no longer available, you must use the powerapps V2 trigger

applied workshop solution is a managed solution

Module: Applied Workshop solution

Lab/Demo: 00

Task: 00

Step: 00

The new available applied workshop solution is a managed solution. Not really demo able as I cannot change anything. Can you upload a unmanaged solution? Although no description of the solution yet.

Repro steps:

Guide not matching power apps portal

Lab: 5

Exercise 3

Task: 2

Description of issue
This is no longer accurate, these options aren't listed below "advanced settings"

Following this guide, you also get an error when trying to import this solution:

Lab 10 ALM Script task fails - ERROR:src refspec main does not match any

Module: 10

Lab/Demo: 10

Task: 01

Step: 12

Description of issue
The script fails with ERROR:src refspec main does not match any

Solution so far is simple. Include git fetch after line 3.

echo commit all changes
git config user.email "[email protected]"
git config user.name "Automatic Build"
git fetch
git checkout main
git add --all
git commit -m "solution init"
echo push code to new repo
git -c http.extraheader="AUTHORIZATION: bearer $(System.AccessToken)" push origin main

"npm run build" never succeeds

Module: 00

Lab: 05

Exercise 1, Task: 2

Step: 7

Description of issue
"npm run build" generates errors. I've tried it on three different instances of the lab and am certain that I am performing every step to the letter.

Repro steps:

1. I follow all the stsps in Tasks 1 and 2 up to Task 2 Step 7.
2. At step 7, I run the specified command: npm run build
3. The result is always as shown in the image below:

PL-400 Trainer Materials/foils

Module: All

Lab/Demo: All

Task: All

Step: All

Description of issue

Repro steps:

I try to find the course material and foils for MCTs. I can see the Instructions and the Labs and Solutions, but no foils!

Where can I get this and if necessary, further course materials for MCTs?

b. rgds.
Petra

Lab 6

Module: 00

Lab/Demo: 00

Task: 00

Step: 00

Description of issue

Task 1

1. You can not download "PluginBase.cs" file from the github. Please make this available to be downloadable

2. Also in the code, throuwn an error:
   protected override void ExecuteCDSPlugin(LocalPluginContext localcontext)

    {
   
        base.ExecuteCDSPlugin(localcontext);
   
        var permitEntity = localcontext.PluginExecutionContext.InputParameters["Target"] as Entity;
        var buildSiteRef = permitEntity["contoso_buildsite"] as EntityReference;
        localcontext.Trace("Primary Entity Id: " + permitEntity.Id);
        localcontext.Trace("Build Site Entity Id: " + buildSiteRef.Id);
        string fetchString = "<fetch output-format='xml-platform' distinct='false' version='1.0' mapping='logical' aggregate='true'><entity name='contoso_permit'><attribute name='contoso_permitid' alias='Count' aggregate='count' /><filter type='and' ><condition attribute='contoso_buildsite' uitype='contoso_buildsite' operator='eq' value='{" + buildSiteRef.Id + "}'/><condition attribute='statuscode' operator='eq' value='463270000'/></filter></entity></fetch>";
        localcontext.Trace("Calling RetrieveMultiple for locked permits");
        var response = localcontext.OrganizationService.RetrieveMultiple(new FetchExpression(fetchString));
        int lockedPermitCount = (int)((AliasedValue)response.Tables[0]["Count"]).Value;
        localcontext.Trace("Locket Permit count : " + lockedPermitCount);
        if (lockedPermitCount > 0)
        {
            throw new InvalidPluginExecutionException("Too many locked permits for build site");
        }
   
    }
   

any correction?

Repro steps:

No Owner column on Permit Type table

Learning Path: 2

Lab: 2

Task: 1.5

Step: 7

Description of issue

The Permit Type table was created as an Organizational Owned table and does not have an owner field.
The step says "Add Require Inspections and Require Size columns to the form between Name and Owner."

The step should say "Add Require Inspections and Require Size columns to the form below Name"
The screenshot needs to be updated to not show the Owner

Inspection doesn't change color

Module: 05

Lab/Demo: 05

Task: 03 Debug

Step: 3

Inspection doesn't change color

Once I add the "Status Reason" in the form I still see green color in all the Inspections shown in slider. In the debug I noticed permitStatus is always null

Rectify Development environment as Dev only.

Module: 01

Lab/Demo: 01

Task: 01

Step: 01

Description of issue: Development environment has been mentioned as Prod env.

Repro steps:

1. Create the community plan environment

Navigate to https://powerapps.microsoft.com/en-us/communityplan/
Click on Existing user? Add a dev environment
Enter your credentials when prompted to sign in
Select your country from the dropdown menu and click Accept
Navigate to https://admin.powerplatform.microsoft.com/environments to see a new environment has been created by the system. We will refer to it as "Prod" environment for the rest of this course.

Lab 0 Ex 2 Task 2.3: Not applicable after updated Task 2.2, navigation to 365 admin center needed

• Practice Lab 0 - Validate lab environment
• Exercise 2 – Power Platform trial
• Task 2.3 – Assign Power Apps licenses to your user

Task 2.3, in which the Power Apps license previously obtained via the admin center is assigned to MOD Administrator, is not applicable following the update to Task 2.2 to provision a trial via https://powerapps.microsoft.com/ (8979724). After competing the updated Task 2.2, the Microsoft Power Apps Plan 2 Trial is already assigned to the MOD Administrator user. Removing Task 2.3 would prevent this mismatch.

Additionally, the updated Task 2.2 concludes with the make.powerapps.com tab open. Tasks 2.3 and 2.4 refer to actions within the 365 admin center page, without a preceding step indicating that the learner should navigate to the corresponding page. Adding a step at the end of Task 2.2 or the beginning of the next task would clarify this.

Ribbon Workbench : for performance reasons, this solution cannot be loaded.

Module: 04

Lab/Demo: 04 - Lab04_Client_Scripting

Exercise: 4

Task: 4 - Add Button to Ribbon

Step: 02 - Load the Permit Management solution

Description of issue: I do see "Permit Management" solution in the pop-up opened for selecting the Load Solution but when I click "OK" it shows a message "for performance reasons, this solution cannot be loaded...". I have followed the instructions twice now, but couldn't resolve the issue.

Following entities are in Permit Management Solution:

Lab 04 Ribbon Workbench

Module: 04

Lab/Demo: 04: Command Button Function

Task: 04: Add Button to Ribbon

Step: 02: Load the Permit Management solution

Description of issue

After selection Permit Management solution the following warning appears:

• The solution contains Entities that have all their sub-components included.
• The solution contains non-entity components (e.g. attributes/forms/apps/dashboards/workflows).
• There are more than 5 entities in the solution.
Please create a solution and add only the Entities you wish to edit, with no sub-components!

Lock Permit is not visible

Lab/Demo: 06 Plug-ins

Exercise: 03 Test Plugins

Task: 01 Test Lock Plugin

Step: 04 Lock Permit

Description of issue: Followed the instructions twice but seems the "Lock Permit" button is not visible.

1. Add Plugin Assembly and Plugin - step to the Permit Management solution
   
2. Check Enable Attachments and Notes,
   
3. Set Enable Plugin Logging to Plugin Trace Log to All
   
4. Create test record
   
5. Lock permit is not visible
   

Errors during Plugin steps

Module: 00

Lab/Demo: 08

Task: 03

Step: 00

Description of issue
Getting reports of multiple "Plugin" errors on this Lab.

Lab/Demo: 08

Task: 03

Lab Number: 6 Plugins

Exercise Number: 1

Task Number: 1

Step Number: 5

Unable to publish to azure function

Module: 10

Lab/Demo: 11

Exercise: 03

Task: 3.1

Description of issue
Cannot publish to Azure from Visual Studio

Repro steps:

1. Follow the steps until Exercise 3, Task 3.1

Ability to import components in Canvas apps is removed

Lab/Demo: 03

Exercise 1

Task: 1

Step: 4

Description of issue

The lab has you importing components. However, import has been deprecated and removed:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/create-component. Users may be able to opt in for a limited time on a per-app basis. This portion of the lab will probably need redone.

Repro steps:

1. On Lab 3, Ex 1, Task 1, Step 4, there is no ellipses and no import option.

Lab 07 : Lab 07 – Azure Functions

Module: 10

Lab/Demo: 07 Exercise 2

Task: 01

Step: 04

Description of issue : The nugget package Microsoft.IdentityModel.Clients.ActiveDirectory. is deprecated.

Due to this complete code need to change.

Repro steps:

Multiple errors in Learning Paths 0 and 10

Learning Paths: 00, 10

Exercise: 02 (LP 0), Exercise 3 (LP 10)

Task: 02 (LP 0), Task 3.2 (LP 10)

Step: 10 (LP 0), Step 1, part 6 (LP 10)

Description of issue

Repro steps:

1. LP 0, Exercise 02, Task 02, Step 10: The instruction to acquire a PowerApps per user plan isn't available in the Admin environment in Lab 0,

2. LP 10, Exercise 3, Task 3.2, Step 1, part 6: The status reason value on the Test Permit after completing the prerequisite steps should be set to Status Reason Value locked, but it's set to Active.

PL-400 Errors and Remedies

There are literally hundreds and hundreds of grammatical, typographical, and graphical errors in the lab files. This results in confusion where code snippets and instructions don't match graphics which don't match the PowerApps and Azure sites. MCT's should expect a large time investment validating the lab instructions and files. I was able to fix every lab except Module 7.

Stumbling points:
Lab 4, Exercise 1, Task 4, Test Event Handlers - I received the same warnings and errors as described by mreherefortea but they did not prevent me from using the debugging tools and receiving the expected outcome. Filtered out warnings and errors to remove the distraction.

Lab 4, Exercise 2, Task 1, Step 3 - var permitType = formContext.getColumn("contoso_permittype").getValue(); should be var permitType = formContext.getAttribute("contoso_permittype").getValue();

Lab 4, Exercise 4, Task 4 - doesn't work and hasn't worked for years as it's described in the course. If you can't complete Lab 4 expect Lab 6 to also fail. Use this reference to fix the nonworking steps in the lab: https://ribbonworkbench.uservoice.com/knowledgebase/articles/169819-speed-up-publishing-of-solutions

Lab 5, Exercise 1, Task 1 - a Visual Studio installation is required for this and future labs (no, it's not listed as necessary software for the course but should be). There are screenshots reflecting a Visual Studio 2019 installation but later course artifacts indicate Visual Studio 2017 was used, therefore, completed lab files will not work unless you have both 2017 and 2019 installed. Developer Command Prompt is used in this lab and Visual Studio will be used to create plug-ins in Chapter 6.

Lab 5, Exercise 1, Task 5, Step 1 - Ensure the styles are added to src\timelinecontrol\css\timelinecontrol.css and not out\controls... or the styles will be overwritten on each run (the styles will work once and then the empty css will overwrite the defined styles in \out). This took a few debugging sessions to figure out.

Lab 7, Exercise 1, Task 2 - Couldn't complete Task 2 so lab was a bust for me. Tried numerous workarounds and found no joy. Moved on to Module 8.

Lab 9, Exercise 3, Task 2, Step 2 - Add, Flow is no longer an option for the Power Apps Solution (options: Cloud flow, Desktop flow, and Dataflow). Select Cloud Flow, a new browser tab opens in Flow for editing, connect to the CPM Calculator, and then add values for text boxes. Guided instructions and screenshots are incorrect.

Lab 10, Exercise 2, Task 1, Step 12 - command-line script is wrong and will not build and run (returns error: pathspec 'master' did not match any file(s) known to git). Use something like this instead (replacing my admin name and email with yours for the project):
git config user.email "[email protected]"
git config user.name "wesley"
git checkout main
git add --all
git commit -a -m "solution init"
git -c http.extraheader="AUTHORIZATION: bearer $(System.AccessToken)" push origin main

You can download my corrected instructions here: https://1drv.ms/u/s!Ajc7F05xVXXpu3aT-5TMpPePYYSG

Lab 9 - Power Apps Component Framework

Module: 09 Power Component Frameworks

Task: 1.2 & 2.1

Suggestion to do this as well to run properly

Description of issue

Repro steps:

1. Open solution.cdsproj from Solution folder and update the path
   bin/debug
   Ex 2 - Task 2.1 - with https

Labs - all

Module: 00

Lab/Demo: 00

Task: 00

Step: 00

Description of issue
Here is the problem.
Can I ask, who is maintaining the labs?
Lab06 is out of date and has no way of working unless a trainer writes the whole thing.
Lab05 has issues with node and more issues.
How does anyone cover a good of high quality.
I shall do my best based on the effort Microsoft are applying to the course material.
Repro steps:

LAB 4 - Ribbon Workbench

Module: 00

Lab/Demo: 04

Task: 04

Step: 02

Description of issue
The new version of Ribbon Workbench does not allow to load a solution with more than 5 tables to improve loading performance.
You are have to create a temporary solution and add the table "Permit" in order to fulfill the workbench loading requirement (limitations).
Repro steps:
Try to execute Ribbon Workbench but depending on the version and especially if you are using the 3.1.443.1, you will not be able to open the solution "Permit Solution" because of the number of tables in your solution.
You will have to create a temporary solution, add the existing table "Permit", Publish all customizations and get back to ribbon Workbench to open your temporary solution.

As you are customizing the commands associated with the "Permit" Table, these customization will apply to all solutions where this table will be used and your command will finally correctly display in the "Permit Management" Solution and Model-Driven app.

Lab 01 - Exercise 01 - Task 02 - Step 04 - [Error] Deprecated

Module: 00

Lab/Demo: 05

Task: 02

Step: 04

When running the command pac pcf init --name timelinecontrol --namespace contoso --template dataset
Throws several errors:

If try to continue, when running command npm run build
Also throws several errors:

**Ask in PowerApps** dynamic content in Step 3 is missing

Module: 05

Lab/Demo: 05

Task: 2.1

Step: 3

Description of issue: Powerapps trigger is now Powerapps(v2). When following the steps, Ask in PowerApps dynamic content in Step 3 is missing

Repro steps:

follow the steps for Exercise 2, Task 2.1

Lab order May 23 - as i followed

Following the Labs on Learn on Demand, I followed this order for delivery of Modules

Training Guide should be updated with this

Module 1 - Lab 1 & 2 - Day1
Module 2 - Lab 3 - Day 2

Module 3 - Day 2 - Lab 4
Module 4 - Day 2 - Lab 5

Module 5 - Day 3 Lab 6 &
Module 7 - Lab 08 - Day 03
Module 10 Lesson 1 - Lab 07 - Day 3

Module 9 - Day 04
Module 8 - Lab 09
Module 6 - Day 4 - Lab 10

Lab 09 Issue with npm run build

Lab: 09

Task: 1.3

Step: 11

Description of issue:
Encountering the below issues when attempting to run "npm run build":
[pcf-1014] [Error] Manifest validation problem: instance.manifest.control[0].resources[0] is not allowed to have the additional property "_"

I have repeated all steps twice and also used the completed forms provided in the latest pull request and still encountering this issue. Any help would be greatly appreciated.

XRM doesn't register new assembly

Lab/Demo: 06

Task: 02

Step: 04

After downloading the XRM Tools and extracting them, I'm able to launch the PluginRegistration application and log in using the Tenant credentials. But after logging in and selecting "Register New Assembly" from the "Register" drop down list, the PluginRegistration app stops functioning. No errors are received and the application itself never crashed, it just won't respond to any of the options in the "Register" drop down list. This error seems to be intermittent, only a portion of the class were affected.

Lab 01 - UI has changed, several issues

Lab/Demo: 01

Task: Various

Step: Various

Description of issue

This lab has some 'drift' between from what the instructions currently say, vs. what the UI now looks like. A sampling of issues are noted here:

1. Screenshots out-of-date, in particular where it used to have a 'tabbed' display horizontally, it now appears to have 'tabs' located vertically i.e. this:

Now looks like this:

2. General UI/text changes - that a user ought to be able to figure out themselves - but nevertheless should be updated at some point to match the updated UI: , i.e. '+Add Column' is now '+New Column', and 'Select Done' is now 'Select Save','Select Select Components' is now 'Select Select Objects'

3. More serious UI/text changes that are not so clear such as in Exercise 2, Task 1, Step 3 it says 'Select Required', however there seems to be a new dropdown with 3 addt'l options from which to choose. (I am guessing 'Business required' is desired here?

Another example in Step 5 is where it says 'Click on chevron icon next to Default'/'Select Custom for filter.'/'Select Save Table', but I am unable to find any 'Default', Custom or other area with such a chevron that allows me to select this option.

Issue with creating a new environment for admin.

Module: 01

Lab/Demo: 00

Exercise: 02

Task: 01

Step: 02

Description of issue
When trying to create the environment for the user, I get an error telling me that I'm not allowed to create a new trial site based on the license type. I believe Microsoft has recently changed the licensing model and it will now only allow me to pick a Production environment.

I can't continue until this has been corrected or a decision made on what type of environment to use.

Repro steps:

1

PL-400 Labs general comments

My view on the course is that it its purpose is to

a) Understand all the different methods by which the platform can be extended and for each of these
i. their capabilities
ii. their limitations
iii. where they run (client side or back-end)
iv. how they run (synchronous or asynchronous)
b) Know how to start developing with each method i.e. the tools required and code starting points

The course objective should be for students to be able to select the correct method to meet a requirement.

Note: I do not use the Exercises in Learn/Slides as these duplicate these GitHub labs.

As for the labs, the ones that are there are good (some fixes are required) and help the students meet the course purposes above. However, there are labs missing for:
• Module 3 Master advance techniques and data options in canvas apps
• Module 4 Automate a business process using Power Automate
• Module 5 Introduction to developing with Power Platform

One issue I have with the lab steps is that the copy and paste of each statement is very difficult to get right and many students end up spending ages trying to figure out where they made an error in copy/paste. I provide the completed code to students – these should be added to GitHub.

One key point is the labs build on each other and must be done in the numbered order, but the slides/modules do not reflect this order and I deliver module 6 (Extending the Power Platform Dataverse) after modules 7 (Extending the Power Platform user experience Model Driven apps) and 8 (Create components with Power Apps Component Framework).

Inspection Form

Module: 03

Lab/Demo: 00

Task: 05

Step: 02

Description of issue
Named on previous task as below
Task #4: Add Inspection Details Screen
Step 3: Rename the form "Inspection Form".
Repro steps:
Task #5
Step 2
Must be "Inspection Form" including space.
SubmitForm('Inspection Form'); Back(ScreenTransition.UnCoverRight);

XRMToolBox Early bound generation fails

Module: 6

Lab: 7

Task: 1.2

Step: 7

Description of issue

The XRMToolBox tool fails to login to environment and generate early bound classes.

Cannot complete Task 1.4 in Exercise 1 without the early bound files

Issue raised on XrmTollBox repo - see MscrmTools/XrmToolBox#1305

Outdated .Net Version

Module: 10

Lab: 11

Task: 2.2

Step: 01

Description of issue
The instructions refer to .Net 3. This version has not been supported by Azure for a long time and should be upgraded to .Net 6.
At the same time, Lab providers should no longer use Visual Studio 2019, but Visual Studio 2022, otherwise .Net 6 will not be supported.

The same applies to all other labs that rely on .Net 3 and Visual Studio 2019.

Lab 0: Ex 2: Unable to establish PowerPlatform Trial! : Entire class is dead in the water

Lab 0

Exercise 2 - Power Platform Trial

Task 2.1 - Sign up for a Power Apps per user trial

Step 7 - expand Billing and select Purchase services.

Purchase services does not exist and none of the other options seem to provide the functionality of the old Purchase services option. As a result, I cannot register the credential. That means students cannot access the Power Platform environment! Class starts Monday btw. Is there no one at MS coordinating changes to training materials?

CurrentUserService not found in ILocalPluginContext

Module: 00

Lab/Demo: 06

Task: 01

Step: 04

Description of issue
https://microsoftlearning.github.io/PL-400_Microsoft-Power-Platform-Developer/Instructions/Labs/LAB%5BPL-400%5D_Lab06_Plugins.html

"Build the project and make sure it succeeds. To build the project, right click on the project and select Build. Check the output and make sure that the build has succeeded. If it does not, go back and review your work compared the steps documented here."

Error at
localPluginContext.CurrentUserService.RetrieveMultiple

CurrentUserService not found in ILocalPluginContext

Repro steps:

1. Follow steps to Build the project.

PL-400 Issues

Practice Lab – Validate lab environment

This should be Next and not Save

Lab 01 – Data Modeling | Exercise #2: Create Tables and Columns | Task #5: Edit Status Reason Options | Step 3. In class view, this is still "Entities" instead of Tables.

Same section, this is still "Fields" and not columns:

Step 11 as well:

Lab 02 – Model driven app | Task #1: Edit Permit Form and View | Step 2

There needs to be steps of how to find the Permit Type column to drag and drop.

Lab 03 - Canvas App | Task #4: Add Inspection Details Screen | Step 3. This should be "Tree View" not "Three View".

Same section, step 5 the name and scheduled date already exist. Instructions need to read to add Status Reason and Comments:

Step 6 should read you will see an error message:

Lab 04 – Client Scripting | Task #4: Test Event Handlers | Step 3

In two test runs, we consistently get the following with the on-load permit form (this is post-clear and refreshing):

Lab 05 – Power Apps Component Framework | Exercise #1: Create the PCF Control | Task #2: Setup Components Project | Step 4

A new command prompt needs to be opened before running the PAC commands:

Lab 05 – Power Apps Component Framework | Exercise #2: Publish to Microsoft Dataverse | Task #3: Debug

F12 returned the following errors, making this task incompletable:

Lab 06 – Plug-ins | Exercise #1: Block New Permit Creation Plugin | Task #1: Create the plugin | Step 1

Suggestion: Add a note of which version of Visual Studio is in reference.

Lab 06 – Plug-ins | Exercise #1: Block New Permit Creation Plugin | Task #1: Create the plugin | Step 5

Screenshot does not display the the 'using' statements below the class. 'using' statements should be included at the start of the program.

Lab 07 – Azure Functions | Task #2: Create Application User and Security Role | Step 4

Full Name column is absent.

Exercise #2: Create Azure Function for Inspection Routing | Task #1: Create the Function | Step 2

The below output is made, contradictory to the one present in the instructional screenshot.

Exercise #2: Create Azure Function for Inspection Routing | Task #1: Create the Function | Step 3 (9)

Add a note at step 2(4) not to stop debugging else the below error will be present.

Lab 9:

Suggestion to put all code blocks in a type/text | code block. Example:

   ``` 
   private static Task<CRMGetListResult<ExpandoObject>> GetUsers(CRMWebAPI api)
    {
    var users = api.GetList<ExpandoObject>("systemusers");
    return users;
    }
   ```

Lab 9 | Exercise #3: Publish and Test | Task #1: Publish to Azure | Step 1

Due to the error above, publishing seemed unaccomplishable Lab 07 was finished prematurely and Lab 08 was continued.

Lab 08 – Publishing Events Externally | Exercise #1: Create an Azure Function | Task #1: Create Azure Function App | Step 1 (4)

Creating a new resource group requires a name.

Exercise #2: Configure Web Hook | Task #2: Create an Azure Function | Step 2

Suggestion:

Instructions to observe past logs should be included. Instructions unclear.

Lab 09 – Custom Connector | Exercise #3 Test Connector | Task #2: Test on Flow | Step 4

Connection must be recreated before step 4 can continue;

Lab 10 – Application Lifecycle Management | Exercise #3: Test the Pipeline | Task #1: Run the Pipeline | Step 1 (12)

Run did not execute successfully - 'Power Platform Export Solution' task failed to connect to environment. See error below;

Task #3: Run Build Pipeline | Step 2 (6) Jobs did not succeed due to above error.

Step 3(3) Due to earlier error reported

---

Suggestion/Ask: For the labs that have a majority of VS code entries, solution files be provided. That way if the end-user needs to compare what they may have done wrong, they can cross compare.

Lab 5 -Power Apps Component Framework

Module: 05

Lab/Demo: 05

Task: 02

Step: 07

Description of issue: You will receive a bunch or errors about code being deprecated.

Repro steps:

1.When you run : npm run build

Solution so far requires the following to be run first.
npm link typescript
then npm run build