Hi @TheoB,

When creating the Excel migration job you have a rule named FETCHCONDITION. This is where you can join other tables but also add where clause conditions to fetch less data.

This is what the documentation says about this:

• FETCHCONDITION
  Keep this to Active if the job should have Query functionality from the Excel add-in (Query enabled jobs). If the job contains multiple logical units, this field should contain the join clause between the logical units.
  e.g. SUPPLIER_INFO.SUPPLIER_ID = SUPPLIER_INFO_ADDRESS.SUPPLIER_ID AND SUPPLIER_INFO.SUPPLIER_ID = SUPPLIER_ADDRESS.VENDOR_NO..

If you want to add additional filtering you can add it here as well. (e.g. SUPPLIER_INFO.COUNTRY_DB = ‘LK’)

https://docs.ifs.com/techdocs/21r2/045_administration_aurena/260_data_management/050_data_migration/030_migration_types/030_excel_migration/

Hope this helps.

Kind regards,

Michael

Hi @mmol,

Thank you for your answer, it's exactly what I needed!

However, I tried to fill in a condition: 

But Excel does not take into account the WHERE clause, it shows me all the customers.

Did I forget something? Something to refresh or to validate?

Thanks in advance!

Hi @TheoB,

Yesterday I was trying the same thing and found out that it seems not to be working in the IFS Cloud. A colleague of me pointed out the following community post about this:
 

It seems like a bug that it is missing as the documentation states it's one of the migration rules that should work. Howerver it was reported as a bug but not solved so far I know as I tested it yesterday in 22R1.

Kind regards,

Michael

Hi @mmol ,

we are on 21R2SU12 and it works for me, pls. see screenshots below, you just need to push button “Re-generate Excel Migration” after you update your migration job with the fetch rule condition.

BR Jan