10-28-2022 06:21 AM
I am implementing Transaction Matching version OFCpv710sv100. I have a very simple data source definition and can load to stage successfully. As soon as I enable the statements in Transformation Event Handler, so that transactions are imported into TXM tables, an exception is thrown: Description: Business Rule error. TransformationEventHandler.
Several errors are thrown, and the following detail is provided in one of them:
Description: Operand type clash: uniqueidentifier is incompatible with smallint
Error Time: 10/27/2022 10:18:29 PM
Error Level: Error
Tier: AppServer
Application: Test - 09092022
App Server: vmDEV1App1
App Server XF Version: 7.1.3.14022
Session ID: a755547f-bd5c-4445-988b-075c6a071b92
Error Log ID: 9f6b5662-ae9b-43a8-bb67-22ac56b38872
Has anyone else seen this, and if so, is there a resolution? I've logged a support ticket as well and if I get an answer, I'll update this post. Thanks
Heather
Solved! Go to Solution.
11-01-2022 05:41 AM
Ok, here's what I know so far. It appears to be a bug impacting OFCpv710sv100, if you upgrade directly from OFCpv630sv100 (unsure about whether it impacts upgrades from prior versions). Safest bet right now, if you are on pv630sv100 and planning to upgrade to pv710sv100, is to upgrade first to pv640sv100 or 660sv100, and THEN upgrade to pv710sv100.
10-31-2022 11:15 AM
Hey Heather, thanks for logging a ticket. Hopefully they'll find a fix!
11-01-2022 05:41 AM
Ok, here's what I know so far. It appears to be a bug impacting OFCpv710sv100, if you upgrade directly from OFCpv630sv100 (unsure about whether it impacts upgrades from prior versions). Safest bet right now, if you are on pv630sv100 and planning to upgrade to pv710sv100, is to upgrade first to pv640sv100 or 660sv100, and THEN upgrade to pv710sv100.