Hello Laflys,

Thank you for bringing this issue to our attention. I have been able to reproduce it on my end and will notify the engineering team about it.

Kind regards.

Daniela

Thank you @Daniela Gavidia !

Having this issue too. 

I have the issue too, for other item types. And actually, this is rendering our plugin useless. I am surprised, that we only found out the reason to why we get so inconsistent data so late. If this issue already exists for a month.

When can we expect a fix?

Seems to be working again. Thanks for fixing it.

And it is broken again. :(

Hi there,

I can confirm that on my developer account at least, metadata on frames does not survive a refresh - both in what is returned in a call to widgets.get(). Using filter arguments on widgets.get to filter by metadata also does not work:
 

Pseudocode:

const clientid = miro.getClientId(); (await miro.board.widgets.create({type: "FRAME", metadata:{
/clientid]: {
        "testing": 123
    }
}})); // resolves to widget with metadata values populated

await miro.board.getAllObjects() // includes widget with meta data values populated.

await miro.board.widgets.get(t"metadata."+clientid+".testing", 123]) // returns the frame created (other get filters function correctly)

After reloading the page, the same getAllObjects and get queries do not return any frames on previous pages. 

I was thinking of using a secret hidden shape on the page to store frame metadata separately and perhaps restore the metadata to relevant frames on load. 

This does not feel a long term approach though so it would be great to know if this behaviour is by design or is it just missing functionality! 

Thanks

Jen Smith