Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X
Hello Dear Community,
Publishing experiences with the same project ID from multiple Studio terminals can result in overwriting the published data.
I'm having a lot of trouble. Is there a way to control access permissions or lock published data?
Take a look here:
Hi! @VladimirN Thank you for your help.
I understand above article. I think.
But now I'm in trouble overwritten the important experience by some developer in internal.
This may be a request, but could you please check the attached document?
Hi @T.Nakamura ,
there are some active Developer proejcst of MultiTenant usage but they are still in the pipeline of dev team where we do not have an official deadline when this will be implented. But I checked you powerpoint to see the requiremetns.
So far I see you need that all mentioned dev group should be able to access to content but for specific project they requires different permission - so this is currently not part of the functionality.
What you can do
curl -u <userId>:<password> -F ThingXExperience=@<myabcapp.zip> -H "X-Requested-With: XMLHttpRequest" https://localhost:2019/ExperienceService/content/projects/
respecitively you can see also the curl for delete Delete Projects from Outside of Vuforia Studio
So this what I belive that will work but possibly someone else in the communtiy have another better suggestion, thanksHI, @RolandRaytchev ,
Thank you for further information.
I am interested in setting up the approval process. I'll check the article. Thank you!
Exactly, I understand that we can prevent overwriting by adding more servers.
For example, test and production servers.
But that can't happen right away because of cost for us.
The only thing I can think of write a script that uses an external command to check the data on the ES server to see if it can be published or not, and then publishes it.
I would be happy if there is a better way.