You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Ashish Vijaywargiya (JIRA)" <ji...@apache.org> on 2014/08/16 16:00:39 UTC
[jira] [Closed] (OFBIZ-4973) AvsSettings screenlet read data bug,
entity-one should be used, not entity-and
[ https://issues.apache.org/jira/browse/OFBIZ-4973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashish Vijaywargiya closed OFBIZ-4973.
--------------------------------------
Resolution: Fixed
Thanks Oliver and team ofbiz.us. Changes are pushed to trunk at r1618359 and to RB13.07 at r1618361.
> AvsSettings screenlet read data bug, entity-one should be used, not entity-and
> ------------------------------------------------------------------------------
>
> Key: OFBIZ-4973
> URL: https://issues.apache.org/jira/browse/OFBIZ-4973
> Project: OFBiz
> Issue Type: Bug
> Components: party
> Reporter: Olivier Heintz
> Assignee: Ashish Vijaywargiya
> Priority: Minor
> Attachments: OFBIZ-4973.patch
>
>
> On Party ViewProfile screen (or PartyProfile PortalPage) in AvsSettings screenlet, the user entry value is never shown because database request in screen action is wrong.
> Entity PartyIcsAvsOverride has only one PK which is partyId so
> {code}
> <entity-and entity-name="PartyIcsAvsOverride" list="avsOverride">
> <field-map field-name="partyId" from-field="partyId"/>
> </entity-and>
> {code}
> should be replace by
> {code}
> <entity-one entity-name="PartyIcsAvsOverride" value-field="avsOverride">
> <field-map field-name="partyId"/>
> </entity-one>
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)