You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ofbiz.apache.org by "Kevin M. Myer" <km...@gmail.com> on 2010/05/20 22:49:57 UTC

Re: Not able to update Company postal address

Sorry to dredge up an old thread, but I have run across this issue
while trying to setup a demo site for internal testing.  Is there any
resolution to this issue in the works or are potential users left to
test with only static seed data?  I'd like to test with a real company
name, organizational structure and a few facilities, so folks can
grasp what Ofbiz can really do.  I realize ERP packages are complex
but figuring out how to change a company address should not be the bar
to entry :)

Thanks,
Kevin

On Wed, Feb 17, 2010 at 2:18 PM, BJ Freeman <bj...@free-man.net> wrote:
> The N/A record was created to take care of data missing or not yet put in.
> of the top of my head it would be a change in the entity engine to
> create  N/A records if it does finds records to satisfy the request.
>
> From a UI point of view if N/A record is found then an action to prompt
> the user for data.
>
> This would take a lot of refactoring at the UI level.
>
> the work around is to put a N/A record in the seed data
>
> my 2 cents.
>
>
>
> Abdullah Shaikh sent the following on 2/17/2010 6:42 AM:
>> I have checked this issue, the error is because the seed data doesn't have
>> nameOnAccount for EftAccount entity, and when the updatePaymentMethodAddress
>> seca service is called when you update the party's postal address, in it
>> turns calls the updateEftAccount service which has nameOnAccount set to
>> optional="false", this results in error.
>>
>>>>From business point of view is the  account name (nameOnAccount) of bank
>> account (EftAccount) mandatory ?
>>
>> If yes then we need to have nameOnAccount set in seed data and if no, then
>> we need to make nameOnAccount field optional in updateEftAccount.
>>
>> Let me know if nameOnAccount shoud be mandatory or not, so that I can
>> provide a patch.
>>
>> I have raised a jira for this at
>> https://issues.apache.org/jira/browse/OFBIZ-3485
>>
>> - Abdullah
>>
>> On Tue, Feb 16, 2010 at 8:07 PM, Ashish Vijaywargiya <
>> vijaywargiya.ashish@gmail.com> wrote:
>>
>>> Glad to know that you are well. :-)
>>> I'll explore and will get back to you?
>>>
>>> --
>>> Ashish
>>>
>>> On Tue, Feb 16, 2010 at 7:54 PM, Abdullah Shaikh
>>> <ab...@gmail.com> wrote:
>>>> Hey Ashish, I am fine, thanks :)
>>>>
>>>> Yes, I am using trunk, any issues with this flow in trunk code ?
>>>>
>>>> - Abdullah
>>>>
>>>> On Tue, Feb 16, 2010 at 7:48 PM, Ashish Vijaywargiya <
>>>> vijaywargiya.ashish@gmail.com> wrote:
>>>>
>>>>> Hello Abdullah,
>>>>>
>>>>> How are you?
>>>>> One quick question: Are you using trunk?
>>>>>
>>>>> --
>>>>> Ashish
>>>>>
>>>>> On Tue, Feb 16, 2010 at 12:35 PM, Abdullah Shaikh
>>>>> <ab...@gmail.com> wrote:
>>>>>> When I try to update the Company's Postal Address using the Update
>>> button
>>>>> in
>>>>>> Profile's Contact Information section, I get the below error,
>>>>>>
>>>>>> The Following Errors Occurred:
>>>>>>
>>>>>> Error trying to begin transaction, could not process method: The
>>> current
>>>>>> transaction is marked for rollback, not beginning a new transaction
>>> and
>>>>>> aborting current operation; the rollbackOnly was caused by: Service
>>>>>> [updateEftAccount] threw an unexpected
>>>>>> exception/errororg.ofbiz.service.ServiceValidationException: The
>>>>> following
>>>>>> required parameter is missing: [updateEftAccount.nameOnAccount] (The
>>>>>> following required parameter is missing:
>>>>> [updateEftAccount.nameOnAccount])
>>>>>>
>>>>>> 1) From the error it seems that while updating the Postal Address it
>>> also
>>>>>> calls the updateEftAccount service. why does it call this service ?
>>>>>> 2) Even if it calls this server there is no input fields related to
>>> this
>>>>>> service on the update Postal Address page.
>>>>>>
>>>>>> or if its like that we need to update the Account details to reflect
>>> the
>>>>>> Company's updated Postal Address ? then we need to handle case for
>>>>>> nameOnAccount
>>>>>>
>>>>>> Should I raise a jira for this ?
>>>>>>
>>>>>> - Abdullah
>>>>>>
>>
>
>