UX List Control set value on save/ sync

[Scott Emerick]

Hi All,

Does anyone know how to set values on a UX control that is bound to a list control detail view? I am trying to do a time stamp of sorts which includes user name. The normal methods do not seem to apply when dealing with a list control detail view.

Thanks in advance.

Scott

[frankbicknell]

Re: UX List Control set value on save/ sync

If your list is a child list with a parent list and you are pre-loading the data. The only events that fire are the events from the parent list detail view. If you do not pre-load data then the events in the detail view of the child lists will fire.

Here is some info from Selwyn that cleared up a lot of misunderstanding for me.

basically if you have a ux with 4 lists that are hierarchical
for example

list1
=====> list2
=====> list3
=====> list4
======> list5


then even though you have 5 physical lists -- we consider this to be one logical list (list1), (since list2 through list5 are all children of list1)

synchronizing ANY of the lists in this hierarchy is equivalent to synching list1 -- the top-level parent list - (since list1 has all of the data for all of the child lists nested in it)

so synching list5 is the same as synching list1 and synching ALL lists in this case is also the same as synching list 1.

in other words, when you have hierarchical lists you cannot sync one of the child lists as if that list were an independent list. synching a child list automatically does a sync on the top level parent of that child list.

now take the case of a more complex ux that has has


list1
=====> list2
=====> list3
=====> list4
======> list5

listA
=====> listA1
=====> listA2


In this case the UX has TWO top-level lists, List1 and ListA

you can use the synch all command to sync list1 and ListA or you can sync just list 1 or list A independently.

hopefully, this helps you understand how it works?

[Scott Emerick]

Re: UX List Control set value on save/ sync

Frank,

Thanks, that is helpful information, but not what I am looking for.

I want to set a value of a UX control that is bound to the List Detail view. I only have one list. In a data bound UX I would use something like {dialog.Object}.setValue('MYCONTROL'); in the after validate event, That would put a value in a field(control) right before it saved. This would be a hidden control that the user has no interaction with.

I want to be able to do the same thing with a List Detail View. I see some detail view events that can possibly be used, but its the syntax I am stuck on. The help says there is a "data" parameter that can be used, but my attempts failed.

I want to set a value to a hidden field right before the List Detail is saved/ sync'd

Thanks,

Scott

[Peter.Greulich]

Re: UX List Control set value on save/ sync

Hi Scott,

Take a look at the list/detail tab validate event. You can refer to a function that you put in the xbasic functions area. Here are a couple I'm using on one UX:

Function xbDetailUpdate as p (e as p)
'This function validates the data that are submitted to the server when a List control is synchronized
'debug(1)

''UPDATE DATA & SYNC FLAG

IF e.data._isNewRow = .f.
	if e.data._oldData.Synch_Flag <> "N"
		e.data.Updated_By = session.User_Id
		e.data.Updated_Dt = now()
		e.data.Synch_Flag = "E"
	End If
End If
End Function



function xbChildUpdated as p (e as p)

	vLink = e.data.INVOICE_LINK
	f_UpdateSynchFlag(vLink)

End Function

[Scott Emerick]

Re: UX List Control set value on save/ sync

Peter,

Thank you so much ... That's exactly what I need. I was trying to do it client side.

Thanks again!

Scott

[frankbicknell]

Re: UX List Control set value on save/ sync

You can do it client side. Look at the client side events under the detail view tab. canSynchronizeList is a good one that fires before the synchronization process. There are about 40 client side events available. Much quicker than doing a callback.

Just set the value of the control with the value of another control or a state variable.

Ps. the only caveat is that your variables (fields) need to be hidden on the client side.