Take a step back and think about what you are doing. You are not seriously using a column that takes YES or NO to determine a unique record?! That will never work, hence why you are getting an error. Think about what columns in your custom logical unit can you use to uniquely identify a record. Hi @Technical Outlaws Sorry I misunderstood- my bad.Identified the unique column and all working fine now :) Thanks
Even though the OBJKEY is technically the key to a record in a Custom Logical Unit, it is a GUID value that is not easily accessible or identifiable to a user. The reason you are getting the error is because you have nothing mapped to the key, during the migration update process this will cause problems since it fails trying to find a unique record. Therefore to determine a unique record in a Custom Logical Unit you need to define an Alternate Key(s). In your example above, for the Source Mapping you need to remove the K flag against the OBJKEY and set it to be I instead. Then you need to decide which column(s) that has a source column mapped should be the Alternate Key(s) instead and change its flag to be K. I believe what happens in the migration update process is that the logic will use the columns flagged as K to determine the OBJKEY in order to fetch the record for update. Hi,Thanks for your reply. I’ve changed the OBJKEY flag to I and CF$_EXPORTED_DB as K but unfortunately
When it comes to migrating custom logical unit data, it has to be defined in that way. See https://docs.ifs.com/techdocs/Foundation1/040_administration/260_data_management/050_data_migration/003_data_migration_in_custom_objects/090_custom_lu/default.htm for more information. In your setup I see both source and destination setup to the same custom logical unit - correct me if wrong. If that's the case from where you are going to migrate these data from? Or is this for a different purpose like to have a default value only? Hi RusiruThanks for your reply. I am not using two-stage migration job (i.e. not migrating data from any file) but trying to update Exported column as YES (by hard coding) on migration job itself.Kind regardsDinesh
Hi Not sure how your file configuration looks like but it’s worth try and changing the String Delimiter field. Regards/D
Hi Guys Wondering if someone can help me with a data migration query. Scenario: As a part of Customer data migration, i am also looking to migrate Address types (Pay, Delivery and Document which is coming from view- CUSTOMER_INFO_ADDRESS_TYPE) Created a migration job to insert new Customers, Addresses and Address types (third highlighted view as below) Migration job works fine and creates first default value i.e. Pay But to pass other two default values (Delivery and Document) I am replacing Pay with other two one- by-one and running the same job few times. Is there any easier way to pass all three value once so that i don’t have to run the same job thrice? Thanks in advance /D You need to add multiple records for CUSTOMER_INFO_ADDRESS_TYPE_API in the method list for the address type. There are a few different ways you can set this up. You can use the CUSTOMER_INFO_ADDRESS_TYPE_API.NEW__ and RMB to method list attributes and hard code the a
Or you could just run a script to add the address types if you have access to the run a script. Note: The attached scripts do not display error messages if unable to add the address type record. Thanks. Was looking to migrate using IFS migration job only (as per the requirement) but thanks for the tips :)
Managed to find that but thanks for your reply @Rusiru!
HiIs it possible to find a list of warning message supported LUs somewhere in IFS or by some other means?I am trying for LU- OrderQuotationLine where error message works fine but not the warning message so just wanted to confirm. ThanksDinesh
Thanks all for taking time to reply.Went through Permission set way and all working fine now :)Regards
Hi @Mike.Hollifield - Thanks for your reply. Unfortunately, that didn’t work either.Regards
All sorted..thanks for your help @durette
Hi @crpgaryw - Did you find any solution to this by any chance? I got a same issue where i can raise an error message on Apps 7.5 without any issue but struggling with warning message. ThanksDinesh
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
