Hello Kieran,

Thanks for the reply, In this approach, custom field mappings are stored in a system property, allowing flexibility in adapting the ETL definition during scheduled imports. While a basic mapping is predefined within the ETL application, users can extend it by adding custom fields without modifying the core configuration. During the import process, the ETL reads the system property and dynamically incorporates these additional fields, ensuring a seamless and adaptable data transformation process. This method enhances configurability, enabling users to tailor data mappings based on evolving business needs while maintaining the integrity of the standard ETL framework.

Hope this is clear for you.

Best regards,

Pethum