Supply chain | Supply Chain Management, Commerce

Issue in automatic deployment of payment connector

(0) Share

Report

Posted on by MarijSiddiqui

I have created an assembly 'A' implementing IPaymentProcessor and another 'B' implementing INamedRequestHandler.

To create a retail deployable package, I have placed my assemblies A and B in "PaymentExternals /IPaymentProcessor assemblies" and "PaymentExternals/IPaymentDevice assemblies" respectively, in retail sdk folder. I am successfully able to apply my package via LCS into my environment.

Issue is, my processor is successfully loaded and I am able to see it among existing connectors in Retail Hardware Profile form. But no sign of assembly B in modernPos' clientBroker or hws' packages folder, needed for payment terminal device at mpos end.

I have tried this twice on two different environments following the deployment steps in commerce docs. Which brings me to my question, is this process of pushing payment connector via LCS applicable for INamedRequestHandler assemblies? or does this work for IPaymentDevice assemblies only? Or am I missing something? Has anyone successfully deployed payment connector via LCS?

Thanking you in anticipation.

I have the same question (0)

All responses (6)

Answers (0)

Ramune on at

Like (0)

Report

Hi Marij,

I leave this question for community to be responded. We will verify and if any information is available, we respond to you next week.

Was this reply helpful? Yes No
Terrance Morgan 515 on at

Like (0)

Report

Kindly refer to the following for the queries related to the automatic deployment of the payment connector in Dynamics CRM.

docs.microsoft.com/.../deploy-payment-connector

--

Terrance

CRM Admin | Apps4Rent

Was this reply helpful? Yes No
Suggested answer

Oksana Kovaliova 3,597 on at

Like (1)

Report

Hi, did you register DLLs in

1) Customization.settings, as ISV_HardwareStation_CustomizableFile - this will include them into HW station and POS packages

2) To make POS and HW station to load INamedRequestHandler library, it must be declared also in HardwareStation.Extension config file

Was this reply helpful? Yes No
MarijSiddiqui 10 on at

Like (0)

Report

Hi Ramune,

Thank you so much, I will wait for your response.

Kind regards,

Marij

Was this reply helpful? Yes No
MarijSiddiqui 10 on at

Like (0)

Report

Hi Terrance,

I have followed this document. Were you able to successfully deploy INamedRequestHandler/IPaymentDevice implementation using this document only?

Kind regards,

Marij

Was this reply helpful? Yes No
MarijSiddiqui 10 on at

Like (0)

Report

Hi Oksana,

Thanks for helping out.

I did add my extension assembly in both of the locations you provided. i.e

in RetailSDk/BuildTools/Customization.settings and in RetailSDK/Assets/HardwareStation.Extension config

I reapplied the package to my environment and downloaded+installed HWS from store, but HWS station in ProgramFiles(x32) does not contain my extension assembly, neither in /bin or in hws.extension config.

I wonder if I am missing something else.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Issue in automatic deployment of payment connector

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Supply chain | Supply Chain Management, Commerce

Featured topics

Product updates

Community site session details

Issue in automatic deployment of payment connector

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Supply chain | Supply Chain Management, Commerce

Featured topics

Product updates