Expand Column

[yuri]

Correct. Stored in the browser. If you switch your device, changes won't be available. The same as it works with show/hide columns.

[rabii]

Yes. It is stored in the session so even if user logged out and logged in again the columns will be the same unless if it is reset

[shalmaxb]

yuri, great! I implemented it in some apps the way telecastg described, but it is always better, if this is a core function.
One question (did not test it so far): If a user resizes the column, will it stay resized even if the user logs out? Because in the telecastg way it would reset on leaving the list view to default.
Ok, I see, it is stored. Question answered.

[yuri]

Column resize: https://github.com/espocrm/espocrm/issues/3186

[telecastg]

New commercial extension released, compatible with Espo 7x. Now you can have column resizing and tabular editing without having to write any code.

If interested check this post please. https://forum.espocrm.com/forum/exte...without-coding

[diyoyo]

The only way to guarantee that it is upgrade safe is to follow what telecastg has described.

Either that or be careful as to how you merge in the updates - I'm merging changes from the EspoCRM GitHub repository rather than installing them via the Admin interface.

The main reason for doing this is that we've made significant changes to the underlying code-base to support many more business functions and therefore just applying an update via the Admin interface would cause a lot of issues.

I guess I saw this too late!
I updated and now the column expansion does not work anymore. and in addition, I think it is causing a bug where in form, I cannot display the popup selector for linked fields, it only relies on the auto-completion.

[esforim]

Wow this is a hidden gem; thanks for reviving it.

[Kertscher]

Hi,
I have followed the intruction.
But it dosent work.

Any advice would be welcome.

[blueprint]

The only way to guarantee that it is upgrade safe is to follow what telecastg has described.

Either that or be careful as to how you merge in the updates - I'm merging changes from the EspoCRM GitHub repository rather than installing them via the Admin interface.

The main reason for doing this is that we've made significant changes to the underlying code-base to support many more business functions and therefore just applying an update via the Admin interface would cause a lot of issues.

[diyoyo]

My Path was correct.
I had to log-out and log-in again and everything went fine, actually.
Do you think there is a way to make it upgrade-proof without the need to edit every single entity's clientDef?
Thanks.

[blueprint]

I just ensured that the path to the CSS file was correct and in the right folder. In my instance, it wasn't. Maybe double-check your paths.

[diyoyo]

blueprint What did you change to make it work again?

[blueprint]

I got the huge white area at first but I realised that the CSS file for the resizableColumns was not being loaded correctly (Google developer tools helped here).

Ensure that you have the custom CSS file specified as per my original comment.

[diyoyo]

Turned out that I was in developer mode , but following telecastg , I had changed the values of the client.json.

Now, the script is working, but both non-upgrade proof and semi-upgrade proof versions are now displaying this huge white screen before column's titles.

[diyoyo]

Indeed, the first answer was not upgrade proof as experienced with today's upgrade.
however, telecastg solution does not work in my hands : I have the following error when inspecting:

TypeError: $(...).resizableColumns is not a function

The page is displayed as if there was nothing changed from the original Espo (unlike the non-upgrade proof version, which now displays a huge white margin before the colum titles, and does not even allow columns to be resized).