Special objects are generated for each group view. The first is the group view object itself. This object holds the Capacity or the maximum number of rows specified in the model. The object also holds the Length or the current number of populated rows in the group view. The Length cannot exceed the Capacity or be negative. If you try to do so, it throws IndexOutOfRangeException or ArgumentOutOfRangeException.
For import groups, the Capacity property is considered read only, while the Length property is read/write.
Note: It is the responsibility of the user written application to set the import repeating group Length property appropriately before flowing to a server. Failure to do so will result in the view data not being processed properly.
For repeating export groups, the user written application should consider both the Capacity and Length properties to be read only.
To store row data, an object is generated. The object represents a row and contains references to all the entity and work set views within the GroupView. This group view object then stores an array of row objects to hold the data. An individual row can be accessed by indexing the Rows property on the group view, or by using the indexer property built into the group view object itself.
Having a row of data represented as an object enables certain row-level operations to be performed, such as looping, cloning, resetting, and tostring.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|