Knockout.js is not Loaded in D365FO MPOS/CPOS Extension Project Successfully / How to import Knockout.js in POS Extension.

 

Knockout.Js

How to Import Knockout.JS in POS Project.

If the Knockout.js is not loaded automatically ApplicationStartTrigger & BirthdayFieldsSection packageform AMER POS is not loaded successfully in POS



Solution:

Reference: https://learn.microsoft.com/en-us/dynamics365/commerce/dev-itpro/pos-extension/knockout-pos-extension

Refrence:https://github.com/microsoft/Dynamics365Commerce.InStore/blob/release/9.28/src/PosSample/Pos.Extension/Pos.Extension.csproj

Go to POS Project Right Click and unload it. See the project Source

Add KnockoutjsFile in PropertyGroup Element


<PropertyGroup>

    <TargetFramework>netstandard2.0</TargetFramework>

       <KnockoutjsFile>Libraries/knockout.js</KnockoutjsFile>

  </PropertyGroup>

 

 

Also add Target Element

<Target Name="ContentIncludeKnockoutLibrary" BeforeTargets="AssignTargetPaths" DependsOnTargets="RunResolvePackageDependencies">

             <PropertyGroup>

                    <KnockoutLibraryFilePath Condition="'%(PackageDefinitions.Name)' == 'knockoutjs'">%(PackageDefinitions.ResolvedPath)\Content\Scripts\knockout-%(PackageDefinitions.Version).js</KnockoutLibraryFilePath>

             </PropertyGroup>

             <Copy SourceFiles="$(KnockoutLibraryFilePath)" DestinationFiles="$(KnockoutjsFile)" SkipUnchangedFiles="true" />

             <!-- Necessary for CPOS -->

             <ItemGroup>

                    <Content Include="$(KnockoutjsFile)"></Content>

             </ItemGroup>

       </Target>




Final Result link This

<Project Sdk="Microsoft.NET.Sdk">
  <Import Project="..\CustomizationPackage.props" />

   <PropertyGroup>
    <TargetFramework>netstandard2.0</TargetFramework>
    <KnockoutjsFile>Libraries/knockout.js</KnockoutjsFile>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.Dynamics.Commerce.Sdk.Pos" Version="$(CommerceSdkPackagesVersion)" />
    <PackageReference Include="Microsoft.TypeScript.MSBuild" Version="4.0.*" />
  </ItemGroup>

  <ItemGroup>
    <ProjectReference Include="..\CommerceRuntime\CommerceRuntime.csproj" />
  </ItemGroup>

<Target Name="ContentIncludeKnockoutLibrary" BeforeTargets="AssignTargetPaths" DependsOnTargets="RunResolvePackageDependencies">
    <PropertyGroup>
        <KnockoutjsFile>Libraries/knockout.js</KnockoutjsFile>
        <KnockoutLibraryFilePath Condition="'%(PackageDefinitions.Name)' == 'knockoutjs'">%(PackageDefinitions.ResolvedPath)\Content\Scripts\knockout-%(PackageDefinitions.Version).js</KnockoutLibraryFilePath>
    </PropertyGroup>
    <Copy SourceFiles="$(KnockoutLibraryFilePath)" DestinationFiles="$(KnockoutjsFile)" SkipUnchangedFiles="true" /> <!-- Necessary for CPOS -->
    <ItemGroup>
        <Content Include="$(KnockoutjsFile)"></Content>
    </ItemGroup>
</Target>

</Project>




 

Comments

Post a Comment

Popular posts from this blog

Update Deployment Failed due to Missing MpProvider Module

 While upgrading a Tier-1 development environment, the deployment failed with the following error: The specified module 'C:\Program Files\Microsoft Security Client\MpProvider' was not loaded because no valid module file was found in any module directory. Cause: This error indicates that Visual Studio cannot locate the MpProvider module, which may be due to outdated or incomplete installations of Visual Studio. Resolution: Upgrade both Visual Studio 2019 and Visual Studio 2022 to their latest versions. This ensures all required modules are installed correctly. 🔧 Steps to Upgrade Visual Studio For Visual Studio 2019: Open Visual Studio Installer from the Start menu. Locate the Visual Studio 2019 entry. Click Update (if available). Follow the installation prompts. Restart your machine after installation. Launch Visual Studio 2019 to confirm the error is resolved. For Visual Studio 2022: Open Visual Studio Installer . Locate the Visual S...
Read more

How to Resolve DVT Script Issues When Applying Quality Updates in LCS for D365FO

Image
 Recently, while applying Quality updates 39, I encountered an error stating  " DVT script for service mode: AOSService on machine. " Upon examining the error logs, I found the description: "ERROR: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel." After some research, I discovered a solution: First: Abort the current process in the Lifecycle Services (LCS) as this option is only available for environments in the Deployed state.  Second: Then, navigate to the Environment details page, click Maintain, and select Rotate secrets. Choose Rotate the SSL certificates and confirm the action.  This simple solution resolved my problem.
Read more

How to remove deployed model in Tier2 environment in D365FO

 How to remove the deployed model in the Tier2 environment Dear all, I have an issue with the deployed model in the D365FO Tier 2 environment. I have some models in the development environment: Model A Model B Model C Model D I want to apply only Models A, B, and C for the Tier 2 environment. For the first time for deployment, I created a deploy package(including Model A, B, and C) in development and applied an update for the Tier 2 environment. However, yesterday, developer X on my team deployed a new deployment package(Model A, B, C, D). So today I could not deploy the package in Tier 2 with Models A, B, and C. Solutions: 1. Download the same package from the Asset Library that was previously deployed. Add File ModuleToRemove.txt (with model listed). Reupload to Asset Library and deploy to UAT. When I do this,  there's a warning on LCS that "it will first reinstall the model and then delete it. In order to not reinstall, delete the model from the package." 2. Create a n...
Read more