Fields show in Studio but Not Module Builder

[Pfranco]

Hello,
Ive been using Module builder to build packages etc... I then started to use studio...

My issue I am having and I am wondering if anyone else is having same issue..

Lets say I create a module called Test , Issue

I set up relationships etc. One to One Related being Accounts

I deploy test module ..

I go to list view and say hey .. I want to be able to see the Account Names that each Test issue is realted to. So I go into Studio and go to List View ...

So I drag the test_accounts_name field over and place in its respective order. Go back to see if it worked and everything is Dandy .

Now .. Here is the thing. If I go into Module builder and try to do this so that this change becomes part of my package under List View there is no selction for test_accounts_name If I go back to Studio it is still there. I will say also that if I go into the Fields section under studio for Test that there is no field there named test_accounts_name ...

And I may add that this is not a field that I created. When I go into studio the field is already there in the list view options. But if I go into fields the field isnt there.

Even If I In Install and re install the package the change isnt there and i have to go back into studio and set it back up .

What I have come to realize si that any Changes I make in Studio do not cross over to Module Builder.. Is this correct?

If so can anyone tell me how to cross reference fields from one module to another using module builder? Or am I out of luck and need to edit source for the Module itself? If source edits are needed I am fine with that but I just need some insight as perhaps I am doing something incorrectly or if this is how things are supposed to be.

Any help is appreciated .

Thanks again ..

[chaos0815]

As I understand it, Studio saves the changes in seperate files apart from the deployed module. So even if you'ld make changes in ModuleBuilder and deploy the module, the changes made in Studio would still persist.

Anyone have a deeper explanation?

[Pfranco]

Yep... Through use etc.. I have realized Module builder is Just better for developing Core Modules and Packages while studio is a more end user customization package after deployment.

I came to realize all of this while building a Returns / RMA module that autogenerates RMA numbers for Return Merchandise Authorization.

I was making changes in Studio and noticed they werent showing in Moduile Builder.
Then after looking at the DB I caught on to the fact that Studio creates _c tables.

So in short I just realize that Module Builder is more for Development and Studio is more for Post-Deployment customization from the end user or super admins etc......

Dont know why, but I guess I just wish studio created the tables and fields the same way that module builder did so they were cross compatible, or at least importable to Module Builder.

Thank you for the reply I appreciate it .