EspoCRM v7.2.0 released

[espcrm]

Sure did, manage to create a few menu... but then I ran out idea after making 2. I'm just not creative enough. But it much more cleaner now, does take a while to get use to. I'm still scrolling down or "hey where my Panel"

[murugappan]

espcrm, Its ok. the names are fictitious. Anyway, i have removed the screencap. Does my post help?

[espcrm]

Thank you! With your 4th screenshot, not sure if those are private information, you may want to delete if it is.

[murugappan]

espcrm

Its been a long time. May be I can help here.

(1) Select an entity->layout->Bottom Panels and you should see something like in first screencap below.
(2) Under this layout, in the middle box, you can drag and drop a tab-break which will give the second screencap
(3) Enter the tab name that you would like. Remember to drop the tab-break above the enabled item
(4) Define as many as you need and then save and you should get all the tabs defined a in the third screencap
(5) Go to entity record detail view and you should be able to see like fourth screencap (sorry removed) at the bottom of the details

I hope that helps.

[espcrm]

How to enable Bottom Panel tabs? I thought it be the same way as you do with Entity Panel but it not. Is it the "Sticky" option?

[murugappan]

TripitakaBC , very interesting problem. I believe that using the system "as is" and "as intended" without my guys meddling with the core/vanilla code and also maintaining usage consistency would be the way to go. We faced similar problems before but we have now corrected the situation by setting up compliance standards so that it will make life easier for our integration teams as well.

[murugappan]

yuri , i understand. The reason for the length of time is that i am upgrading from version 7.1.4. That means it needs upgrade until 7.1.11 before 7.2.4. Thank you so much.

[TripitakaBC]

Yes, a poor choice of words from me. By 'should be' what I intended was 'used to be prior to upgrade'.

I am sure I will not be the only user in this situation and my intention in posting is to help others diagnose the inevitable errors. It helps me to understand that the error existed previously but the new validation in 7.2.x exposes it rather than creates it. That is a good thing, but we still need to understand how to fix it on our installations. Hopefully, this helps.

[yuri]

It was always case-sensitive, nothing changed. In your case you had not proper values storing in database (what breaks many things, dynamic logic, workflow, reports, etc.). Thanks to the new validation it exposed the problem. I'd recommend running an UPDATE query to fix existing values.

> Sending a value of 'Male' when the option of 'male' is available should be accepted, but is not.

This is wrong. Think of enums with options (AM, am), (MM, mm). Please, no need to argue on this point. I know something how Espo should work.

[TripitakaBC]

yuri - the case sensitivity is not described in that section, maybe it could be added? Sending a value of 'Male' when the option of 'male' is available should be accepted, but is not. I read that section, reconciled that what was being sent was one of the available options and only revisited when I had run out of other ideas.

[yuri]

This issue is described in the first post (the last section).

[TripitakaBC]

https://forum.espocrm.com/forum/bug-reports/83592-error-400-field-validation-error#post83592

[yuri]

5 min is quite more than I expected. It took less than 1 min for instances I upgraded.

[murugappan]

yuri thank you for the update. We do not have any large import_entity table. We do not execute much imports as we have integrated Espocrm to our transaction processing systems. I have tested on the dev server and it took less than 5 minutes.

[yuri]

Only minor. I only can remember this one: https://github.com/espocrm/espocrm/c...76fbe5e6ff8878

Upgrade can take bit longer if you have a big import_entity table.