unnecessary data access in widgets

[BJ Freeman]

Albeit I am not an expert on widgets, I am finding what I believe is
extra code that accesses data and it is never used. this creates
unnecessary overhead in processing.
I ran across this when looking for example of using the tree widget.
GlobalGlAccountsScreens.xml#GlAccountNavigate
has a action element with
 <entity-one entity-name="GlAccount" value-field="glAccount"/>
yet I could not find any where in this screen or in the Tree screen
where glAccount was used

Am I missing something or is this extra code.

[Bilgin Ibryam-2]

May be it is used in EditGlAccount form?

Bilgin

On Sun, Jul 3, 2011 at 4:48 PM, BJ Freeman <[hidden email]> wrote:

> Albeit I am not an expert on widgets, I am finding what I believe is
> extra code that accesses data and it is never used. this creates
> unnecessary overhead in processing.
> I ran across this when looking for example of using the tree widget.
> GlobalGlAccountsScreens.xml#GlAccountNavigate
> has a action element with
>  <entity-one entity-name="GlAccount" value-field="glAccount"/>
> yet I could not find any where in this screen or in the Tree screen
> where glAccount was used
>
> Am I missing something or is this extra code.
>
>