I have an activity that I have split into 4 session per week. But I now need to increase that to 5. Is there a way to properly modify the activity to reflect this, or would I have to remove the activity and create a new one? It is not very much trouble to do so--I was just wondering if there was a more elegant way of carrying out this edit.
Sadly you need to remove and add it again. it isn't easy to care about that problem. (because it might effect to many time and space constraints and it also effect all following activities, which effect also to many time and space constraints.)
Thanks for that. Luckily in this case there were no constraints affected. There are indeed cases though where I have had to edit/remove an activity, which in-turn affects (removes) many related constraints. When this happens, I have had to rely on my memory/notes to fix/re-add the affected constraints. Is there a tool within FET that, when I modify/remove an activity (or category), can output exactly which constraints are affected? If not are there any tools/tricks within FET that would ease that process?
Not a complaint. As I'm a beginner, I'm just trying to learn how to make FETing as efficient can be.
Thanks again.
Quote from: panyadee on March 13, 2016, 02:18:47 AM
Is there a tool within FET that, when I modify/remove an activity (or category), can output exactly which constraints are affected?
Before the removal, go to activities dialog; for each activity, on the right, in the description, will appear the constraints which use the exact id. I hope no constraint is missing from this description.
Thanks, that will help. In the case of many constraints which use that activity, could I perhaps employ some of the 'write to csv' tools that FET contains? In other words, am I able to write all the activity/constraint pairs to CSV at any point? If so, I could make a point to always write this out for each updated timetable version. If not, I'm sure I can just copy/paste from the activities dialog box.
Cheers.
There is no such CSV export/import, unfortunately.