Genexus Sub-level Grid in Transaction

Question

I have a transaction with sub-levels

In the Transaction Web Form, I have the grid for it, but without conditions, and as I have a lot of records in this sub-level transaction and it loads all of them, there is a performance problem and a timeout error.

If I remove the grid, I have this compilation error: error: spc0104: Grids are mandatory for all levels but the first one..

As an example, I have this Transaction (and the table filled)

State
* StateId
StateName
StateCities
  * StateCityId
  StateCityName

There is a way to solve this o I have to delete the sub-level and make all the logic by myself?

Thanks a lot, Ariel

I'm sorry, but questions must be in English and accompanied with a [mcve]. — jonrsharpe, Jul 20 '16 at 19:11
Sorry for the language, I saw a lot of questions in Spanish I thought it was possible, and now there is an example. Thanks! — Ariel Laniado, Jul 20 '16 at 19:22
Ariel you can post on Spanish at http://es.stackoverflow.com where there's also an active Genexus community — sebagomez, Jul 20 '16 at 21:22

score 0 · Answer 1 · answered Jul 21 '16 at 01:14

0

Ariel,

You might created another transaction (with only one level) with the compound keys, like this:

*StateId *StateCityId StateName StateCityName

And insert, update or delete one by one

But I, personally, prefer not to use this approach but yes to create one webpanel (crud style)...

answered Jul 21 '16 at 01:14

Sandro Magrinelli Vianna

140
7

Thanks a lot, thats are my options, but I prefer the Genexus one, that's why ask – Ariel Laniado Jul 21 '16 at 20:38
In that case, I don't think the sub-levels are usefull for anything – Ariel Laniado Jul 22 '16 at 15:26

score 0 · Answer 2 · answered Jul 28 '16 at 13:11

When you have a two-level Transaction in GeneXus, you are saying that the data in that transaction must be managed as a whole. That's why GeneXus won't let you remove the second level's grid from the Form.

What you need to do, if you want to manage the two levels separately, is to have two different transactions, one for each level.

In your case, the structure of the transactions would be:

-- State
* StateId
StateName

-- StateCities
* StateId
* StateCityId
StateCityName

And then, by applying the WorkWith pattern to both transactions, you'll be able to work with them separately.

Genexus Sub-level Grid in Transaction

2 Answers2