Thanks Pawan!
Le 23/05/2020 à 20:58, Pierre Smits a écrit :
Thanks Pawan, for the quick action.
Op za 23 mei 2020 20:16 schreef Pawan Verma :
Hello Everyone,
I dig around the issue and found that getPartyNameForDate is the main
culprit for this issue. It can be easily generated on the local
Thanks Pawan, for the quick action.
Op za 23 mei 2020 20:16 schreef Pawan Verma :
> Hello Everyone,
>
> I dig around the issue and found that getPartyNameForDate is the main
> culprit for this issue. It can be easily generated on the local instance by
> updating the admin's name.
>
> Updating nam
Hello Everyone,
I dig around the issue and found that getPartyNameForDate is the main
culprit for this issue. It can be easily generated on the local instance by
updating the admin's name.
Updating name will create a new record in PartyNameHistory entity and
service getPartyNameForDate has an iss
Hi Pawan,
It seems related to this error:
Caused by: org.apache.ofbiz.service.GenericServiceException: Error running Groovy method [getPartyNameForDate] in Groovy file
[component://party/groovyScripts/party/PartyServices.groovy]: (The field name (or key) [gender] is not valid for entity [PartyN
Hi Pawan,
It seems related to this error:
Caused by: org.apache.ofbiz.service.GenericServiceException: Error running Groovy method [getPartyNameForDate] in Groovy file
[component://party/groovyScripts/party/PartyServices.groovy]: (The field name (or key) [gender] is not valid for entity [PartyN
Hello Devs,
Just saw some unusual errors on demo-trunk.ofbiz.apache.org for ordermgr
component. Most of the Order screens are broken.
At first glance, it seems some deployment issues because most of the
screens are broken. At my local, after the latest update these screens seem
to be working fine
