Skip to Content

Bind multiple fields to one node in data view

I have a need to have an interactive form where data from a single data source is displayed in multiple fields on the form. In addition these fields are open for input. I have bound the multiple fields on the form to one node in the data view. The data is being displayed in the multiple fields. This form is being routed thru workflow so various agents are updating the form. The problem that I am having is that the form only seems to allow input in the first field on the form but not the other fields that are tied to the same data source. For example, field A and field B are bound to node SUMMARY. I can add/change/delete data in field A but not in field B. After I have done some entry in field A, I can then sometimes make changes in field B. We have a requirement that field A be enabled for agent #1 but field B is invisible. Later in the workflow, agent #2 needs to make final changes on a "summary" page so agent #2 had field B enabled.

Does anyone have any idea how to correct this data entry issue so that data can be entered into either field that is tied to a single node?

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Nov 10, 2009 at 03:57 PM

    Data binding can be very tricky. I don´t think it is possible to anything like the thing you want.

    I don´t even understand why would you need to do this. If (workflow or not) the data are seen multiple on the form, it is because some difference should be noticed (like one field combines two fields using concatenate string function or something like that).

    I can understand you need multiple instances of one data field to get multiple version from various people. But why would you do such a thing using a single field?

    - In ABAP coding you wouldn´t do such a thing. You would add "change lines" to the initial value or something like that.

    - Or you would change the infotype and note down who has changed the value, but you would limit the validity of the value, do not just change it.

    - Or if multiple users in ERP would change the single field. You would note down the history of the changes, who did it, when etc.

    My recommendation is:

    create a structure with fixed number of "rows", like VER1, VER2 etc.

    bind your form fields to the proper "versions" of the initial field (can be called VER0 or something...).

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 12, 2009 at 08:08 AM

    I wish you good luck with our solutions. I think neither will work and if so (by chance), nobody will be able to change this app but you in the future. This is not the way the form app should be structured.

    You should use multiple backend fields, or at least multiple form fields but only one has the interactibe binding and the others get their values by the hardcopy.

    Let us know, how did you finish your app, I am curious about it. Have a nice day, Otto

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.