Studio issue with Opportunities module

💬 General Discussion
1

Hello everyone,

We are experiencing an unusual issue while adding new custom fields to the Opportunities module Edit View using Studio.

When we make changes under Studio > Opportunities > Layouts > Edit View, the layout sometimes merges two tabs into one. In other cases, after saving changes to the Edit View, some fields are removed from the layout and moved back under the Toolbox.

Has anyone experienced this issue before? If so, could you please advise on the possible cause and how to fix it?

Thank you in advance for your help.

2

I can’t replicate it.

I had some glitches with the studio before though - but it was very rare and usually some temporary / caching / similar issue.

You’re on Suite 7, right? (Suite 8 doesn’t need the edit view anymore due to the new UI).

Can you check your editviewdefs.php ?
Maybe even move it away and re-build the layout for testing?

1 Like
3

Yes, it is Suite v7. I have checked the edit, detail, list and search view defs and we have the below in the end of each file in custom folder. Is it normal to have it?

;
?>

Also, do we usually have file called editviewdefs.php.suback.php in the same folder?

Suggested solution:

In php.ini file.

max_input_vars = 10000

Then restart php and web server services.

4

There are some SuiteCRM files the PHP closing tag, but mostly templates:

And: https://softwareengineering.stackexchange.com/questions/89553/closing-tag-on-php-files

su = initials of an admin and back = backup maybe?
It’s not default / standard in the repo.

Is this related?
How many fields do you have in your opportunities module.
Maybe, if it’s over 1000 fields and they are all passed via POST during the save action, potentially, you could run into this issue.
But 1000 fields might result into other issues on the DB level at first maybe (aside from a nightmare data architecture :wink: )

Do you have a local environment / virtual machine with a Suite installation of the same version of yours?
That’s what I sometimes compare for details like this, especially with a heavily customized instance.

1 Like
5

It sounds like Studio may be saving a corrupted or conflicting layout definition rather than just moving the fields visually.

I’d try a Quick Repair and Rebuild first, then clear the application cache and browser cache. It may also be worth checking whether any custom code, package, or logic hook is modifying the Opportunities vardefs or Edit View metadata.

Does the problem happen with every new field, or only when you edit a specific tab or panel?

1 Like
6

It’s strange that this only happens when I edit a specific tab or panel, and only with certain fields.

For example, when I add back WYSIWYG fields in the particular panel, it removed same 4 fields and move them to toolbox area.