Announcement

Collapse
No announcement yet.

New Espo and old data -> Contacts view is blank - reset/plain layout seems to fix

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • New Espo and old data -> Contacts view is blank - reset/plain layout seems to fix

    I was able to create a new Espo version, the latest, and copy over the Custom folder and poof all of our fields were there and all was well.
    Then I proceeded to restore the database, which loaded fine for a while then threw errors.

    It's a training version, so I settled for just importing CSV and that seems to work ok except.... when I rebuild the layout for Contacts, current or new records cannot be re-opened once created/saved. Clicking on the record does nothing, and right-clicking opens to a blank screen.
    • ? is there information in the database we don't have and need causing this issue?
    The customer has added a lot of fields in the past 4 years, so I am wondering if there is a practical limit to the # of fields on a record. They are marching toward 100 and YES I advised them to break it up in to modules, standard normalization. Trying to convert them to the nice tabbed option

    When I RESET everything, layout, entity, everything works FINE, just 10 or so default fields in the layout and 1 or 2 of my custom fields. No issues opening.
    • ? Anyone have experience with or know of a practical limit for the DETAIL layout?

  • #2
    Hi crmclients,

    And why not transfer /custom/Espo/Custom folder from the old problematic instance to a new version of the same version, then import .sql dump. And only then upgrade to the current version?
    This is a proven way that will not cause unexpected errors and subsequent strange behavior in the new instance (as it happened to you).

    Otherwise, you will spend much more time solving strange behavior of the new instance by studying its error logs. In another thread, I already gave you detailed instructions on how I personally and many in the community migrated from a problematic instance to a new one: https://forum.espocrm.com/forum/deve...444#post111444.

    In addition, if you fail to make such a migration, there is always an opportunity to do it using the Export-Import extension: https://github.com/espocrm/ext-expor...ases/tag/2.4.0. You mentioned version 7.5.6 which is perfectly compatible with the current version of Export-Import extension 2.4.0.

    Comment

    Working...
    X