I forgot to say that every product has a unique CategoryID and each Category has his own Transformation, therefore a Macro would be good I think eg Product A which has CategoryID = 1 would get a Transformation called 1.

Hi,

In Portal engine, you can use macros in webpart properties, therefore it's possible to use standard or custom macro in Transformation name field, that will be resolved at runtime.

Standard macros can be used rather for multiple document types and their different transformations, like:

{%classname%}.default

For more complex logic, custom macro will be probably better.

--Zdenek