Skip to main content

Dear Experts,

 

I’m trying to build an Excel Migration job that would need to:

  • create some functional objects - EQUIPMENT_OBJECT_API
  • apply a parameter template after the functional object is created - Asset_Param_Template_Util_API.Apply_Template

Below is the Medthod List

 

The problem I have is how to pass EQUIPMENT_OBJECT_SEQ when applying the parameter template.

This method expects EQUIPMENT_OBJECT_SEQ which is created by method 10 - EQUIPMENT_OBJECT_API. However it seems that at the point of executing method20 the equipment_object_seq is not available.

In Mig Jobs - migrate source data it was possible to set a COMMIT rule - I was thinking if such a thing is possible for Excel migration - for example to commit after each method.

 

Any ideas how I could fetch the equipment_object_seq created through method 10?

​@dsj ​@Jens 

When I try to validate the Mig Job data in Excel I get no result / no error either. When I execute I also get no result. It’s like nothing happens. If I remove method20 and it’s attributes, the functional object is created successfully.

 

Hi Marcel,

 

Did you try passing the seq from method 10 to 20 in the method list attribute?

 

Kind regards!

Niyo 

Hi ​@Marcel.Ausan 

 

Values added as default are used in the generated select statement, which is used to fetch the values to use in the executions. Since the equip object record is not created by the time of the selection, you will get null from the select statement. 

But as ​@NiyomalN mentioned, data migration stores the attr (or procedure out/ function return values) which can be used in the later executions.

Syntax to use to access the values from attr: <item-name>@<method-sequence>

In your job, seq 10 will create a new record and the generated EQUIPMENT_OBJECT_SEQ is returned in the attr.

In order to use this for the next execution, go to the Method List Attributes in seq 20 and add the EQUIPMENT_OBJECT_SEQ@10 as the fixed value for EQUIPMENT_OBJECT_SEQ_

 

Hope it helps!

Damith

Terms & ConditionsCookie settingsAccessibility statement