cancel
Showing results for 
Search instead for 
Did you mean: 

Interactive Form in WD ABAP, Blocks WEB page Interaction.

Former Member
0 Kudos

SCENARIO:

ABAP web dynpro with UIelement for interactive form display and editing.

1- 1st Web dynpro view with IForm element, (enable option = True) so user can edit the IForm.

2- Data node for Binding has 0-n cardinality (so in IForm a dynamic table will be generated)

3- 2nd Web Dynpro View, UI FileUpload for Iform Upload.

PROBLEMS:

1 - On Upload view, I tried the the Auto-Binding combining FileUpload and UI IForm element (as sap note) but dosen't work. For now I solved the problem the old way, converted the xml from binary to string, parsed the XML and then did backward-data-binding.

2- On PDF display view, the pdf is displayed correctly and it's editable, but any other actions user tries to do on the web page don't work.

2.1 I have a (navigate back) button on the web dynpro, but once the pdf is displayed, no interaction with the web page is possible.

NOTE: when enable option = FALSE, everything works ok, but Form is no more editable.

Can't find any sap notes that solve the problem, Help needed....

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

OK,

then forget about the popup window, for a moment...

I wrote:

At FIRST, I tryed it in a normal web Dynpro View, and it didn't work anyway... the problem is the same!

The popup window was just a test, to see if I could close the popup PDF preview with the default X button...

Former Member
0 Kudos

One more thing:

If I put the view that contains the Iform in a popup window, I get this error when I try to close the popup, or any action on the popup window:

__________________________________________________

Short text

The ASSERT condition was violated.

What happened?

In the running application program, the ASSERT statement recog

situation that should not have occurred.

The runtime error was triggered for one of these reasons:

- For the checkpoint group specified with the ASSERT statement

activation mode is set to "abort".

- Via a system variant, the activation mode is globally set to

for checkpoint groups in this system.

- The activation mode is set to "abort" on program level.

- The ASSERT statement is not assigned to any checkpoint group

************************************************************************

method create_by_view_element.

data:

class_registry_entry type t_class_registry,

mappings type standard table of wdr_elem_ap

mapping type wdr_elem_apt_map,

elem_defs type sorted table of wdy_ui_elem_d

elem_def type wdy_ui_elem_def,

new_entries type standard table of t_class_reg

adapters type sorted table of wdr_uiel_adap

adapter_def like line of adapters,

id_gen_entity type string.

if view_element is not bound.

==> assert 1 = 2.

endif.

read table m_class_registry into class_registry_entry

with table key view_element_cid = view_element->_cid

thomas_jung
Developer Advocate
Developer Advocate
0 Kudos

>If I put the view that contains the Iform in a popup window, I get this error when I try to close the popup, or any action on the popup window:

That is a documented limitation of the InteractiveForm UI element. It can not be placed in a popup window. Note number: 1098009

Former Member
0 Kudos

First of all Thanks for the response.

I have already read that sap note, but I tried it anyway. With a static print Form the popup works, for my needs, but when the enable option is ON, the web page behaves the same way as if it whas in a normal WD view.

I tried debuging it, but after IForm rendering, there is no way to interact with the Web Dynpro. No event is raised and no execution is done in WD, looks like WD is dead... No interaction, no dump... it just keeps loading....

Other ideas?

thx.

thomas_jung
Developer Advocate
Developer Advocate
0 Kudos

>

> I have already read that sap note, but I tried it anyway.

Why? SAP just told you via the note that it doesn't work and we won't support any attempts to get it to work.