Onboarding and linking to a shared template doesn't seem to work.

[qc4vmware]

I need to import many thousand systems and I'd like them linked back to a central cloud template.  We have a project where we do most of our template development then share them out to various projects.  If I manually create an onboarding plan it I can only select templates that were created / owned by the project I'm attempting to import them to.  If I use the api I can set the template link but after the onboarding plan is run the link is not created.  This seems like a bug you should be able to map this to any valid template for the project.  If you execute a new deployment the template is linked correctly back to that shared template.  Anyone else encounter this?

[LuluTchab]

If you're using vRA8.18, it the "new way" to onboard VMs, unfortunately. I already had a call with 2 Aria Automation ProductManagers to show them the issue and they finally noticed that we have less possibilities than before to import VMs because of this but I don't know if this will be fixed.

Anyway, on my side, I just did things a bit differently:

1. Onboard VM inside the Project in which the linked CloudTemplate is
2. Call the "Change Project" Day2 Action on the imported Deployment to assign it to the right "final" Project.

It seems you're using the API, so can just add this step (change project) to your onboard process and it will work 😎

[qc4vmware]

Thanks for the suggestion and that will work.  Hopefully someone will eventually fix the on boarding utility.  I'll also need to add/remove zones to our image development project as I run through imports.  I've got about 30K to on board and it will be spread across several hundred projects ultimately but I can automate it.