Update Custom Persistent Referenced field via Migration Job | IFS Community
Question

Update Custom Persistent Referenced field via Migration Job

  • 14 January 2022
  • 1 reply
  • 51 views

Userlevel 2
Badge +4

I want to setup a migration job (in IFS 10 update 11) to update a Custom Persistent Field on the Inventory Part.
I read – and followed - the recommendations in Topic https://community.ifs.com/framework-experience-infrastructure-cloud-integration-dev-tools-50/updating-custom-field-via-script-1728 and everything seems OK, but the record is not updated.

 

Set up a Job

  • of type MIGRATE_SOURCE_DATA, with Source Name INVENTORY_PART_CFV and - for testing purposes - scoped to one PartNo (which exists and is manually updatable – checked)
  • Rule ADDOBJID is set to Inactive:
  • Method list is as follows with a call to INVENTORY_PART_CFP.CF_Modify__

I did a debug of a manual update, which gives me the following information:


DECLARE
   -- p0 -> __lsResult
   p0_ VARCHAR2(32000) := NULL;

   -- p1 -> __sObjid
   p1_ VARCHAR2(32000) := 'AAAWZEAAGAAAKNLAAA';

   -- p2 -> __g_Bind.s[0]
   p2_ VARCHAR2(32000) := 'CF$_C_DELIVERY_ADDRESS'||chr(31)||'CD6ECD1F20B5485CB11B55F6B8FF4E3D'||chr(30);

   -- p3 -> __lsAttr
   p3_ VARCHAR2(32000) := '';

   -- p4 -> __sAction
   p4_ VARCHAR2(32000) := 'DO';

BEGIN
    IFSAPP.Log_SYS.Init_Debug_Session_('en');
    
IFSAPP.INVENTORY_PART_CFP.Cf_Modify__(p0_ , p1_ , p2_ , p3_ , p4_ );


 

So my source mapping is as follows (I set the values to hard coded values for testing purposes as using column names did not work). Trying to narrow the error options. 

 

 

Showing the Select Statement of the Migration Job also looks as expected:


SELECT 'AAAWZEAAGAAAKNLAAA',  'CF$_C_DELIVERY_ADDRESS' || CHR(31) || 'CD6ECD1F20B5485CB11B55F6B8FF4E3D' || CHR(30), 'DO' FROM IFSAPP.INVENTORY_PART_CFV WHERE PART_NO = '990000'

Select statement OK, parsed and executed for 1 row 
Length of statement : 176 characters


 

and finally, the job runs without any error:

But the column is not updated, checking the table in Oracle shows NULL-values. 

 

 

Anyone an idea what I am overlooking?

 


1 reply

Userlevel 2
Badge +4
Source mapping - sorry, had to remove it from my original post 

 

Reply