As part of the backend improvements we are making in order to enhance the performance and stability of the Iterable platform, we are upgrading our underlying database technology. We are deploying the upgrades to our customers on a rolling basis; your customer success manager will be in touch with you when your turn arrives!
Q: What happens when it's my turn to upgrade?
A: Your customer success manager will inform you of a short downtime window in which you should not make any changes to your database. Note that scheduled blast campaigns, active triggered campaigns and active workflows will not be impacted.
Q: What kind of changes are you talking about?
A: All PUT API calls and user updates/uploads via CSV.
Q: After the upgrade, I noticed that some of my field names changed. What happened?
A: There are two instances in which a field rename was performed - if you had a field with an illegal empty (i.e. "") name or more than one field with the same name, we will help you to rename those fields due to the strong name enforcement in the new database version. If you have any questions about this, please reach out to your customer success manager!
Q: What happens if I have a custom event or user field with "" for a name?
A: Those custom events will get renamed to unnamedEvent, while fields get renamed to unnamedField.