AJ Gregg Posted February 19 Share Posted February 19 FYI -- It looks like the 2024 Release 1 has a change to the Update AP Payment <APPYMT> API where <AMOUNTTOPAY> is required now when paying from a bank with a different currency than that of the transaction. The <AMOUNTTOPAY> always existed on Create and was required when paying from a bank with a different currency than that of the transaction, but <AMOUNTTOPAY> wasn't required and is not in the list of fields on the Update AP Payment API. The documentation for Update AP Payment does not reflect this change, yet. Link to comment Share on other sites More sharing options...
Sterio, Louis Posted February 20 Share Posted February 20 @Steve Nay Is this something we need to coordinate with the AP PM? 1 Link to comment Share on other sites More sharing options...
AJ Gregg Posted February 20 Author Share Posted February 20 I also created support case # 00640859 yesterday. The first reply was a little off base. They didn't really read my case notes. My concern is, we had to make a quick change to our code so our MPP Apps would work again. If Intacct removes this change without notice, it will break our app again. Link to comment Share on other sites More sharing options...
Sterio, Louis Posted February 21 Share Posted February 21 @AJ Gregg, That is concerning. Can you provide me the API call that worked prior to the release which is failing now? We should have a way internally to test this in the branch prior to R1. Also let me know the company ID we will need to copy it down to a dev box to test this in the prior branch. Link to comment Share on other sites More sharing options...
AJ Gregg Posted February 22 Author Share Posted February 22 Hi @Sterio, Louis, I attached an example that would have worked before. You can copy 'bt-smartfx2-test'. Thank you! update_APPYMT_Request.xml Link to comment Share on other sites More sharing options...
Sterio, Louis Posted February 22 Share Posted February 22 Thank you! I add this to my schedule to review right after transform. Link to comment Share on other sites More sharing options...
AJ Gregg Posted February 23 Author Share Posted February 23 @Sterio, Louis Thank you! I wish I was going to Transform, but unfortunately I can't make it this year. It would have been great to catch up with you. 1 Link to comment Share on other sites More sharing options...
Sterio, Louis Posted March 6 Share Posted March 6 @AJ Gregg I did not forget about this. I requested a copy to our dev environment which has the R4 release code base. Once I test and if I can confirm it did indeed work before without issues, I will work with the proper internal teams to make sure we have the proper process in place so this does not happen again. Luckily our REST API will have versioning so breaking changes will simply force a new version and we will have backwards compatibility with prior versions for a couple of years. Link to comment Share on other sites More sharing options...
Recommended Posts