Skip to main content

Hi everyone,

I’m currently facing an issue with Excel migration where empty values from the Excel sheet are overwriting existing data in our IFS application. Specifically, I want to prevent fields from being updated with empty values. For example, if the “DUNS No” field (column F) is empty, I don’t want it to overwrite the existing value in the application.

Here’s a simplified example to illustrate the problem:

Example Data:

 

ID Name Address City Country DUNS No
1 Company A 123 Street Kraków Poland 123456
2 Company B 456 Avenue Warsaw Poland  
3 Company C 789 Boulevard Gdańsk Poland 789012

 

In this example, for row 2, I want to update the application with the data from columns B-E for the corresponding ID, but leave the “DUNS No” field unchanged if it is empty, regardless of whether data exists in this field in the application or not.

Has anyone encountered a similar issue or have any suggestions on how to handle this in the migration process?

Thanks in advance for your help!

Hi ​@Martyna ,

I made a quick test on a 24R1 release and encountered the same issue. From my point of view the job should not overwrite the field to be empty when you do not provide any value. So I would suggest to raise a ticket for this topic.

BR
Martina

Hi ​@Martyna 

what if you put a NVL on the default value for DUNS No column in the mig job and fetch the value from the table/view by giving the keys. This way it will fetch the existing value if the value passing from the excel is null?

 

Regards,

Damith

Hi ​@Martyna 

what if you put a NVL on the default value for DUNS No column in the mig job and fetch the value from the table/view by giving the keys. This way it will fetch the existing value if the value passing from the excel is null?

 

Regards,

Damith



Yes, you're right. It's exactly how I resolved my problem. It's important to name the Migration Jobs/Source Mapping Source differently from the Column name — this is probably why it didn’t work the first time. It’s not a bug, it’s just how this functionality works, although it can be confusing.

Reply


Terms & ConditionsCookie settings