In older Monday accounts the “Main Workspace” has id null
(like specified in docs) while in newer accounts the id is a true number(which contradicts the docs). As a result, the API is now inconsistent.
For instance, the query below returns:
the boards of the main workspace in older account
nothing in newer accounts.
This makes it hard to develop reliable programs for developers.
What is the future planned behavior for this? Please also suggest a way developpers can reliably point to the Main Workspace.
Thanks
{
boards(workspace_ids: null) {
...boardFragment
}
}
fragment boardFragment on Board {
id
name
description
type
state
board_kind
board_folder_id
items_count
permissions
updated_at
workspace {
...workspaceFragment
}
top_group {
id
}
}
fragment workspaceFragment on Workspace {
id
name
}
Thanks. So the newer accounts now have a Main Workspace that is a proper workspace with an id and that is great.
The missing piece is that from the workspace list returned from the API, we cannot know which workspace is the main one (other than the name… that can be changed by user). I would have expected some flag to tell us that a workspace is the main one. What is the plan for the future after migration? And how can I know today reliably?
Just wanted to update you that we recently add the is_default_workspace field that should solve this problem! Announcement will be coming soon, but here are the docs for now