How to change ownership of an API prorject? | Adobe Higher Education
Skip to main content
M
myradio_digital
Level 2
December 21, 2021
Resuelto

How to change ownership of an API prorject?

  • December 21, 2021
  • 2 respuestas
  • 2951 visualizaciones

Hi, I'm trying to find out how to change the ownership of an API porject from one account to another. In this case I want to change the ownership of a project I've created to another account. Is the ownership shared for all the users in the subscription or must be shared or changed like the assets of the workspace projects?

I'm also wondering if one account is deleted if the project will still work or does it need to be created again?

Este tema ha sido cerrado para respuestas.
Mejor respuesta de jlinhardt

Hello.  Thanks for getting back to me.

 

I think the biggest hurtle you will have will be have the correct 'access rights'.

 

Meaning, when i created a new workspace project via the API, it was assigned to my 'techAccount' email address which is different than my Adobe Analytics Log In email address.  So I was able to use a PUT url of "https://analytics.adobe.io/api/mcdona4/projects/{{project_id}}" and a body script of 

{
    "rsid": "{{rsid}}",
    "owner": {
        "id": "{{ownerId}}",
        "name": "{{ownerName}}",
        "login": "{{ownerLogIn}}"
    }
}
to transfer the project from my Tech Account over to my Adobe Analytics Account
 
but if I tried to reverse the ownership (meaning transfer from my Adobe Analytics Account back to my TechAccount) i get a 'insufficient access' error.  because the asset is no longer under my TechAccount ownership
 
The work around I came up with has to share the project with both accounts.
you can do that by adding the Shares tag to your postman script.  It might look something like this
 
shares: [{shareToId: "xxxxxxxxxx", shareToType: "user", accessLevel: "edit"}]
 {shareToId: "xxxxxxxxx", shareToType: "user", accessLevel: "edit"}
  1. accessLevel: "edit"
  2. shareToId: "xxxxxxxxx"
  3. shareToType: "user"

 

sharing 'edit' access seems to fix the 'insufficient access' issue and i'm able to develop the project via the API while at the same time letting the end Adobe Analytics User see the updates i'm making.

 

I hope that helps give you some ideas.

2 respuestas

J
jlinhardt
Level 2
January 5, 2022

Hello.  Quick follow up.  I've been able to transfer ownership of an Analysis Workspace project between two users within the same company/account using Adobe's API and Postman.  You can do the same thing within the Adobe UI, but i was able to get it to work using Postman.  Is that what you're looking to do?   Or are you looking to transfer assets across companies?  Thanks for the clarification.

M
myradio_digitalAutor
Level 2
January 5, 2022

I was trying to do it in the same company, lets say from account corporate1_user1 to the account coporate1_user2.

J
jlinhardtRespuesta
Level 2
January 5, 2022

Hello.  Thanks for getting back to me.

 

I think the biggest hurtle you will have will be have the correct 'access rights'.

 

Meaning, when i created a new workspace project via the API, it was assigned to my 'techAccount' email address which is different than my Adobe Analytics Log In email address.  So I was able to use a PUT url of "https://analytics.adobe.io/api/mcdona4/projects/{{project_id}}" and a body script of 

{
    "rsid": "{{rsid}}",
    "owner": {
        "id": "{{ownerId}}",
        "name": "{{ownerName}}",
        "login": "{{ownerLogIn}}"
    }
}
to transfer the project from my Tech Account over to my Adobe Analytics Account
 
but if I tried to reverse the ownership (meaning transfer from my Adobe Analytics Account back to my TechAccount) i get a 'insufficient access' error.  because the asset is no longer under my TechAccount ownership
 
The work around I came up with has to share the project with both accounts.
you can do that by adding the Shares tag to your postman script.  It might look something like this
 
shares: [{shareToId: "xxxxxxxxxx", shareToType: "user", accessLevel: "edit"}]
 {shareToId: "xxxxxxxxx", shareToType: "user", accessLevel: "edit"}
  1. accessLevel: "edit"
  2. shareToId: "xxxxxxxxx"
  3. shareToType: "user"

 

sharing 'edit' access seems to fix the 'insufficient access' issue and i'm able to develop the project via the API while at the same time letting the end Adobe Analytics User see the updates i'm making.

 

I hope that helps give you some ideas.

R
rayfost
Level 2
August 25, 2022

I had encountered a similar issue and experimented with the access for the tech account.  I set up one project with a tech account that has Adobe Analytics admin access for being able to view items across our entire implementation.  So, another option to sharing the project is for the API to have admin access.  In that case,  there are not any issues with the tech account being able to transfer ownership to/from any other user, including itself.   

Términos y condicionesAccessibility statement

Loading footer...