Creating or editing view.edit.php

[dante2010]

Hi,

I am using SugarCRM 5.2.0a (Build 5447).

I am trying to following this tutorial in order to allow a dropdown to hide/display panels based on what is selected. The tutorial tells me to create the following file:

custom/modules/Accounts/views/view.edit.php

My custom module is called propt_Property so I have created this file in:

custom/modules/propt_Property/views/view.edit.php

My issue is when I save and deploy my custom module, this file gets removed every time. What am I doing wrong? Is it meant to be placed in another directory?

UPDATE: Now when I deploy the package it has totally removed the propt_Property directory under /custom/modules ??? My module still appears to work as it did before tho. What is going on?

[andopes]

Hi dante

Check this thread.

[dante2010]

Thanks for that alternate version of how to hide/display panels based on a dropdown.

I am still unclear where to create these view.edit.php and such files that contain the new code. When I place them in the /custom/modules/<modulename>/views directory, they are always removed whenever I redeploy the custom module. Am I supposed to be doing a deploy after I make these kinds of changes to a module? Seems that I have to in order to see any changes made via module builder...

I have read that perhaps I am to be placing them in the extension folder instead? It's all not very clear that's for sure. And why has my custom module that I was working on totally disappeared from the /custom/modules directory now??

[dante2010]

So I've done a bit of playing around... it does seem that if I create files within /custom/modules/<modulename>/views , I am able to get things to change within the custom module. This seems to happen right away, and doesn't require me to perform a "deploy' as other changes made via the module builder seem to require.

I guess I just don't understand why performing a deploy then totally wipes all the files I had created in this /views directory...??

[andopes]

The re-deploy wipes the customization done because the module is re-installed at all.

Cheers

[dante2010]

OK, thanks for clearing that up.

I guess I still don't understand the reasoning behind a deploy wiping out all customizations one has made to a module. A deploy is needed to bring over any changes one has made within module builder, correct? So I guess the dev process within Sugar is to make sure you have made all changes needed in module builder, and then do your further custom work via code in the /custom dir? Cause once you're at that point you can't do a deploy w/o wiping what you've done in /custom ... ?

Just seems like a very strange process to me is all.