Hi,
what i need this time is to integrate two already generated and blocked timetables...
Scenario:
Timetable 1
hours from 08:30 to 14:00
already generated and blocked
Timetable 2
hours from 14:30 to 20:00
already generated and blocked
I have imported the activities cvs, but that is not enough because I also need to import the blocking rules, and that is not easy, because at both timetables, restrictions counts for activities from 1 to n, and at the moment of the cvs importation activities change their id number to consecutive ones, I mean n+1 and so on; so blocking restrictions do not fit with new ids, in the case I copy blocking restrictions from one .fet file to another. So basically I'm totally lost, your help, as always, will be appreciated.
hmm...
difficult at the moment. (especialy because of all other constraints)
the only workaround i know is this:
that the timetable with the lowest number of activities.
export as csv.
open the timetable with the highest number of activities adn all locked activities.
import the activities with cvs.
so you have at least 50% of the activities alreaady locked.
now regenerate or lock some/many activities of the just imported activities.
Andrés, the solution is to work with the XML .fet files. Merge them manually, copying the necessary sections.
Thanks, I did it that way, I first imported the activities from csv, I had to renumber the <Activity_Id> from the higher number to the minor one, at the importing file to fit with the new Id number, and then do a lot of work manually, finally relocate activities that could have been moved to finally generate it.
Uffff!!! lots of work.
I think the ability to renumber the IDs of the activities starting from a specific ID would be very useful in other XML-related work, too.
An advanced option: "renumber activities" with a dialog asking for "new lowest ID" would be ideal for these merge-split issues.
In this case we could renumber the first FET file from 1, the second from 1000, then copy paste directly into the XML file.
This would get all rules and activities, wouldn't it?
Hmmm maybe we could use XSL for this but I'm not good enough at it....
Yes, this is a good suggestion, which I added into the TODO.
Is it been implemented some way?
QuoteIs it been implemented some way?
No, it isn't implemented. It should be very easy, but it is a bit complicated because one needs to update all activities constraints, and there is a large palette of possibilities and it is a lot of tedious work.
I could give detailed advice on how to do that and answer queries, or do it myself as a last resort.
I would not like to add it to official FET, because: 1) I prefer current stability of FET, 2) I do not see it as standard feature, may complicate things for many users, 3) it is part of many many possible improvements of the interface/data creation/manipulation, and I prefer others to develop a better interface. Reason 1) may look revolting to others reading this, and indeed it is, so we may drop it :-)
An alternative would be a separate program to do that (using a small portion of FET).