Skip to content
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

Bundle Product price is required when dynamic price enabled after data migration from magento1 to magento2 #661

Closed
magentoguyssageone opened this issue Feb 25, 2019 · 7 comments
Labels

Comments

@magentoguyssageone
Copy link

Preconditions (*)

  1. Install Fresh Magento version 2.2.7
  2. Install Data Migration tool
  3. Complete Data Migration from Magento1(Magento versie 1.9.3.2) to Magento2

Steps to reproduce (*)

  1. After Complete Data migration go to Magento2 admin and Edit any migrated bundle product
  2. Bunle Product has Dynamic Price set to Yes : http://prntscr.com/mptl6t
  3. Try to Save Bundle Product but unable to save becuase Price is Required field for bundle product for my magento2 website. : http://prntscr.com/mptlxk

Expected result (*)

  1. Bundle Product price should not required as Dynamic Price is Yes
  2. Bundle Product should Save Successfully without required price error.

Actual result (*)

  1. Try to Save Bundle Product but unable to save becuase Price is Required field for bundle product for my magento2 website. : http://prntscr.com/mptlxk but it should not required and price filed should disabled.
@victor-v-rad
Copy link
Collaborator

Hi @magentoguyssageone

Internal ticket MAGETWO-98531 was created to fix this issue

@VDCProjects
Copy link

Hi,

any update about this issue?

Thanks

@MagentoGuysProjects
Copy link

Hi,

its very long time and no update.
can you please update about the status of this issue ?

Thanks

@victor-v-rad
Copy link
Collaborator

Hi,

The ticket is in queue for development, but the tool is open source and you can make a great contribution for all Magento community.

@MagentoGuysProjects
Copy link

Hi,

Any progress about this issue ?

@victor-v-rad
Copy link
Collaborator

Hi @MagentoGuysProjects @VDCProjects @magentoguyssageone
I did not able to reproduce the issue on the latest Magento 2.3.2 and the tool 2.3.2.
Probably it was fixed in #574 It looks very similar.

@ityetti
Copy link

ityetti commented Jan 6, 2020

@victor-v-rad I have a similar problem, and I'm looking for a solution to fix it without starting a full data migration again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants