joomlamate
Member
Following the other issue on this thread, I found out also that after the update database join elements won't contain the value's label in the PDF, but only their raw value. So it's impossible to print on the PDF what the selection's represent in text. This time, this issue appears in both my forms.
Overall, the same template when is used as the detail layout it will return different data sets than when it's used as PDF layout.
One descriptive example is when on Details, an element's ro will contain a string, but when in PDF it's value becomes an array. So it actually becomes harder to test/debug the PDF layout if for example is set to be used as a Details layout.
I remember that this was the same some years ago when I first created those custom layouts, but I had managed to accept that as the use case and created the layouts.
I would have no problem with this at this time, but I definitely need the database join elements to return the value's labels in the PDF, instead of just the raw data (usually numbers that represent the id of the selected option of the joined element).
Overall, the same template when is used as the detail layout it will return different data sets than when it's used as PDF layout.
One descriptive example is when on Details, an element's ro will contain a string, but when in PDF it's value becomes an array. So it actually becomes harder to test/debug the PDF layout if for example is set to be used as a Details layout.
I remember that this was the same some years ago when I first created those custom layouts, but I had managed to accept that as the use case and created the layouts.
I would have no problem with this at this time, but I definitely need the database join elements to return the value's labels in the PDF, instead of just the raw data (usually numbers that represent the id of the selected option of the joined element).