Share
Report
2Dear Microsoft Dynamics 365 Community,
I am currently working on developing a custom extension for Commerce Runtime (CRT) in Dynamics 365 Commerce. My goal is to integrate my extension into the existing CRT environment. I have created the necessary components, including request handlers, triggers, and other runtime configurations. However, I am encountering some challenges in correctly deploying and integrating the extension into the CRT.
Here’s what I have done so far:
Developed the Extension:
Created a custom extension project in Visual Studio.
Implemented the necessary interfaces such as IRequestHandler and other required components.
Built the project to generate the corresponding DLLs.
Configured commerceRuntime.config:
I modified the commerceRuntime.config file by adding the necessary <add> elements under the <composition> section to include my extension assembly and types.
Updated manifest.json:
Included all the necessary details in the manifest.json file within my extension package.
Deployment Process:
I placed the compiled DLLs and configuration files in the appropriate directories within the Store Commerce installation directory.
Restarted the Store Commerce application to load the new configurations.
Important Context:
CSU Modifications: I am not planning to make any changes to the Commerce Scale Unit (CSU) at this stage. My goal is to observe and test the changes on a test device connected to an existing store setup.
Real Data Testing: I aim to work with real data in this test environment before eventually deploying the changes to the live environment.
Despite these steps, my extension does not seem to be recognized by the CRT, and I am not seeing the expected behavior when the runtime processes requests.
Questions:
Is there a step or configuration I might be missing when integrating a custom extension into CRT?
Are there specific logs or diagnostics tools within Dynamics 365 Commerce that can help me identify where the integration is failing?
What are the best practices for deploying and testing custom CRT extensions to ensure they are correctly integrated, especially in a scenario where I am not modifying the CSU?
I would greatly appreciate any guidance or recommendations from the community on how to successfully add a custom extension to Commerce Runtime in this context.
Thank you in advance for your assistance!
Best regards,
I am currently working on developing a custom extension for Commerce Runtime (CRT) in Dynamics 365 Commerce. My goal is to integrate my extension into the existing CRT environment. I have created the necessary components, including request handlers, triggers, and other runtime configurations. However, I am encountering some challenges in correctly deploying and integrating the extension into the CRT.
Here’s what I have done so far:
Developed the Extension:
Created a custom extension project in Visual Studio.
Implemented the necessary interfaces such as IRequestHandler and other required components.
Built the project to generate the corresponding DLLs.
Configured commerceRuntime.config:
I modified the commerceRuntime.config file by adding the necessary <add> elements under the <composition> section to include my extension assembly and types.
Updated manifest.json:
Included all the necessary details in the manifest.json file within my extension package.
Deployment Process:
I placed the compiled DLLs and configuration files in the appropriate directories within the Store Commerce installation directory.
Restarted the Store Commerce application to load the new configurations.
Important Context:
CSU Modifications: I am not planning to make any changes to the Commerce Scale Unit (CSU) at this stage. My goal is to observe and test the changes on a test device connected to an existing store setup.
Real Data Testing: I aim to work with real data in this test environment before eventually deploying the changes to the live environment.
Despite these steps, my extension does not seem to be recognized by the CRT, and I am not seeing the expected behavior when the runtime processes requests.
Questions:
Is there a step or configuration I might be missing when integrating a custom extension into CRT?
Are there specific logs or diagnostics tools within Dynamics 365 Commerce that can help me identify where the integration is failing?
What are the best practices for deploying and testing custom CRT extensions to ensure they are correctly integrated, especially in a scenario where I am not modifying the CSU?
I would greatly appreciate any guidance or recommendations from the community on how to successfully add a custom extension to Commerce Runtime in this context.
Thank you in advance for your assistance!
Best regards,
All responses (
Answers (
