Forum Discussion
Document conversion
Hello! We have been testing the Universal Print feature in combination with pull-print scenario. It worked, basically, all things considered. But we also wanted to test the document conversion and t...
abitor I seem to get the same results as you. There appears to be documentation to suggest this should work:
https://docs.microsoft.com/en-us/universal-print/fundamentals/universal-print-document-conversion
I note this also seems to happen when I use the xps mime type application/vnd.ms-xpsdocument.
The only content-type setting it seems to work with is application/oxps.
Probably worth mentioning that when the printer's content type is set to anything other than application/oxps, the print on the client fails with 'Error - printing'.
Saurabh_Bansal
Microsoft
Microsoftabitor / AndrewCardy First lets confirm a few things:
- The virtual printer you created supports PDF only as content-type.
- The virtual printer does contain OXPS as one of the supported content types
- Are you trying to implement task trigger? If yes, then are you accessing the document after completing the task trigger?
Here is how it should work (if you have PDF only as the content type):
- For Windows versions 2004 onwards (2004 and 20H2), Windows itself will upload PDF and you can access the payload in PDF format.
- For Windows versions 1903 and 1909, Windows uploads OXPS. If you have task trigger, Universal Print will create a task and then wait for your application to complete the task. During all this time payload will continue to be in OXPS (unless you convert to another format and replace the payload). Once you have mark the task as complete, then Universal Print will process the job further and convert to PDF (if not already converted and document conversion is enabled). After conversion to PDF job will move to JobFetchable status.
Hope this clarifies.
Thanks,
Saurabh