Let me underline a current problem with this issue! Bill correctly points Anna to InteractiveFrameUpdate.
You might have thought — as I always do, and then I have a problem similar to Anna’s — that you could create the InteractiveFrame with that flag set, so that “prevent reorganization” is false (that is, “allow reorganization,” which is not what it’s called, is true… :).
But you can’t. Mostly. You have to create the Frame and then update it. As I have learned repeatedly. In case it might be useful so some poor sod following in our footsteps, some code that (currently) works:
await codapInterface.init(this.iFrameDescriptor, null)
// now update the iframe to be mutable...
const tMessage = {
"action": "update",
"resource": "interactiveFrame",
"values": {
"preventBringToFront": false,
"preventDataContextReorg": false
}
};
const updateResult = await codapInterface.sendRequest(tMessage);
Oddly, it also seems to be the case that if you make more than one data context (more than one table), the second one can be reorganized. This leads us to wonder whether, perhaps, the flag should be attached to the data context (a.k.a. dataset, table) rather than to the entire iFrame, that is, to the entire plugin. I think the Wizards of Emeryville are considering this.