You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a dataview through CJA API the owner property is not set to the specified one in the request body.
Instead the owner seems to be set to the account that is used for authorization against the API.
However, PUT /data/dataviews/:dataViewId?expansion=name,owner with a specified owner in the request body works fine.
Steps for reproducing:
POST /data/dataviews?expansion=name,owner
with a defined owner (other than the account used for auth against the api) in the request body.
The owner is set to the account used for auth against the API
The text was updated successfully, but these errors were encountered:
Hi @lukkyluke, Response from developer: "The owner used in the body is overridden by the user making the request. We don't allow a user to create a dataview for someone else. (We have other unexposed endpoints for that.)" I hope that helps. Thanks for using the API services.
Thanks for coming back to me @johnwight
Okay, I understand. However I don't get the logic why updating with a different owner should be allowed but not when creating.
In the case you want to stick to the current behavior, the documentation maybe should be updated so that the owner is not a part of the request object on POST (create)?
URL of documentation issue
https://developer.adobe.com/cja-apis/docs/api/#tag/Dataviews-API/operation/createDataView
Description
When creating a dataview through CJA API the owner property is not set to the specified one in the request body.
Instead the owner seems to be set to the account that is used for authorization against the API.
However, PUT /data/dataviews/:dataViewId?expansion=name,owner with a specified owner in the request body works fine.
Steps for reproducing:
POST /data/dataviews?expansion=name,owner
with a defined owner (other than the account used for auth against the api) in the request body.
The owner is set to the account used for auth against the API
The text was updated successfully, but these errors were encountered: