Cannot leverage document conversion on UP

%3CLINGO-SUB%20id%3D%22lingo-sub-2107947%22%20slang%3D%22en-US%22%3ECannot%20leverage%20document%20conversion%20on%20UP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2107947%22%20slang%3D%22en-US%22%3E%3CP%3EHello!%3C%2FP%3E%3CP%3EI'm%20developing%20a%20custom%20UP%20Connector%20and%20the%20communication%20flow%20with%20the%20Infrastructure%20Printer%20and%20the%20Notification%20Service%20described%20in%20the%20IPP-Infra%20spec%20works%20quite%20well.%3C%2FP%3E%3CP%3EHowever%2C%20I've%20registered%20a%20printer%20that%20doesn't%20support%20%22application%2Foxps%22%20as%20a%20document%20format%3A%20the%20connector%20talks%20straight%20to%20the%20Output%20Device%20via%20IPP%2C%20not%20using%20the%20printer's%20driver%20(which%20I%20reckon%20would%20be%20able%20to%20handle%20such%20a%20format).%20The%20Output%20Device%20does%20support%20%22application%2Fpdf%22%20though%2C%20but%20when%20I%20try%20to%20print%20a%20document%20from%20a%20user%20account%20the%20printer%20had%20been%20shared%20with%2C%20it%20results%20in%20an%20error.%3C%2FP%3E%3CP%3EThe%20document%20conversion%20is%20enabled%20on%20the%20Management%20Portal%20and%20the%20client%20Windows%20version%20is%2010.0.19042%20Build%2019042.%3C%2FP%3E%3CP%3EAre%20there%20additional%20steps%20to%20follow%20to%20leverage%20the%20conversion%20feature%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMany%20thanks%2C%3C%2FP%3E%3CP%3EGianvito%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2160980%22%20slang%3D%22en-US%22%3ERe%3A%20Cannot%20leverage%20document%20conversion%20on%20UP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2160980%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F947200%22%20target%3D%22_blank%22%3E%40Gianvito_Difilippo%3C%2FA%3E%26nbsp%3BI%20recall%20the%20Windows%20client%20build%20you%20are%20using%20is%20the%20Windows%2010%20October%202020%20update.%26nbsp%3B%20That%20release%20supports%20printing%20in%20PDF%20format%20to%20a%20printer%20that%20supports%20PDF%20through%20IPP.%26nbsp%3B%20You%20should%20not%20require%20the%20Document%20Conversion%20functionality.%26nbsp%3B%20You%20can%20verify%20the%20set%20of%20document%20format%20specified%20by%20the%20printer%20by%20using%20the%20Universal%20Print%20admin%20portal%20and%20look%20at%20the%20printer's%20properties.%26nbsp%3B%20Under%20the%20%22Printer%20Defaults%22%20tab%2C%20you%20should%20see%20%22Content%20type%22%20and%20in%20the%20drop%20down%2C%20select%20%22application%2Fpdf%22.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBTW%2C%20looks%20like%20you%20have%20some%20control%20over%20what%20the%20printer%20is%20specifying%20to%20Universal%20Print%20on%20its%20capabilities.%26nbsp%3B%20If%20this%20is%20the%20case%2C%20you%20can%20omit%20setting%20%22application%2Foxps%22%20as%20a%20support%20document%20format%20since%20your%20application%20is%20sending%20the%20print%20job%20to%20the%20printer%20over%20IPP%20in%20PDF%20format.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHTH%2C%3C%2FP%3E%0A%3CP%3EJimmy%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hello!

I'm developing a custom UP Connector and the communication flow with the Infrastructure Printer and the Notification Service described in the IPP-Infra spec works quite well.

However, I've registered a printer that doesn't support "application/oxps" as a document format: the connector talks straight to the Output Device via IPP, not using the printer's driver (which I reckon would be able to handle such a format). The Output Device does support "application/pdf" though, but when I try to print a document from a user account the printer had been shared with, it results in an error.

The document conversion is enabled on the Management Portal and the client Windows version is 10.0.19042 Build 19042.

Are there additional steps to follow to leverage the conversion feature?

 

Many thanks,

Gianvito

2 Replies

@Gianvito_Difilippo I recall the Windows client build you are using is the Windows 10 October 2020 update.  That release supports printing in PDF format to a printer that supports PDF through IPP.  You should not require the Document Conversion functionality.  You can verify the set of document format specified by the printer by using the Universal Print admin portal and look at the printer's properties.  Under the "Printer Defaults" tab, you should see "Content type" and in the drop down, select "application/pdf".

 

BTW, looks like you have some control over what the printer is specifying to Universal Print on its capabilities.  If this is the case, you can omit setting "application/oxps" as a support document format since your application is sending the print job to the printer over IPP in PDF format.

 

HTH,

Jimmy

@Jimmy_Wu hello Jimmy, thanks for your response.

We solved our problem by adding the IPP attribute "media-col-supported" in the registration step. This attribute seems to be missing in the list of supported printer attributes, but one of your developers kindly provided us with a more exhaustive list.

We didn't think that could be the cause of the error since oxps printers worked fine, but now we can also print to PDF and PCLm printers.

 

We are truly grateful for your support,

Gianvito