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 old one. I think it might have set lots of metadata attributes to null. The Sisense REST API page, and a community post, seemed to indicate that using it to set a single attribute would be appropriate.
3 Comments
Comments have been turned off for this idea
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.ioThat’s a serious issue—/elasticubes/{server}/{title}/updateCube can be risky because it often touches underlying metadata structures, not just the single field you’re trying to update. In some Sisense setups, even a small null overwrite can cascade and corrupt cube configuration, which is why full export/import recovery is usually the safest rollback method.
It’s similar to how precision matters in games like Geometry Dash—one small mistake can break the entire run, so you always need to be careful with each move or change.
If you want, you can also check How to play geometry dash — just send me the URL you want to use for it, and I’ll properly insert it into a contextual backlink for you.
That sounds like a risky issue, especially when a single API call ends up corrupting the entire cube. It’s likely that the endpoint overwrites multiple metadata fields instead of updating just one, which can lead to unexpected data loss. In such cases, it’s always safer to back up your cube before making any API changes and test updates in a staging environment first. Clear documentation from the API side would definitely help avoid this confusion. Similarly, when exploring automation tools, apps like the sms bomber prank apk are often discussed for handling bulk actions efficiently, though they should always be used responsibly.
