-
Notifications
You must be signed in to change notification settings - Fork 588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Follow up : #4153 Serial Letter Feature #4216
Comments
* it looks like I lost the part where the reference was created #4216
IT
=> could not create user NOK
2018-07-25 15:00:31.844 ERROR 12232 --- [http-nio-8080-exec-10] o.a.a.m.AnnotatedModelInterceptor : Model interceptor method de.metas.marketing.base.interceptor.MKTG_ContactPerson#onChangeEmail threw an exception.
You can disable this method with SysConfig InterceptorEnabled_de.metas.marketing.base.interceptor.MKTG_ContactPerson#onChangeEmail='N' (with AD_Client_ID and AD_Org_ID=0!)
2018-07-25 15:00:31.863 WARN 12232 --- [http-nio-8080-exec-10] o.adempiere.ad.trx.api.impl.TrxManager : AbstractTrxManager.call0 - caught class org.adempiere.exceptions.AdempiereException with message=NullPointerException: userRecord
2018-07-25 15:00:31.863 WARN 12232 --- [http-nio-8080-exec-10] o.adempiere.ad.trx.api.impl.TrxManager : AbstractTrxManager.call0 - caught class org.adempiere.exceptions.AdempiereException with message=NullPointerException: userRecord
2018-07-25 15:00:31.866 WARN 12232 --- [http-nio-8080-exec-10] o.adempiere.ad.trx.api.impl.TrxManager : AbstractTrxManager.call0 - caught class org.adempiere.exceptions.AdempiereException with message=NullPointerException: userRecord
2018-07-25 15:00:31.866 WARN 12232 --- [http-nio-8080-exec-10] o.adempiere.ad.trx.api.impl.TrxManager : AbstractTrxManager.call0 - caught class org.adempiere.exceptions.AdempiereException with message=NullPointerException: userRecord
2018-07-25 15:00:31.869 WARN 12232 --- [http-nio-8080-exec-10] de.metas.ui.web.window.model.Document : Failed saving document, but IGNORED: Document{tableName=C_BPartner, id=2156426, windowNo=272, writable=true, valid=Valid, validOnCheckout=Invalid('child invalid'), saveStatus=DocumentSaveStatus{saved=false, deleted=false, hasChangesToBeSaved=true, error=false, reason=child invalid}, saveStatusOnCheckout=DocumentSaveStatus{saved=false, deleted=false, hasChangesToBeSaved=true, error=false, reason=child invalid}}
org.adempiere.exceptions.AdempiereException: NullPointerException: userRecord |
* On new is not a valid option because a user can't have contat persons if it doesn't exist. #4216
#4216 change the AD_User callout to only work on change.
[#4092](#4092) sync mail address between contactperson and linked user [#4153](#4216) Follow up : #4153 Serial Letter Feature [#4396](#4396) Pipes/Cabling vertical [#4403](#4403) Process to void order and revert flatrate terms, shipment schedule, invoice candidates [#4413](#4413) ShipmentScheduleHandler.retrieveModelsWithMissingCandidates() shall return an iterator [#4416](#4416) Split Product Nutrition/ Allergene in 2 Tabs [#4417](#4417) New Textfield for Product Ingredients without BOM [#1629](#1629) Invoice data goes missing in payment after save [#4405](#4405) Action Sales Order from Quotation wrong Prices [#4412](#4412) async-processors shall only run on app [#4415](#4415) JSON Fehler "Der Kurier" [#1889](metasfresh/metasfresh-webui-frontend-legacy#1889) Order line batch entry not working for current experimental cables/pipes batch entry
IT
|
As a rule: a contact person will be created without an address if the address is not required in the Marketing Platform. |
For my new process, I will make it impossible to create a contact person if there is no address as required, but for the older process, the contact person must be created if the platform has the RequiredLocation flag on false. |
IT
|
#4216 make sure if an empty location fits for the MKTG campaign contact person then none is taken
IT |
Is this a bug or feature request?
FR
What is the current behavior?
Which are the steps to reproduce?
What is the expected or desired behavior?
Follow up #4153 Serial Letter Feature
The text was updated successfully, but these errors were encountered: