Alternative Element Trees - Extending Adapters - Extra Fields

[cancan101]

Is it possible to add an adapter for Alternative Element Trees that maps to "extra" fields on the Object? Or does the list of adapters have to 1:1 with the list of fields? Some examples:

1. An Adapter for Published vs Unpublished
2. Transforms of a given field where I might want to preserve the field but also aggregate at a higher level as well

[wisconaut]

As discussed internally, the answer should probably be the same as this one (enterprise repo): https://github.com/pimcore/backend-power-tools-bundle/issues/453#issuecomment-2642225660

Hello @cancan101 ,

right now there are no other options available than selecting an adapter from the list. What you could do is creating your own adapter and implement the transformations you need there. If you are interested, a good starting point would be here:

Frontend part: https://docs.pimcore.com/platform/Backend_Power_Tools/Alternative_Element_Trees/Customization/Adding_Custom_Frontend_Adapter
Backend part: https://docs.pimcore.com/platform/Backend_Power_Tools/Alternative_Element_Trees/Customization/Adding_Custom_Backend_Adapter

Best regards

[cancan101]

If I create my own adapter, will that get added to the list of options shown or will the new adapter have to replace an existing option? Ie is the list of adapters shown limited to just the fields on the model.

The linked docs don't make that clear.

[fashxp]

Now I understand your point.

Right now, the list of fields is limited to actual data object attributes defined in the class definition. No system fields (id, published) or completely extra fields (e.g. workflow states from state table) can be injected in the current implementation.
But maybe we should think about making it extendable - eventually with some events?

For now, the easiest way to get such extra fields in the field list would be to create a calculatedValue attribute in the class definition that returns the wanted extra values.

[cancan101]

the easiest way to get such extra fields in the field list would be to create a calculatedValue attribute in the class definition that returns the wanted extra values.

make sense. I can see how I would do that for the published field. Is there anyway to do that for a workflow state with a Symfony expression or would I need to write a Calculator Class? i.e. is there anything injected into the environment that acn be used to resolve the state?

[fashxp]

out of my head I would say a calculator class is needed for the workflow states.