Describe the bug
A clear and concise description of what the bug is.
The documentation suggests that after a Task has been created via the package, it can then be reassigned to a Queue "any other way you'd like...". I have tried to do this via the UI, via API, and via the packages invocable Apex class with a Flow, all of which is generating the same Error message:
LabsActionPlans.APTask: execution of AfterUpdate caused by: System.DmlException: Upsert failed. First exception on row 0 with id a461x0000009hmDAAQ; first error: FIELD_INTEGRITY_EXCEPTION, Assigned To: id value of incorrect type: 00G1x00000Aqu2PEAR: [LabsActionPlansUserc] (LabsActionPlans)
Could be something silly that I am doing or not doing, just hoping to have some feedback if you expect this to work or not.
To Reproduce
Steps to reproduce the behavior:
Create an Action Plan Template with Template Tasks
Create a Case, and then a new Action Plan using the AP Template
Tasks are successfully added to the Case, assigned to the users identified in the Template Tasks.
View one of the new Tasks, and change the Assigned To user to a Queue.
On Save, the error is generated preventing save.
Attempt to update the OwnerId on Task via API, get the same error.
Attempt to generate the Action Plan and update the new Tasks via Flow and invocable Apex action, get the same error.
If removing the Task relationship to AP Task, then the OwnerId can be changed to a Queue, but if reestablishing the relationship with AP Task will get the same error.
Expected behavior
Should be able to reassign the standard Task manually to a Queue via UI, API, or declarative automation such as Flow.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Describe the bug A clear and concise description of what the bug is. The documentation suggests that after a Task has been created via the package, it can then be reassigned to a Queue "any other way you'd like...". I have tried to do this via the UI, via API, and via the packages invocable Apex class with a Flow, all of which is generating the same Error message:
LabsActionPlans.APTask: execution of AfterUpdate caused by: System.DmlException: Upsert failed. First exception on row 0 with id a461x0000009hmDAAQ; first error: FIELD_INTEGRITY_EXCEPTION, Assigned To: id value of incorrect type: 00G1x00000Aqu2PEAR: [LabsActionPlansUserc] (LabsActionPlans)
Could be something silly that I am doing or not doing, just hoping to have some feedback if you expect this to work or not.
To Reproduce Steps to reproduce the behavior:
Expected behavior Should be able to reassign the standard Task manually to a Queue via UI, API, or declarative automation such as Flow.
Screenshots If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):