Avoid creating additional documents with tables data after submitting the form

HCL Leap Leap Forum
,
1

Hi,

I have a form. In a hidden section I have several tables that are populated with data using services.

Problem:

After submitting the form, I open the document in Notes and at the bottom of the page I see many new documents created with data from the hidden tables.

Is there a way to avoid creating these documents?

Thanks for any help.

2

This is how DLeap is implemented, you can not avoid that. And there is nothing wrong regarding this way of DLeap -> Domino mapping. IMO people are not expected to work with DLeap apps via Notes client...

3

Thank you Jan for reply.

I am worrying about space and performance.
Because on creating one document on submit event ,it creates more than 100 other mapped documents from my tables data.

4

That's why I say that tables are evil :-) You should rather avoid them.

I used to have apps with 10 pages, 10 stages and 10 tables and I have got rid of them because everything was so slow (opening an app, saving an app, form submission, etc.)

5

How can this problem be solved? beside using REST API

6

Datagrids can be used instead of tables in most scenarios, however they support only main forms (in Dleap or in NSF). Tables in DLeap create subforms in NSF and therefore they are not accessible via DataGrids.

Also tables are used always in context of a specific BO (=submitted form) while Datagrids can display other BOs. This is very useful on application pages.

7

Thank you Jan for help

8

If you are using tables, for rendering, then it is important to clear them before submitting the form so that you do not have all the extra data stored when it is not necessary.

I suspect that if you just cleared the tables before submitting, it would address your concern.

9

Hi Christopher,

I tried running the search service with parameters that did not find anything in the database.It works.
Is there another approach to cleaning tables?

Thank you in advance.

10

To clear a table you call BO.F_Table1.setValue("")

11

By a chance I found my old AHA idea https://domino-ideas.hcltechsw.com/ideas/VOLT-I-264

If BO.F_Table1.setValue("") works then you can close it :-)