Custom REST Destination error - Provided property key is not valid

13 views
Skip to first unread message

David Rinell

unread,
Sep 30, 2025, 5:01:27 PMSep 30
to COZYROC
I am trying to get a custom REST destination working.  I successfully created the REST commection manager, imported from Swagger, and tested the connection successtully after setting up basic authentication via a Bearer Token.

When I run the data flow I get the following error for every row:

[AssetCustomFields [2]] Error: System.Exception:
(1) {"":["Provided property key is not valid for the AssetCustomFieldPatchRequest."]}
...

   at CozyRoc.SqlServer.SSIS.RestDestination.#=zoBaoLlNB404t(ArrayList #=zdvMETOXD1lMP, IStatus[] #=zKre1hy0=)
   at CozyRoc.SqlServer.SSIS.RestDestination.#=zfAaXwG0=(ArrayList& #=zdvMETOXD1lMP, ArrayList& #=zBX7XLyDYyXEQ)
   at CozyRoc.SqlServer.SSIS.RestDestination.#=z$7BNokonuYkv()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at CozyRoc.SqlServer.SSIS.RestDestination.PostExecute()
   at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPostExecute(IDTSManagedComponentWrapper100 wrapper)

The API doc is here: 

I have been able to call the same endpoint (AssetCustomFields) using Postman and everything works fine.

Any ideas why this isn't working?

Thanks


David Rinell

unread,
Sep 30, 2025, 9:45:34 PMSep 30
to COZYROC
I figured out what the error is - I just can't figure out how to fix it

The REST destination is putting all the JSON in the body - the API is expecting the key parameter in the querystring and the other fields in the body of the request  

HOW do I configure the resource(s) to do it this way?

Ivan Peev

unread,
Oct 1, 2025, 8:09:10 AMOct 1
to COZYROC
Hi David,

Configure your key field with the attribute IsKey="true" . Did it work now?

David Rinell

unread,
Oct 1, 2025, 8:27:28 AMOct 1
to COZYROC
Where do I do that?  I don't see that "key" attribute anywhere

Ivan Peev

unread,
Oct 2, 2025, 7:59:44 AMOct 2
to COZYROC
David,

In the custom configuration you are creating. It is an attribute of the Field element.

Reply all
Reply to author
Forward
0 new messages