Update existing items via import using unique ID column for mapping

Feature requests
, ,
1

When importing items from excel in order to update existing items, it is only possible to map these items via the item name or date columns which are often not unique and as such this feature is very limited especially with larger data sets. If it would be possible to use the item ID column which is unique to map the existing items this would enable much better update capability of existing items on a board.

2

This would make cleaning and updating data in large Monday boards so much easier. The item ID column seems made for this feature.

1 Like
3

it would seem to me that this feature is a no-brainer, we currently have a number of boards with large data sets and need to manually add-in a unique ID number to the item name so that we can properly map the data when we need to import data which we do in order to sync the data with other sources.

This feature would reduce a significant amount of manual work arounds and reduce the margin for error.

1 Like
4

Agreed!

A workaround I did use that worked okay was to add in the Item ID column, export to Excel, make my updates in Excel, then convert the Item ID column to a text column before re-importing. Then, when you re-import , you can use the text version of the ID column as your matching column.

That being said, as you said, using the ID number column for the unique ID (vs a workaround) seems like a no-brainer.

1 Like
5

Hello Monday Team,
Please revisit this feature request. This will really add value and it makes a million sense to add this feature since you already have unique IDs assigned to each created items automatically at the back end.

2 Likes
6

Agreed! Please revisit this request, it is much needed.

1 Like
7

Agreed! Please implement this feature!

8

+1 to this request.
While there is a workaround possible (add ItemID column, duplicate with values, convert duplicate to text and add an automation to fill the column for new items), this is a true workaround and does not work when you want to apply it on large tables (>20K items).
Our items often do not have one specific unique value, so using the itemID’s as the unique value to check for duplicates when importing would be so useful to alter large amounts of items using an import.