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

xml import and wrong data type

Avatar

Level 2

Hi all !

I have a form, i want to import xml data.

In the data xml : when i put a string value in a numeric field (mistake) and the i import the data into my form :

Acrobat does not tell me there is a 'format' error but instead the 0 (zero) value is put is the field.

Is there a way (early event) to detect a data format error in the xml ?

Thank you

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Not that I am aware of .....it tries to bind the imbound field to the field named on the form and if it can you will see your data ...otherwise it will not appear.

It is assumed that the inbound data has been validated against the schema before the import is done hence there should not be data type mismatches.

paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Not that I am aware of .....it tries to bind the imbound field to the field named on the form and if it can you will see your data ...otherwise it will not appear.

It is assumed that the inbound data has been validated against the schema before the import is done hence there should not be data type mismatches.

paul

Avatar

Level 2

Thanx a lot Paul for your quick answer !


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] ----