[midPoint] assignmentTargetSearch "null polystring orig" error

[Devin Rosenbauer]

Version is 3.3.

I've got the following in my user template, based on a somewhat modified
version of what's in the documentation online:

  <mapping>
      <source>
         <c:path>$user/givenName</c:path>
      </source>
      <expression>
         <assignmentTargetSearch>
            <targetType>c:OrgType</targetType>
            <filter>
               <q:equal>
                  <q:path>c:name</q:path>
                  <q:value>
                     <expression>
                        <path>$givenName</path>
                     </expression>
                  </q:value>
               </q:equal>
            </filter>
            <createOnDemand>true</createOnDemand>
            <populateObject>
               <populateItem>
                  <expression>
                     <c:path>$givenName</c:path>
                  </expression>
                  <target>
                     <c:path>name</c:path>
                  </target>
               </populateItem>
            </populateObject>
         </assignmentTargetSearch>
      </expression>
      <target>
         <c:path>assignment</c:path>
      </target>
   </mapping>

I expect that this would create an Org called "Devin" and assign the user
to it.

Here's what I get as an error message when I attempt to save and reconcile
the user:

   - Failed to convert query. Reason: Null polystring orig in XNode(map:1
   entries)(givenName=PPV(PolyString:Devin); ) in expression in mapping in
   objectTemplate:c0c010c0-d34d-b33f-f00d-777222222334(User Template 2)
   - operation.com.evolveum.midpoint.web.page.admin.PageAdminFocus.save
      - *Cause:*

      Failed to convert query. Reason: Null polystring orig in XNode(map:1
      entries)(givenName=PPV(PolyString:Devin); ) in expression in mapping in
      objectTemplate:c0c010c0-d34d-b33f-f00d-777222222334(User Template 2)

The documentation on the Expressions page and the samples appear to be
somewhat incorrect here. I've had to make some corrections from <query> to
<filter>, adding a <source>, and so forth. I also am temporarily using an
OOTB field instead of a custom field to ensure that it's a PolyString and
not an xsd:string, just to make sure that wasn't the issue.

At this point, it seems pretty clear that it is grabbing the value in the
XNodeMap, since it's printed in the error message.

So, how should this mapping be structured to do what I need to do?

-- 
Devin Rosenbauer
Principal Consultant
Identity Works LLC
+1 585 210 3201
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20151201/aa0769ab/attachment.htm>