Hi everyone! Did Monday recently make an update that impacts the order that connected item IDs are returned when multiple items are linked in a connect boards column?
It used to be that when returning the value for a connect boards column, you got an array of connected item IDs (linkedPulseIds), and they were ordered from the item that was connected first through the most recently connected item.
It seems like sometime very recently this was reversed, and it is wreaking havoc on my automations.
Has anyone else experienced this issue?
Can anyone from Monday provide any insight on this?
Okay after running some tests, it appears that not only are the connected items no longer returned in the order that they were connected, but they are not consistently returned in any order (that I can decipher) at all.
In my test, I have a webhook that is triggered when a connect boards column changes. The column connects a test products board with a customers board.
In the test run of this automation, I’m triggering it by connecting a third product item (6511927966) to a connect boards column that already has two items (6511927959 and 6511927954) connected to it. The customer item is named Bill (6511931747).
First, looking at the output of the “watch events” module that’s triggered by the change in the connect boards column we have a value collection that contains the array linkedPulseIds.
In the array, we have three pulse IDs, returned in the following order:
6511927966
6511927959
6511927954
Then, I have a “get an item” module, in which we get the data for Bill. In the mappable column values for this item, we have a collection for the connect boards item that includes the array linkedPulseIds. This array contains three IDs in the following order:
Monday support told me that there have not been any recent changes to this, though I have certainly observed this as being the case.
@Matias.Monday did verify that the order of these items is not guaranteed. Interestingly, he also let me know that item IDs are sequential.
As such, my workaround has been to sort the connected pulse IDs in ascending order.
It’s worth noting that this works for my use case, because items are connected at the time of their creation, so order of creation and connection are interchangeable. I can imagine other use cases where this wouldn’t be a sufficient workaround.
I believe webhooks for when a connect board column changes return the current and previous values? It should be entirely possible to do a comparison on the size of previous to current and then know if one was removed or added - and then create a map of each and compare to get the one(s) added or removed.
This way you’re not limited to only new items that were created being in order.
