we are following Baan Customization Administration (Baan5c ) to have a proper control of components being tranferred from devl to prod env.

I am having a problem in exporting components from devl env. based on Customization administration. Here is what I am trying to do:
I run the session ttiex1280m000 : Export Data Dictionary. In the 4th tab (Components 3) if I select Customisation Project, than only those components which are attached to the Project/Customization Part/Project Part must be exported. But this seems to be not working.

Can anybody through some light on this or is it a baan bug?

Thanks

You would think that is the way it would work -- and it would be tremendously helpful if it did work that way. Unfortunately, filling those fields won't help you export the components you really want to export. It only specifies which customization parts (not the other objects associated with those parts) to export.

There was another post not too long ago about this as well. I think there is widespread agreement that this would be useful. Unfortunately, for now, you have to pick and choose the things to export using the ranges for each object type.

Sorry.

I have developed in the past a small tool that generates a file which can be used with ttiexdeliverp.

ttiexdeliverp needs an ascii file which contains a list of components. That list can be used in ttiexdeliverp in order to export specific components.

I did develop it for a customer and haven't took the code with me, so I am not able to share it, sorry.

Han

Thanks guys for the quick replies !!!!

Han,

Is there any information around (that you can provide ;))that tells what the layout of the components file needs to be?

"Customized (http://gwconsulting.netfirms.com/configuration.html)" - Customization Administration sessions and strategy.

Is there some trick to getting the program source to accompany the object when using ttiexdeliverp? I've used the "PS" code, but this doesn't seem to have any effect.

If I remember well the online help of the session, or perpaps on field level describes how the file should look like. If you're not able to retrieve it then I can find it out, I have noted it somewhere.

Han

Hi guys,

I developed a nice tool that I called tcmcsexportec of which I am enclosing the dump.

I am still enhancing it but this version is pretty usable.

Remember to set the variable CUNO_SRC to something (e.g. "Y") if you want to export also sources.


Hope it helps.

Claudio Montanari
KNOW-HOW Italy

have you tried ttiex4100m000 ? .... I don't know if it's still present in BaaN V, but it has saved us a lot problems in BaaN IV ....

Somebody knows if ttiex4100m000 in Baan Vc exists?

Marcelo

It exists in B5.0x also, but under the session id ttiex4500m000. I extensively use it.

We released the tool that Ed was working in the above posts as Freeware - Export by Customization Administration code (probably similar to what Claudio has). That way you do not have to create the patch first. We put this and a few other handy tools on a CD and passed this out at BWU / Montreal. We have Baan IVc3, IVc4 and Vc out there right now. There is also a client tool that tracks the bclients that are logging in, their versions etc. If you missed the conference, you can download these at:

http://www.rmcis.com/tools.html

We hope to continue expanding these tools.

Would you like to share the source code? I am thinking of doing some enhancement to automate our weekly code move procedure.

Chris.
ccheah@altera.com