-
Notifications
You must be signed in to change notification settings - Fork 153
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
feat: add linking method to ecommece customer controller #305
base: develop
Are you sure you want to change the base?
Conversation
ping |
Kindly help move this PR forward. Many thanks from Yours Sincerely! |
Kindly help move this PR forward. Many thanks from Yours Sincerely! |
Kindly help move this PR forward. Many thanks from Yours Sincerely! |
Kindly help move this PR forward. Many thanks from Yours Sincerely! |
Kindly help move this PR forward. Many thanks from Yours Sincerely! |
Kindly help move this PR forward. Many thanks from Yours Sincerely! |
Kindly help move this PR forward. Many thanks from Yours Sincerely! |
Kindly help move this PR forward. Many thanks from Yours Sincerely! |
Kindly help move this PR forward. Many thanks from Yours Sincerely! |
Kindly help move this PR forward. Many thanks from Yours Sincerely! |
Context
The Primary address and contact of a customer are customarily used to aquire defaults across ERPNext.
They furtheromre serve as a fallback customer identification scheme, for example based on email or phone number of their primary contact.
However, the ecommerce controller did not properly set those fields upon creating a new customer
Proposed Solution
primary_*
fields are set for the Shopify Integration (since only the Shopify Integration uses the controller)