Regarding updateonactivate

navinb

hi ,

in classic the property updateonactivate is not set on posted document form.I think it is done as the form are posted and may not be updated .Also is it a best practice to set it on all editable form ?
Is that for someother reason .

Also setting that has any performance impact ?

Thanks in advance

mohana_cse06

here is a good example
http://www.mibuso.com/forum/viewtopic.php?f=23&t=21445&view=previous

navinb

Thanks for reply!!
But still it doesnt answer my query :
> Its gud to have form refreshed with latest info ,then why journals and posted documents are not having the property set.
> Is there any performace impact ?

mohana_cse06

navinb wrote:

> Its gud to have form refreshed with latest info ,then why journals and posted documents are not having the property set.

What do you modify in Posted Documents?

navinb wrote:

> Is there any performace impact ?

Not much as it just need to get the data from table and show..

navinb

Journal forms can be modified and if the performance cost is too low why standard NAV doesnt have the property set on Journal forms.

navinb

Also when the property is set some of the form triggers are fired twice.And if there is not check for repetetive execution it will defintely kill performance .