Skip to main content
Question

I want to perform a full clone using the IFS cloning process.

  • July 31, 2026
  • 1 reply
  • 44 views
Sidekick (Partner)
Forum|alt.badge.img+4

When cloning from the PRD environment to the CFG environment using "Clone Environment" in Environment Studio, data for certain custom events remained in the CFG environment instead of being deleted.

Upon contacting support, I was informed that the following tables are excluded from the refresh process due to refresh rules:
     FND_EVENT_ACTION*
     FND_EVENT*
     Custom extension tables
     Configuration tables

I would like to know how to configure these refresh rules, but I haven't been able to get an answer; if anyone knows how to do this, please let me know.
My goal is to refresh all tables so that the data in the target environment is exactly the same as in the source.

I saw a similar issue mentioned in another post, but I am asking this question because I do not know the specific steps required to resolve it.

 

IFSクラウドクローン|IFSコミュニティ

IFS最適化フレームワークにおける背景処理 - IFSクラウドの技術文書

PSOでIFSクラウドをクローン(DBからPSOを無効に) |IFSコミュニティ

1 reply

Navinth Bakmeedeniya
Hero (Employee)
Forum|alt.badge.img+14

As far as I am aware, there is no such configurability (to override the default behavior of this) provided by the cloning process. Perhaps ​DB Services team in Platform (Jennifer Tawiah / Mykyta Kushniruk) may confirm.

When it comes to why this behavior present for events is, mainly due to event related metadata may contain environment specific configuration (suhc as URLs, etc), so that if you do clone them as well, at many customers, those resulting event metadata could be of less value, so that they need to reconfigure them against the ones you already had previously. Considering this majority scenario, we have implemented this way, so that the majority of the customers have to do less re-work of these configs after cloning.

However, providing more configurability here to override the default, perhaps to toggle the current behavior (of 'keeping event related metadata') manually by the customer when ordering a clone could be a useful functionality. The feasibility of integrating such capability into the existing cloning pipelines needs to be further investigated by the DB Services team in Platform.

Terms & ConditionsAccessibility statement