Any dangers around deployment in this scenario:
I think this is generally okay when new content types are released, but if you change an existing one you can run into trouble, correct?
How can you get around this?
Episerver Forms is probably not the right forum... But.
Don't change properties. Hide them or remove them. Raise the version number for the assembly so that old code won't get picked when synchronizing.
whoops. Yeah, didn't mean this to go in Forms forum. Can't seem to move it.
So what would you do if for example you had a block with integer properties that you wanted to change to decimals?
I have used the 'Convert page types' feature a bit to manage changes to content types. There doesn't seem to be a 'convert block types' feature, which could be really useful for managing changes to functionality.
Found some more useful info here too: https://world.episerver.com/blogs/Per-Bjurstrom/Archive/2012/10/Synchronization-of-typed-models/
Post moved to the CMS forum.
I think int => decimal can be changed without data loss. But test it locally. If it works; don't remove/rename.