XBasic Handling of Repeating Sections

[DVD528]

We just discovered something about the way XBasic (in particular the AfterDialogValidate server side function) handles repeating section data.

We are currently trying to construct a SOAP call based on submitted data. One of the sections in the SOAP call contains a repeating section of fields, so we match it with a repeating section on our form. We loop through by using something similar to the following code:

FOR i = 1 TO e.dataSubmitted.field.size()
    xmlVar = xmlVar + <<%xml%
<xmlField>{e.dataSubmitted.field[i]}</xmlField>
%xml%
NEXT

xmlVar = evaluate_string(xmlVar)

Etc etc. That's just a very slim example of the code we are using, but it describes the issue.

Our issue is, apparently in the way XBasic handles the e.dataSubmitted for repeating section rows, it takes the physical row number, and therefore takes deleted rows into account.

For example: Say we have a repeating section with 4 rows, and we delete the 3rd row, so now only 3 rows remain. e.dataSubmitted.field.size() will be 4, and e.dataSubmitted.field[3] will contain the value of the field in the 3rd repeating section row that was deleted, and not the 4th row that became the 3rd row.

I need to know if there's a simple way to make this loop only get data from the Logical rows, not the physical ones. I don't care about deleted rows, since they are deleted, and obviously I won't be using them.

Thanks.

[Steve Workings]

Re: XBasic Handling of Repeating Sections

Have you looked at some prototype code for a callback? It has all of what you need. Here's some that is immediately useful, and check out the .deletedRows property.

'--------------------Repeating Sections ----------------------------------------
'If your dialog contains repeating sections, data in the repeating sections will be in an array.
'For example, say that your dialog has a repeating section that includes a field called QTY:
'e.dataSubmitted.qty[1] - contains data from first repeating section row
'e.dataSubmitted.qty[2] - contains data from second repeating section row, etc
'e.dataSubmitted.qty.size() - number of entries in the array.

'In addition, the e object will contain information about the repeating sections
'e.repeatingSectionNames - a comma delimited list of the name (container ID) or each repeating section
'e.repeatingSectionInfo - a property array with one entry for each repeating section.
'The e.repeatingSectionInfo[] array will have these properties for each entry:
' - .activeRow - the row in the repeating section that had focus when the Dialog was submitted
' - .deletedRows - a CRLF delimited list of rows that were deleted. e.g. 1 and 3
' - .rowCount - a count of the number of non-deleted rows
' - .totalRowCount - a count of all rows in the repeating section including rows that were deleted
' - .fieldsInRepeating section - a CRLF delimited list of fields in the repeating section
' - .dirtyRowsInSection - a CRLF delimited list of rows in the repeating section that were edited. (A row that was edited, then deleted will still appear in this list).
' - .dirtyFieldsInSection - a CRLF delimited list of fields in the repeating section that were edited. for example: PARTNO_A5INSTANCE3 is the 'PARTNO' field in row 3.
'-------------------------------------------------------------------------------------------

[DVD528]

Re: XBasic Handling of Repeating Sections

Yep, looked at all of that already.

I considered writing a loop that would be something similar to the following:

FOR i = 1 TO e.repeatingSectionInfo[1].totalRowCount
    if .NOT. word_exists(e.repeatingSectionInfo[1].deletedRows, convert_type(i, "C")) then
        ' Code to handle data in the event that it's not in a deleted row
    end if
NEXT

But I wanted to see if there was a simpler way. I assumed there was a simple way to access only the Logical rows, i.e. the rows that actually exist on the repeating section, excluding deleted ones, in a way like the current existing way (e.dataSubmitted.rs_control[1]) that I just didn't know about.

If there is no other way to ONLY get the data from the rows that were not deleted at the time of submission, then I guess I'll implement the fix that I described.

I would still like to know if anyone has any other possible solutions.

[GGandhi]

Re: XBasic Handling of Repeating Sections

take a look at video d30 in version 11, there is a method to relate the logical rows to physical rows, you should be able to use that property.
repeatingSection[1].logicalRowToPhysicalRowMap property.
that video will give some hints to make use of this property.

[[email protected]]

Re: XBasic Handling of Repeating Sections

Hi David

There is a variable that is created that I make use of in this situation; I use it for all repeating section when I am working with them so the variable is

e.repeatingSectionInfo[1].visibleRows

and this is how I use it

LIST1 = e.repeatingSectionInfo[1].visibleRows
list1 = crlf_to_comma(list1)
for i = 1 to e.repeatingSectionInfo[1].totalRowCount
	Vrow = convert_type(i,"C")
if inlist2(Vrow,list1) = .t. then

So if vRow (which is the Logical Row Number) is in list1 (which is the visible rows) then I work with the row if not visible just move on to the next row

Hope it helps

Andy

[DVD528]

Re: XBasic Handling of Repeating Sections

Hi Andy,

Thanks for the response.

I actually just implemented the code that I listed above:

FOR i = 1 TO e.repeatingSectionInfo[1].totalRowCount
    if .NOT. word_exists(e.repeatingSectionInfo[1].deletedRows, convert_type(i, "C")) then
        ' Code to handle data in the event that it's not in a deleted row
    end if
NEXT

And it seems to have worked perfectly.

I was hoping there was something like a secondary array of e.dataSubmitted.rs_control_logical[] or something that would make it easier, but it doesn't seem like there is.

Thanks for all the suggestions.