Events for changes in a board configuration

monday Apps & Developers
, ,
1

Hello Team,

I’ve faced an issue when I use monday.listen.
I’ve made a subscription for changes in the board.

monday.listen('context', res => {
//handler's code here
});

Then I changed the numeric column settings, but the event hasn’t fired.
Maybe I’m wrong but a few weeks ago all worked as expected.

Or It would be much better if you offered a solution to catch changes in the column’s settings such as changes in format or adding a description.

1 Like
2

A small clarification.

An event inside the listener didn’t contain any information about matters of change, but it appeared whenever something changed in a board or column configuration.

3

Hello there @DKostochko,

Our team informed me that a fix has been deployed.

Would you be able to please try this again now?

4

Hi @Matias.Monday

Nothing changed

How I’ve checked.
Environment: Chrome with open dev console
Tab 1 — Board
Tab 2 — Test app (for board view) with a subscription for events in “context”
Turned on messages tracing between the main window and app frame using a feature from dev console

monitorEvents(window, 'message')

Test case 1
In the board, I changed the settings for a numeric column. I switched Unit from None to $
In a context listener, nothing happened.

Test case 2
Resize app tab generated events stream from the main window to frame. But the reasonable part of the message is

{
    "errorMessage": "undefined command isn't available or supported for this app feature type"
}

But before in this case, the app had got an event in the context listener.

Shall I collect more info and provide details to you?

5

Hello again @DKostochko,

I was just informed that the issue was solved momentarily and now came back.

Our team is working on it!

6

Hello again @DKostochko ,

Matias here!

Our team has deployed a fix for this.

Would you be able to please check if it works for you now?

Looking forward to hearing from you!

Cheers,

Matias

7

Hello @Matias.Monday!

At this moment the issue still presents.

Details

For Test case 1
Nothing changed.

For Test case 2
I’ve seen changes only for messaging between frames. Data from the previous post was replaced by this data.

{
    "source": "react-devtools-bridge",
    "payload": {
        "event": "operations",
        "payload": [
            3,
            // skipped data
            0
        ]
    }
}

But the listener for context hasn’t been invoked anyway.

9

Hello again @DKostochko,

I believe the fix that was deployed solved an issue with the listener but not this specific one then.

Would you be able to please fill this form adding as much information as possible to it (the script and a screen recording would be fantastic) so that our team can take a look into it?