I did not tested but I suggest that encrypted field should not be exported but virtual column should be. Template based export can be achieved using defining print format currently.

Yes - for support users mainly - that sounds OK to implement, just noting that will be incomplete, and can lead to situations where the exported file cannot be imported directly - but that's minor as the implementor must know the cause.

I guess perhaps the original intention of this ticket is not for end user but implementer. Perhaps others can clarify here.

Is not a bug, an improvement, if done is OK - allowing to export those columns sounds fine, but is not worthy for end users as they must not have access to that button.

So, the best implementation for end users would be to implement this adding the template export.

Hi , , and ,

so what’s the conclusion here ? not a bug and implement template for export instead ?

Regards,

Low