Hello IFS Community, Does anyone in the Community have a solution for the current Avalara issue? We are currently on Apps10 UPD22. We have received UPD26 but are unable to deploy because the integration with Avalara is broke. More details on the issue can be found in KB0083849. The fix can be found in UPD28, however, with Global Extensions, UPD28 won’t be available until late Aug - Sept. Thank you for your support. Mark B. KB0083849Avalara Integration Behavior and Compatibility in IFS Cloud and IFS Applications 10Article metadata. Revised by Pabasara Gunathilaka This article was updated• 8d ago8 days agoIntroductionSummaryThis article outlines the compatibility considerations and behavioral changes related to the Avalara integration in both IFS Cloud and IFS Applications 10. It specifically addresses the transition from SOAP to REST APIs in IFS Cloud, as well as the replacement of the deprecated Customer Usage Type with the Entity Use Code in both platforms.BackgroundAs part of the Avalara Connector Recertification initiative, IFS has introduced several updates to its Avalara integration across IFS Cloud and IFS Applications 10. These changes aim to align with Avalara’s latest standards and deprecations.In IFS Cloud:Starting from IFS Cloud 24R1 SU4, the integration replaces the deprecated CustomerUsageType with EntityUseCode, in accordance with Avalara’s updated requirements. From IFS Cloud 24R1 SU9 onward, Avalara integration mandates the use of REST-based API endpoints. The EntityUseCode is supported only in these REST-based integrations, marking a shift away from the legacy SOAP-based approach.In IFS Applications 10:Beginning with IFS Application 10 Update 26, EntityUseCode was introduced as a replacement for the deprecated CustomerUsageType.In Update 28 , the change was reverted due to the lack of support for EntityUseCode in SOAP-based messaging, thereby reinstating CustomerUsageType for compatibility.ExplanationDue to the changes introduced in IFS Cloud versions 24R1 SU4 and 24R1 SU9, as well as IFS Applications 10 Update 26 and 28, customers upgrading within this version ranges may encounter compatibility issues related to the Avalara integration.ResolutionTo avoid compatibility issues with Avalara integration in IFS Cloud, upgrade to one of the following versions that support REST API integration: 23R2 SU17, 24R1 SU11, 24R2 SU5, or 25R1 GA.For IFS Applications 10, it is recommended to avoid updating to UPD 26 and UPD27, as these versions may introduce compatibility issues with the Avalara integration. To ensure proper functionality and compliance, customers should update directly to UPD 28.Versions prior to UPD26 do not include the changes that cause these issues and are therefore not affected.

Avalara integration broke in Apps10 UPD26 need solution

Hello IFS Community,

Does anyone in the Community have a solution for the current Avalara issue?

We are currently on Apps10 UPD22. We have received UPD26 but are unable to deploy because the integration with Avalara is broke. More details on the issue can be found in KB0083849. The fix can be found in UPD28, however, with Global Extensions, UPD28 won’t be available until late Aug - Sept.

Thank you for your support.

Mark B.

KB0083849

Avalara Integration Behavior and Compatibility in IFS Cloud and IFS Applications 10

Article metadata. Revised by Pabasara Gunathilaka

This article was updated• 8d ago8 days ago

Introduction

Summary

This article outlines the compatibility considerations and behavioral changes related to the Avalara integration in both IFS Cloud and IFS Applications 10. It specifically addresses the transition from SOAP to REST APIs in IFS Cloud, as well as the replacement of the deprecated Customer Usage Type with the Entity Use Code in both platforms.

Background

As part of the Avalara Connector Recertification initiative, IFS has introduced several updates to its Avalara integration across IFS Cloud and IFS Applications 10. These changes aim to align with Avalara’s latest standards and deprecations.

In IFS Cloud:

Starting from IFS Cloud 24R1 SU4, the integration replaces the deprecated CustomerUsageType with EntityUseCode, in accordance with Avalara’s updated requirements.
From IFS Cloud 24R1 SU9 onward, Avalara integration mandates the use of REST-based API endpoints. The EntityUseCode is supported only in these REST-based integrations, marking a shift away from the legacy SOAP-based approach.

In IFS Applications 10:

Beginning with IFS Application 10 Update 26, EntityUseCode was introduced as a replacement for the deprecated CustomerUsageType.

In Update 28 , the change was reverted due to the lack of support for EntityUseCode in SOAP-based messaging, thereby reinstating CustomerUsageType for compatibility.

Explanation

Due to the changes introduced in IFS Cloud versions 24R1 SU4 and 24R1 SU9, as well as IFS Applications 10 Update 26 and 28, customers upgrading within this version ranges may encounter compatibility issues related to the Avalara integration.

Resolution

To avoid compatibility issues with Avalara integration in IFS Cloud, upgrade to one of the following versions that support REST API integration: 23R2 SU17, 24R1 SU11, 24R2 SU5, or 25R1 GA.

For IFS Applications 10, it is recommended to avoid updating to UPD 26 and UPD27, as these versions may introduce compatibility issues with the Avalara integration. To ensure proper functionality and compliance, customers should update directly to UPD 28.

Versions prior to UPD26 do not include the changes that cause these issues and are therefore not affected.

Be the first to reply!

KB0083849

Reply

Did you find what you're looking for? If not:

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded