REST API error - Cannot convert value to type 'ObjectIdentifier' when creating Parent link

Hi Fernando,

First, you no longer need to separately create a link to the parent. When creating new work items, you can specify parent as a field:

 "body": {

        "id": "/Task/ae35cd4b-ed6b-48b5-9ff5-de3da68cf635",

        "Description": "Test Description",

        "Name": "Test Rest",

        "Parent":  "/Task/0cbc02c2-48d3-4b1c-afa4-857723cb0b4b"

Second, you don't need to use "id:" for reference to object fields, this is only relevant when creating a new object, for the object itself. Thus the link creation message should look like this:

 "body": {

        "Child": "/Task/ae35cd4b-ed6b-48b5-9ff5-de3da68cf635",

        "Parent": "/Task/0cbc02c2-48d3-4b1c-afa4-857723cb0b4b"

        }

Hope this helps,

Ophir     

Hi Ophir,

I finally was able to do a complete test on this and I found out that the hierarchy workflow rules are not triggered when using the method you mentioned (putting the parent reference in the entity to be created instead of creating the link separately). Is this as designed? Because this completely breaks several workflows we had based on the notion of the parent link being created, but at the same time is very convenient not having to create the link separately.

Thanks in advance.

Hi Fernando,
Great to hear you managed the previous one.
As for the workflow rules, I took my own tests, but it seems the 'Parent' workflow rules DO run, (I particularly tested bulk REST API).

As you've sent detailed information and access to your account in the support ticket you've opened separately (you did a really good job on that!), I could look into the specifics in your account.
I think the workflow rules don't run because the conditions evaluate to false, meaning the Task data you've entered is the cause of the issue.
Specifically I could see the Forecast Task Type is not set. Could you look into the data sent with the API and the workflow rules again?
Hope this helps,
Ophir

Hi Ophir,

You are right, I had a bug in my code that wasn't populating the "Forecast Task Type" field. Once I fixed that, the workflow rule was triggered as expected and everything went fine.

Thanks for pointing that out and your quick support on this.

Regards.