Posted: Wed Jul 05, 2006 5:21 pmOne of the fields on our DataFace records is "Publish?" to which we can answer Do or DoNot. This then controls whether or not that record will be displayed on our front-end. Another field is called Task# and we enter a unique Task# on each record.
As a way to emulate version control, we'd like to be able to copy a record before making extensive changes to it, then on the original record, putting a suffix of "-bk" (or "-bk2", "-bk3", etc) on the Task# and setting the original record's publish field to DoNot so we can keep it around for awhile in case we screw up our changes on the new version of the record. All of our programmers are having to learn how to work with the TinyMCE editor including using some tricky stuff that Bill Royer and Mike Wassil set up for putting boxes around our screen shots, etc and it's really easy for us to screw stuff up at this point.
You had indicated the following about this in an email to Mike. We'd very much like to get this feature implemented and the sooner the better. As per with "Record locking via check-out and check-in", we could also potentially take a stab at doing this ourselves (as part of the standard project).
>> Dataface 0.6 ( still in testing ..
makes it easy to add actions like this.. though no action like this has been created yet, it would be a good one to add.
Note: Aside from emulating version control, we may have nearly identical records for our IdealWare clients and our IdeaLaw clients and, after having creating a record for one of these, it would be very advantageous to be able to copy it to a new record then make a few mod's to second copy. We have 28 fields on each record, including 3 TinyMCE edited ones, and that's a lot of data to be repeating.
As a way to emulate version control, we'd like to be able to copy a record before making extensive changes to it, then on the original record, putting a suffix of "-bk" (or "-bk2", "-bk3", etc) on the Task# and setting the original record's publish field to DoNot so we can keep it around for awhile in case we screw up our changes on the new version of the record. All of our programmers are having to learn how to work with the TinyMCE editor including using some tricky stuff that Bill Royer and Mike Wassil set up for putting boxes around our screen shots, etc and it's really easy for us to screw stuff up at this point.
You had indicated the following about this in an email to Mike. We'd very much like to get this feature implemented and the sooner the better. As per with "Record locking via check-out and check-in", we could also potentially take a stab at doing this ourselves (as part of the standard project).
>> Dataface 0.6 ( still in testing ..
makes it easy to add actions like this.. though no action like this has been created yet, it would be a good one to add. Note: Aside from emulating version control, we may have nearly identical records for our IdealWare clients and our IdeaLaw clients and, after having creating a record for one of these, it would be very advantageous to be able to copy it to a new record then make a few mod's to second copy. We have 28 fields on each record, including 3 TinyMCE edited ones, and that's a lot of data to be repeating.