Committing data in a repeating section

[jtm311]

On my UX component I have two repeating section the first is a read only repeating section from a dbf table.

On the second repeating section I allow the user to enter a few field into the repeating section and pull four fields from the above repeating section by adding the read only field name into the Calculated Field expression. On the screen all the fields show the correct data, however when submitting the data the four field I pull in from the above section do not commit to the table.

Using Debug(1) I see the data is in the e.dataSubmitted.PN[1], however it is not saving into those fields.

If I read the information in afterdialogValidate I do not think the e.dirtyColumns = e.dirtyColumns applies to committing data for repeating row?

Any help in committing the data from a repeating row.

John

[GGandhi]

Re: Committing data in a repeating section

usually it is the dirty columns.
when the calculated expression work they don't dirty the columns. so try that out first.

[jtm311]

Re: Committing data in a repeating section

Thanks I understand but how do you force a repeating section field to go dirty? Do I use {dialog.Object}.setDirty(); ?

Thanks for the help.

[GGandhi]

Re: Committing data in a repeating section

see the documentation in afterDialogValidate in version 12 may be just Dialogvalidate event

'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.

that will shed some light.

[jtm311]

Re: Committing data in a repeating section

Thanks took me a few times reading it :)
But the following worked.

e.dirtyColumns = e.dirtyColumns + crlf() + "PN_A5INSTANCE1" + crlf() + "PN_A5INSTANCE2" + crlf() + "PN_A5INSTANCE3" + crlf() + "PN_A5INSTANCE4"

[GGandhi]

Re: Committing data in a repeating section

very good. but that is not going to help if there are more lines added or less lines in the repeating section.
if i have time this weekend i will see if i can post an example, you should cycle thru the line numbers and add them to the dirty columns. ( unless someone posts earlier than me of course, there are plenty of nice people on this board)

[jtm311]

Re: Committing data in a repeating section

Thanks Gandhi I wondered if there is a way to loop through, however it did work when I use one record or three records. A loop would be a better solution.

John

[GGandhi]

Re: Committing data in a repeating section

dim rowNumber as n
	rowNumber = e.repeatingSectionInfo[1].rowCount
	for i = 1 to rowNumber
		e.dirtyColumns = e.dirtyColumns + crlf() + "PN_A5INSTANCE"+i
	next

see if this works in place of the hard coded dirty columns.
hard coding will work, if the number exceeds the hard coded limit then it won't.
(ps: i have only one repeating section section number for me is [1])

[GGandhi]

Re: Committing data in a repeating section

dim dirtyRows as c
	dirtyRows = e.repeatingSectionInfo[1].dirtyRowsInSection
	p = *string_to_array(dirtyRows)
	n1 = p.size()
	for i = 1 to n1
		e.dirtyColumns = e.dirtyColumns + crlf() + "PN_A5INSTANCE" + p[i]
		next

this will have only those rows edited. pick your choice and see which works best for you.

[jtm311]

Re: Committing data in a repeating section

Thanks Gandhi I will try first thing in the AM.

John

[WindForce]

Re: Committing data in a repeating section

dim dirtyRows as c
	dirtyRows = e.repeatingSectionInfo[1].dirtyRowsInSection
	p = *string_to_array(dirtyRows)
	n1 = p.size()
	for i = 1 to n1
		e.dirtyColumns = e.dirtyColumns + crlf() + "PN_A5INSTANCE" + p[i]
		next

this will have only those rows edited. pick your choice and see which works best for you.

Hi Gandhi
I am having the same issue with a repeating section i populated programatically. Should i use this (quoted) method, or the previous one ( that will dirty, i think, even deleted rows)?

Jaime

[GGandhi]

Re: Committing data in a repeating section

jaime,
both will do exactly the same. first one will state all rows are dirty if if they were not, for example you have 5 rows and edited only three rows the first one will say all 5 rows are dirty(including any rows that were edited and deleted) a brute force method.
the second one will dirty only edited rows, for example if you have 5 rows and edit only 3 or 1, 3 and 5 it will pickup those rows only (including the rows that were edited but deleted ), more finesse. that's the only difference as far as i know.

[jtm311]

Re: Committing data in a repeating section

dim dirtyRows as c
	dirtyRows = e.repeatingSectionInfo[1].dirtyRowsInSection
	p = *string_to_array(dirtyRows)
	n1 = p.size()
	for i = 1 to n1
		e.dirtyColumns = e.dirtyColumns + crlf() + "PN_A5INSTANCE" + p[i]
		next

this will have only those rows edited. pick your choice and see which works best for you.

Worked perfect thanks for the help.
John

[WindForce]

Re: Committing data in a repeating section

Thanks for the explanation gandhi...
Alas, this doesn't completely fix the issue for me. Will keep on playing with this

[GGandhi]

Re: Committing data in a repeating section

Alas, this doesn't completely fix the issue for me. Will keep on playing with this

what was the problem you had?