Re: Content-Range header missing error in HTTP request but it isn't
Thanks, I found that article shortly after I posted. What's so incredibly frustrating is that Power Automate strips this header out, yet Universal Print requires the header in step 3 (uploading content). So invoking Universal Print from Power Automate does not seem possible.
What I'm attempting now is writing my own web service and custom connector and passing it the binary from Power Automate. Of course, binary isn't an option when creating a custom connector through the UI, but it *is* an option if you use the Swagger editor. Another topic in this forum pointed me to this:
https://github.com/microsoft/PowerPlatformConnectors/blob/8e8702daa846d3d35755971282947347dba2931d/custom-connectors/ServiceNow/apiDefinition.swagger.json#L530
I'm now stuck on authentication issues. I can invoke my web service through the custom connector, but it doesn't propagate the user's identity, so either a) it doesn't authenticate to my web service properly, or b) it authenticates as a service, not as the specific user, but the graph API for creating a print job doesn't support application permissions.
I'm hoping to work through that today. If/when I get it figured out, I'll post an update.