It seems that this problem comes from the “merge” feature, but I don’t fing any doc about the effect of the merge on the source connection

Hi ​@SimonP 

Kindly note that when merge functionality is used, the actual connection is between the PM Action maintenance plan line and the Work step. If you check the work steps, source connection details are updated. But for the Work task, since it have steps that have connection to many PM Actions, it does not update the source related details - Source connection / Source ID, Source Ref fields etc. However, the PM Group ID will be updated as it is common for all the steps created in the work task.

Hope this helps.

Best Regards,

Thilini

Hi Thilini, 

Thanks for your help. Why is it working like that ? Because I understand that the merge will link steps to the PM action, but the WT and the WO are also created regarding these PM action.

Kind regards

Hi ​@SimonP 

You are most welcome.

I think this is because the fields “Source connection” and “Source ID” are updated together. So, for the work task created from merged PM Actions, a unique value cannot be given for the “Source ID” (PM Action ID) because it has many source IDs (PM Actions) connected. Due to this, the source related fields are kept empty.

When it comes to Work order, anyway the source connection cannot be specified because a work order can have many tasks created in the work order itself or created from many PM Actions. Therefore, no unique source connection/source ID is specified.

Best Regards,

Thilini