Documentation indicates *obj/json was implemented last year: PxPlus 2025.

We're finally moving off 2018 (v15.10) ourselves soon, and will be glad to have the various new objects and tools available.

James,

I appreciate the response.  It is a FACTS customer and it appears that newer versions open windows as new sessions which was causing the disconnect.

I need to convert XML data to JSON.  I see there are some objects to do that, but wondering at what version the json object was available.  The customer is at PxPlus 2018 (15.10).

Thank you both for your help!

As my application is not adding anything to the header (just using  *web/email) and as it's really just one customer whose exchange server is rejecting our emails, I'm more and more convinced it must be a problem on his side, not ours. And I found out that the email address where we send the mails to is not an exchange server but a mail account hostet by his provider and there it's forward it to a Microsoft exchange address (like bla.bla.bla@companyname.onmicrosoft.com). And it's that exchange server that rejects the mails. So I guess hat when the emails are forwarded to the onmicrosoft.com domain, something happens to the email that makes the microsoft server reject them.

That would explain a lot. Except that when I send the emails using Outlook (classic) instead of our application using *web/email, then the mails aren't rejected. Maybe this is because Outlook creates the headers differently than *web/email. Anyway it's just like my father said: we use computers to solve problems we wouldn't have without them 

Update 5th March 2026: The problem is now solved. We found out that the customer forwarded his incoming e-mails (hosted by his providers mailing servers) to the exchange server (hosted by Microsoft) and that this forwarding caused DMARC tests to fail. Now he rearranged his email structure and that solved the problem. Thanks to Mike King and yonman for your help!

Stay up to date with everything happening at PVX Plus.

Check out our latest newsletter for important updates:

• .NET Interface User Group Update – Discover the new enhancements coming in 2026
• New VS Code Features – Recently added improvements based on User Group feedback
• Using Temporary License Activations

February 2026 Newsletter

We're already doing this, as a "pre-view".
Here's what we're really trying to do: In our software we have a universal printer handler, and all print jobs go through it so the end-user can select either "PDF" or to a printer. With some destructive print jobs we will only allow printing to printer for auditing purposes.
For security purposes browsers are not permitted to expose local resources so the only way that we can really provide a printing solution for these print jobs is to either print to PDF and let the PDF print to the local printers or to an HTML page and provide access to the local printers. For regular print jobs (text) the browser print works as you can access via CTRL P or using a print button on the page which gives a list of local printers. What is happening is that when we use *HTML* for those printouts that use the graphic print rather than the text we render a blank page and not a graphic printout. We can get a PDF, but the logic for "previewing" will not allow for "updating" the print job. HTML is the right choice, but not for graphics.
Do I need to implement a PDF to HTML converter for these jobs?

How about creating a PDF and downloading it?

Hi Jane, thank you for your suggestion, but that would mean that ALL our print programs would need to be processed via the report writer. (Nearly 300 programs)

We have plain text printouts now being processed via the *HTML* file type and this is a good solution.
Our issue now is any of the graphic forms that we print, like invoices, statements etc. These forms render via PDF properly, but when directed to HTML the result is a blank web page.

Any or all suggestions would be appreciated. Thank you in advance.

Mike.

I don't know if this would be applicable to your case, but you might consider using the Report Writer as it can create HTML output.

You are very welcome.  Always happy to help.