Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Issue with generating a PDF by requesting from AEM 5.6 to forms 6.4

Avatar

Level 2

Hey Guys,

We are currently performing migration from 5.6 to 6.4 but we need to support an application in AEM 5.6 to send a request to Forms 6.4 to generate a PDF. Initially we were generating using 6.2 but now we are moving to 6.4.

I am able to generate a PDF if i request it from AEM 6.4 but i am getting an error if i request it from AEM5.6

Below is the error. Any help would be appreciated.

Thank you,

~Swetha

31.08.2018 13:23:48.540 *ERROR* [RequestProcessor-1] com.adobe.document.XMLFormService ALC-XTG-001-021: [13544] XMLForm, load : 12309, XFA data Model is empty.

31.08.2018 13:23:48.540 *ERROR* [127.0.0.1 [1535736228295] POST /aem-services/fundstory HTTP/1.1] com.adobe.forms.aem.impl.XFANativeServiceImpl <?xml version="1.0" encoding="UTF-8"?>

<status

><messages

><m mid="12309" tid="13544.23404" sev="f" d="2018-08-31T13:23:48.536-04:00"

>XMLForm, load : 12309, XFA data Model is empty.</m

></messages

><validationWarnings

/><validationErrors

/></status

>

1 Accepted Solution

Avatar

Correct answer by
Level 2

This issue was resolved. I had special characters in the json which was creating the issue. It was painful to find it!

View solution in original post

5 Replies

Avatar

Employee Advisor

Swetha,

Can you please give detail on how you are invoking the PDFG service from 5.6 and 6.4? Also, Did it worked previously when you invoke the d same service from 5,6 to 6.2?

Avatar

Employee Advisor

Also, why would you run and support an application on a version(5.6) which is even end of extended support[1].

[1] All Apps Help | Products and technical support periods

Avatar

Employee

It sounds to me that the you are not passing in all the inputs necessary to render the PDF (dynamic or flat?). How are you calling either the Forms or Output API?

Avatar

Correct answer by
Level 2

This issue was resolved. I had special characters in the json which was creating the issue. It was painful to find it!

Avatar

Level 2

We are currently migrating and still have to support the existing application for our customer base.