Right now if you restore your site via backup, the collection IDs and Item IDs will change. If you're using the API to reference specific items in another system, this can break your process.
There should at least be a warning, and really these IDs shouldn't change as they wouldn't in another database system when it goes to a backup.
Phil Strazzulla
Crickets. There should at least be an official release now so developers can move away from Webflow now before getting deeper in the quicksand. Yes? Not now? Never? What is the deal?
Any update on this ? Is a fix even under consideration ?
Also ... why is the warning message that item id's can change ?? afaiks they always change on a restore ? Kind of gives a glimmer of hope when none exists.
This is a deal breaker for us continuing to use Webflow. As i'm sure you are aware any integrations rely heavily on collection and item ids' . (as your api relies heavily on these!). Is this likely to ever be addressed ? If no we are out.
Wasnt aware of it. Have to update 600 item now in Airtaible and integromat.
How much time does Webflow take to fix a small bug that could be fixed in 1-2 hours? Cause it's been over an year now.
My team experienced this issue recently. I created another wishlist item with some ideas for addressing it and would love your votes or feedback on it!
This just killed my whole project IDs...
This is unbelievable
There should be a warning!!! I have such a mess to clean up now. Terrible.
I have just experienced this almighty ball-ache! Because of this my automated Zapier process failed and new users didn't have log in pages!!! Why the hell would item IDs change?!
Experienced this pain today too. jesus.
I've now felt this pain. It is not a good feeling.