Hi all,

I have a question about the exporting function of a datawindow in XHTML.

I have built a small DLL in C# that allows me to convert a group datawindow, exported as XHTML, into a docx file. I use the export to XHTML only because it is a format that facilitates the conversion: it allows me to recognize the different fields as header, groupheaders, details, footer, etc. (I doubt it is a good idea overall, but I wanted another method apart from using an OLE object).

Long story short, I encountered what seems to me a contradiction in the guide for pb2022 about exporting a datawindow as XHTML:

- on this page, it seems ok: https://docs.appeon.com/pb2022/datawindow_programmers_guide/dwprgug-webdw-exporting.html#d0e5939

- but on this other page, it seems that the same instruction is marked as obsolete: https://docs.appeon.com/pb2022/datawindow_reference/XREF_70072_Data_XHTML.html

So, I wanted to ask: is it safe (that is "not counterproductive") using the Data.XHTML method?

And if it is the case, is it safe to modify the default configuration on the Web Generation tab in the datawindow's properties? Because I don't need the generation of the js files. I know that it is "preserved for the backward compatibility only", but those properties affect the XHTML exportation.

Thanks in advance