-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
Try to use an A4J rule, using Smart Values to set an Object's reference Type Attribute (object) with multiple objects, using Smart Value: lookupObjects.
According to the Audit log, the Action is attempting to set the attribute with the combined values, using = and not IN () hence the action fails.
This is reproducible on Data Center: no
Steps to Reproduce
- Configure Object Type A to have an Object Type Attribute to reference Object Type B, with Cardinality Max >1
- Make sure you have a few objects in Object Type B
- Configure an automation rule:
- When, Object Created
- Use the Action "Lookup Objects" with IQL: objectType = "Object Type B"
- add an Action; Edit Object Attribute, edit the "Object Type A" Attribute to reference "Object Type B" with any of these smart values:
{{lookupObjects}} {{#lookupObjects}}{{Key}}{{/}} {{#lookupObjects}}{{Key}}{^last}}||{{/}}
- Create an Object of the type A
Expected Results
The New object is referencing ALL the Object Type B Objects
Actual Results
If there are more than 1 objects in the lookupObjects smart value - No Object Type B objects are referenced, the Automation results in :
Edit Insight field attributes Error updating Object(s) Attribute value is not valid on Objects PFNL-19749 (Network Location = PFNL-17346, PFNL-17347)
(this error results from lookupObjects
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available