Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Submitting form to asp.net server

Avatar

Level 1

Hello,

I have several questions about submitting forms to asp.net server.

Let's say I have a form which submits data to asp.net server and submit format is xml data. If the pdf file contains an image will it be included too? If yes what will be the format of the image?

Secondly, if some of the fields are not filled, will they be included in the xml files as empty fields or will they be omited from the xml file altogether?

Finally, after processing the posted data I would like to display a message to user e.g: success or failure. How can I achieve it? I believe I need to set the Response but what should be the format of the response? Will just a plain text work?

Thank you.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Yes I believe so.

Paul

View solution in original post

4 Replies

Avatar

Former Community Member

1. The inage will be included if you are using an image field. It will be base64 encoded in the image field tags.

2. The only time the fields will not be included in the data file is if the binding is set to None or there is a bad binding expression for what you are trying to do.

3. If the form is being displayed in a browser you can send back an HTML formatted message. If it is being displayed in standalone Acrobat/Reader then you must send back a PDF with the message in it

Paul

Avatar

Level 1

Thank you for your answer.

Will it work with Reader if I just do Response.Redirect("somewebsite.com/somefile.pdf"); ?

Thanks

Avatar

Correct answer by
Former Community Member

Yes I believe so.

Paul

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----