In my short experience with report models, they use GUIDs to refer to everything instead of a proper name, and so whenever a database schema is modified or deleted/recreated, it will break the model; and in many cases you'll have trouble finding exactly what in the model has changed and just have to delete it all and recreate it from scratch... until it happens again.
IMHO the best solution is not to use report models at all.