D365 Commerce making changes to Adyen payment and service connector considerations

 Hello all, 

I wanted to make a quick note about changing Adyen account and payment connector settings within Dynamics 365 Commerce. From time to time, you'll need to make changes to account or payment connector settings in Dynamics 365 Commerce as a result of an upgrade.

The way that things work, you can make these changes but you need to make sure you invoice all orders and capture payments (so the system shows no outstanding funds due), and then change the settings. 

By failing to do that, you'll run into an incongruence of payment settings between the previous authorizations with the old configs vs the new configs using the old authorizations. 

This will obviosuly be a very big trick when you look into online ecomm orders coming in bound, orders in multiple statuses, etc. You almost need a hard stop on new orders being authorized for payments, or temporary change the process to collect payments up front, which is usually not possible. 

So looking at this dilemma, it might seem unrealistic to making any config changes to the Adyen Dynamics 365 Commerce settings. But what if you have to and can't stop the flow of orders?

For one potential solution, you could create a tool that can be used to update the current open authorizations after the config change is made. This will allow you to make the change in PROD and then create new auths as needed. For open authorizations after that change is made, apply your tool to update those open records to accommodate the new configs. 

If you wait and those open auths expire, sometimes as early as 7 days, you'll have to recapture the payment either manually or via a reauth if you have card on file.

So the lesson here is to get ahead of correcting the open auths if you can't put a hard stop to your order/payment flow. 

Hopefully this post will help proactive dialog for those who encounter this uncommon, hopefully rare scenario. 

What I've been up to in past few years and new company: Illumina Technology Solutions

Hey everyone! I have not kept up on my promise to produce more content from my blog under DAXDude. The past two years have been crazy, ala literally everyone in the world via COVID.

However, I do owe everyone who has hit me up a collective response to what has happened over the past few years causing me to not blog as much. 

That and I wanted to wish everyone a happy new yea 2023. 

March 2020 - A new Baby+COVID world

On March 10th, 2020, my wife and I went into the hospital to welcome our second child, Colette. We entered in a world of caution and uncertainty, but the same day to day as March 10th 2015, and left the hospital on March 14th in a world of turmoil and masks and hazmat suits. 

August 2021 - Blue Horseshoe Acquisition by Accenture

In July, I caught word that we would be selling the company that I started with who had 25 people at the time and then got 

June 2022 - New company: Illumina Technology Solutions

I started a new company called Illumina Technology Solutions with several other highly talented people. I'm able to truly pursue my passions and work with others that are also 'rockstars' in their area. We are trying to address the pains in the D365 community most companies have, such as taking routine updates, security, regression testing, support, ecommerce and POS, etc. We'll have a heavy focus in D365 Commerce as that is the background of our group, but we have deep understanding and experience in the other areas of the system.

Already, we have been able to jump into a few accounts as well as assist a few partners in helping to grow their companies. I anticipate significant growth as we continue to establish ourselves as industry experts that are incredibly partner friendly and focus on the thing that matters: sustainable and successful customer implementations. 

Its been a lot of work starting the company and trying to lay a solid foundation for accelerated growth in a sustainable way. I'm CTO which has put a lot on my plate in addition to family stuff. I'll try to post more on this site as these do help people in the community and I think more non-Microsoft content needs to be created again. Things change so much but with D365, I think a lot of the 'debug' and 'error' type situations aren't covered as much. So I'll try to patch those gaps in here as I encounter them.

Happy new year 2023!

Happy Dax'ing

~DAXDude

Solved: D365 Fields automatically populating on form errantly - Due to a Chrome addin

So here is an interesting post that I hope will help someone out with. I'm going to add some keywords in here too that might match what someone is looking for when looking for something along the lines of "Dynamics 365 Finance/Commerce/Supply Chain Form fields overriding:

There was a scenario where, in production, a user was seeing data mysterious change to an old test server and login credentials. The user would continuously need to go into the system and reset the credentials and server IP for the integration to work. We were not sure if it was a person, a batch process, etc. 

We found out that the issue was on the form itself, and whenever a user went into that form and made some kind of action such as expanding tabs or right clicking and selecting personalization. It would overide the data on the fields, not in the table itself. The data would only actually commit to the tables when the form was saved. 

After a lot of debugging, we found the issue: A Chrome Web browser addin (LastPass). There was an entry that would recognize the form and automatically default data, much like you would if you were entering credentials for a login page or an address. 

There were no indicators or form popups indicating that the fields were being auto-populated. They were just occurring which led the original mystery of why this was happening. Very concerning as all you really needed to do to mess up the data was go into a page and make some kind of action, including non-data related actions. 

Debug tip if you're seeing something similar: Turn off all add-ins on your browser and see if you can replicate the issue. Or compare if other users are seeing similar issues. 

Happy Dax'ing!

~DAXDude