Skip to main content

Anyone have luck using a Post Deployment process to change Routing Alternate or Product Structure Alternate from Tentative to Buildable in Data Migration Manager? I’m trying ROUTING_ALTERNATE_API.BUILD_ in this example. I can’t get it to fire off, no matter what settings I try. The Customer Order Status change is very straightforward in comparison, just requiring the ORDER_NO. I’m wondering if it has something to do with the migration not actually filling anything in for the OBJID or OBJVERSION. No idea what should go in the ATTR or ACTION sections.

 

Hi, 

On the above scenario, are you running the post deployment when you deploy data in deployment container?

 

 

I’m using the Post Deploy button on a per row basis, but yes.  It isn’t changing the Deploy Status like other Post Deploys Ive done so I feel like its not triggering the criteria at all.

Please check whether the OBJID is holding correct value and passing to the Build__ function. You need to give DO as action and don’t need to give any value for attr_.

Hi

 

I am having the same problem.
Has anyone else had this problem solved?

I could never get it to work.

I ended up just creating python scripts to run the build APIs for routings and product structures after the migrations finished.

Hi @dustin_arp

 

Thank you for your reply.

I see that the current functionality cannot handle this.
We will wait for a functional update...

 

Hi,

 

I share this information in case someone else has the same problem in the future.
I was able to update the status with the following settings.

(Sequence 4 is not required if set up in advance.)

settings

Reply


Terms & ConditionsCookie settings