I used /elasticubes/{server}/{title}/updateCube to set the "creator" attribute. It destroyed my cube; the only way to recover was using the REST API to export a .sdata, import that, and delete the ol...
Hi Tim,
Thanks for sharing your experience! This is a helpful caution for anyone using the /updateCube REST endpoint. A few tips to avoid similar issues:
- Full backup first – always export the cube (.sdata) before making updates.
- Be careful with partial updates – sending only one attribute (like creator) may overwrite other metadata and break the cube.
- Consider retrieving the full cube definition first – if you need to change something, make a copy, update the field, and then save the full cube data back.
Even without development work, these steps can reduce the risk of losing cube metadata. Your experience is a good reminder to the community to handle REST API updates with caution.
Best Regards,
Piotr from QBeeQ, a Sisense Gold Implementation Partnerwww.qbeeq.io