TD: How can I add not the newest component version

  • Thread starter Thread starter Joerg Schneider
  • Start date Start date
J

Joerg Schneider

I have to specify a new(!) TD file using an old(!) version/revision of one
of my components.
How can I select a specific component version/revision?
Do I need specific TD settings? What is to do?

I tried it with a Copy (from an old TD file) and Paste (to the new file).
But that will not work. I got the newest.
And the newest version/revision of the component I can't remove from
database because it is already used in an other TD file.....

Any help is appreciated
Jörg
 
Joerg,

I don't know any way how to add old component revisions in new SLX
configurations.
However, there is always a workaround. Save you SLX configuration as XML,
open the XML file in notepad, find you particular component (easy to search
by the component's GUID) and change "revision=" field value to the revision
number you need, save and open the file in TD again. The this point , you
should see a blue arrow icon accoss your component meaning it is not
up-to-date with XPe database.

KM


JS> I have to specify a new(!) TD file using an old(!) version/revision
JS> of one of my components.
JS> How can I select a specific component version/revision?
JS> Do I need specific TD settings? What is to do?

JS> I tried it with a Copy (from an old TD file) and Paste (to the new
JS> file).
JS> But that will not work. I got the newest.
JS> And the newest version/revision of the component I can't remove from
JS> database because it is already used in an other TD file.....

JS> Any help is appreciated
JS> Jörg
 
Hi Joerg,

Fortunately/Unfortunately - Good/Bad, TD does not allow adding an
older version of any component. So, whenever u open an existing slx
file, it shows u an icon to indicate that a newer version of the comp
exists. Luckily, it doesn't force u to upgrade it and u can work with
the old version. Here is the workaound I did sometime back.

If you have the both the versions of the component in the database,
delete the new version for some time, add the component and u r good
to go.

BUT Ideally, if you need the old and the new version too frequently,
making a fresh component (with a slightly different name) is
recommended instead of updating the old one.

Cheers,
Ashisha
 
Just a suggestion, I've not tried this. IIRC, in Component Designer when
specifying dependencies, you select a particular version of a component for
yours to depend on. I don't know if this would work, but have you tried
creating a component that only consists of a dependency on that particular
old version of the component that you want?
 
If that doesn't work, assuming you have the old .sld file, you could
re-import it as a different component, then you have the choice of which one
to use.
 
Thanks for your responses. I used the mothod of <KM>:
...."Save you SLX configuration as XML, open the XML file in notepad, find
you particular component (easy to search by the component's GUID) and change
"revision=" field value to the revision number you need, save and open the
file in TD again"...

The first suggestion of Heidi Linda will not work because a dependency can
only be set to "newer than"....
But the new component is also a good idea.

A wish to MS: Please think to those who have the problem: "Not always
lastest is greatest..."
The best would be modified tools:
- CD viewer with selectable listboxes of versions/revisions (all old
versions are in the database!)
- TD with selectable versions/revisions of a component (for e.g. in a CMI
variable?)

Jörg
 
Back
Top