Skip to main content
Question

Migration job for Connecting Delivery Unit to Dataset

  • May 6, 2026
  • 1 reply
  • 8 views
Do Gooder (Partner)
Forum|alt.badge.img+4

Hi,

Few weeks back I was able to insert the Dataset in the Delivery unit in Service Org screen but when I am trying to use the same job and same input file, the dataset are not importing.

What I Investigated is, table Service_Organization is not storing the datasets field now, but earlier it was there.

Not sure if IFS has made some changes, can anyone confirm what needs to be checked?

thanks in advance.

1 reply

Do Gooder (Employee)
Forum|alt.badge.img+4
  • danhse
  • Do Gooder (Employee)
  • September 14, 2026

Hi ​@nitesht,

Which version are you on?

This behavior might be due to the Dataset Segmentation architecture introduced in IFS Cloud 24R1.

Prior to 24R1, dataset IDs were stored directly on the Service Organization table. In 24R1, dataset mappings were decoupled from the organization header and refactored into the Resource Scheduling Dataset Segmentation framework (ResSchedDatasetSeg) to allow datasets to be assigned down at the Service Delivery Unit (SDU) level.

Because the dataset attribute is now a fetched field rather than a physical column on the Service Organization table, standard Data Migration jobs that target the Service Organization header view directly will execute successfully but silently skip the dataset field.

To resolve this:
Update your migration process to target the dataset segmentation mapping entities (ResSchedDatasetSeg) or populate dataset linkages using the corresponding projection endpoints/APIs (SetSerOrgDatasetId / SetServiceDelivery) after creating the Service Organization and Delivery Unit records.

Hope this helps!

Terms & ConditionsAccessibility statement