10.5.2 - PartitionObjectId value ignored

I have a perl script that creates user templates, but it seems that the Partition value is getting ignored in 10.5.2. Here is an example of the POST I am sending:

<UserTemplate><Alias>Test Alias</Alias><DisplayName>Test DispName</DisplayName><PartitionObjectId>1a17728a-f212-4458-bd41-013fc2d37fc7</PartitionObjectId></UserTemplate>

I verified through the VMREST logs that the script is passing the correct partitionobjectid to Unity:

14:51:40.151 |10742,,,VMREST,3,DEBUG [http-bio-443-exec-23] com.cisco.connection.rest.impl.GeneratedUserTemplateRestImpl  - created subscribertemplate: SubscriberTemplateCreateTOImpl[partitionObjectId=1a17728a-f212-4458-bd41-013fc2d37fc7; (removed irrelevant content)

Now if we view the newly created template the incorrect partition will be listed:

<UserTemplate><URI>/vmrest/usertemplates/7f074b08-e553-408e-ab02-2cbf7b39b03e</URI><ObjectId>7f074b08-e553-408e-ab02-2cbf7b39b03e</ObjectId><Alias>Test Alias</Alias><DisplayName>Test DispName</DisplayName><PartitionObjectId>1182c9f2-ae76-4889-be44-8e2c43e018e4</PartitionObjectId><PartitionURI>/vmrest/partitions/1182c9f2-ae76-4889-be44-8e2c43e018e4</PartitionURI></UserTemplate>

I'm curious to see if anyone else can replicate this issue in their 10.5.2 cluster.

I tried this on 10.0(1) and it works ok, on my 10.5.2 the partitionObjectId value does not override - you have to do a subsequent update after the creation completes - looks like it's using everything from the template passed in and ignoring the additional parameters or override.

Nice idea for a workaround, I'll try it out and report back.