OroCRM Forums

Covering OroCRM topics, including community updates and company announcements.

Forums Forums OroCRM Error with new entity field created in db but not appeared in config mapping

This topic contains 2 replies, has 2 voices, and was last updated by  irina.k.melnikova 3 years, 11 months ago.

Starting from March 1, 2020 the forum has been switched to the read-only mode. Please head to StackOverflow for support.

  • Creator
  • #40784



    I have faced the issue related to a new Opportunity field generation. It was added through migration which was totally correct (checked on a testing installation beforehand). But during the migration run it failed by timeout (the message queue was overloaded so the timeout has exceeded). On the second try of running the migration, it ended with no errors, however, while checking the results I noticed that the db property was created in an appropriate way while there was no such a column in an extended entity nor in entity config (on UI, ‘Entity Management’ functionality). Also, obviously there are no getters/setters for this columns generated.

    Could you please advise how I can make such a field appear in entity mapping while it already exists in DB and no further migrations cannot solve this issue?

    The system version is 2.5.0.

    Thank you!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Author
  • #40786

    Andrey Yatsenko

    Hi Irina,
    The recommended way to solve it – restore the database from the dump taken before the migration, check that the PHP in the command line has enough memory assigned, more is obviously better, and remove the time limit for all the command completely. Then rerun the migration by following this guide https://doc.oroinc.com/backend/setup/upgrade-to-new-version/



    Hi Andrey,

    I tried to run a similar migration after solving memory issues, it indeed succeeded. However, despite second migration was successful, the new field strangely was not created in entity config as well. Though I was able to have it generated though running ‘oro:entity-extend:update-config’ and ‘oro:entity-extend:update-schema’ commands, it unfortunately didn’t affect the firstly added field.

    So the only solution is indeed restoring the database from a backup.

    Thanks for your help!

Viewing 2 replies - 1 through 2 (of 2 total)

The forum ‘OroCRM’ is closed to new topics and replies.

Back to top