Copy schedules and key schedules to another project and OVERWRITE the old schedules
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I have one storage-project that keeps all my schedules. This is NOT my template or starter project. When a live-project requires such schedule, I copy them to the clipboard and then paste them into that live-project. Transfer project standards doesn't seem to work on schedules.
it just happens that every once a while I edit the schedule in the live-project (add new parameters, edit naming etc.). that kind of has to happen in a "live" project to work with the families. In that case I then copy those schedules (and key schedules) back to my storage-project.
The problem with that is, it doesn't offer the option to overwrite the old same-name schedules, but it adds those and appends a "1". I then have to manually delete the original schedules, and rename the new schedules to delete the "1". Obviously this is unnecessary manual labor and can lead to errors.
I thought about only editing schedules in that storage-project. But then I have to re-create that situation from my actual live project to test. It is a bit forth and back to edit families and schedules to get it right. But even if I could stick to this, if a schedule is improved, it then would have to be copied over to my live project and then I have the same problem with the appended "1".
Theoretically I should keep track of what schedules I edit, or copy them right away... but in practice it would be easiest if at the end of a project, I just copy all schedules back to my storage-project.
I do the same with view-templates. but "transfer project standards" is nice enough to let me overwrite the old view template with he same name.
Is there a better way to handle this? Maybe there is a whole better way to maintain schedules.
Hardware: i9 14900K, 64GB, Nvidia RTX 2000 Ada 16GB
Add-ins: ElumTools; Ripple-HVAC; ElectroBIM; Qbitec