relationships and custom CE packages

[ldebaets]

Is there a known problem with relationships between custom modules when generating and loading packages for them? It looks like relationships can be lost and relationship tables can be lost for modules which also are related to standard Sugar modules.
I was using the SugarCRM CE version 6.1.0 to generate the package and it was loaded into a SugarCRM CE version 6.1.2 and 6.1.3 application load when I saw the problem.

I would like to know if anyone else has experienced the same problem and what the solution may be. This is very crucial for me.

[ldebaets]

Is there a known problem with relationships between custom modules when generating and loading packages for them? It looks like relationships can be lost and relationship tables can be lost for modules which also are related to standard Sugar modules.
I was using the SugarCRM CE version 6.1.0 to generate the package and it was loaded into a SugarCRM CE version 6.1.2 and 6.1.3 application load when I saw the problem.

I would like to know if anyone else has experienced the same problem and what the solution may be. This is very crucial for me.

Documentation indicates we should be able to relate custom modules to sugar modules and have them survive a package export or publish operation and install correctly in a new installed instance of the Community Edition of SugarCRM. Since it is failing for me, and I have successfully deployed and tested the package prior to publishing the package, I suspect it is a defect and I should open a bug.
It`s high priority for myself as there are many people dependent on a solution very soon. Someone please help.

[eggsurplus]

It's definitely a known issue and you may be able to find a bug for it. Best practice is that once you publish a package to do all your additional changes in Studio instead. Stinks though since any additional fields will be in the _cstm table instead.

[ldebaets]

It's definitely a known issue and you may be able to find a bug for it. Best practice is that once you publish a package to do all your additional changes in Studio instead. Stinks though since any additional fields will be in the _cstm table instead.

Thank you very much. Another question if you don`t mind:
For a a fresh installation with an upload of the package, does your reply mean I should use Studio to fix or reset the relationships. I would think that would work but for upgrades with live data that has to survive, I think I could use a tool like phpMyAdmin to import the data for the lost table after it gets recreated using Studio. Would you agree with that procedure.

Same question as above but with Modulebuilder for an exported package.

Thanks again for your help. In a way it`s good to know it`s a known bug, but I think we definitely would like to be able to do seamless upgrades and installations of custom pacakges. I may open a new bug and try the scenarios above to see if they are good workarounds.

[eggsurplus]

Personally I've had to repair relationships directly in the database. If you're comfortable with that I don't see an issue. I forget how the deployment works. Does a file get created in custom/metadata for your relationship as well?

[ldebaets]

Personally I've had to repair relationships directly in the database. If you're comfortable with that I don't see an issue. I forget how the deployment works. Does a file get created in custom/metadata for your relationship as well?

Yes, for the case of an Exported package loaded into a new sugar instance, there is a file in the custom/metadata directory for it! The relationships are seen in ModuleBuilder and Studio too.

Thanks eggsurplus. I am trying the various workarounds to see which one I would prefer to use.

[tickletoe]

I have a slightly different problem and don't know whether it is because of this bug or because of the way I have designed my packages. I have two custom packages which contain various custom modules. I divided the modules between the two packages because it seemed logical at the time.

I have package A, with module 1,2,3,4 and package B with module 5,6,7

When I relate module 1 and 5 in module builder and deploy the relationship can be lost.

My question is, do people think this is because of this bug or because I have the modules in two different packages? Would it happen if they were in the same package and if not is there an easy way to merge packages?

Many thanks for any input on this.

Cheers
scott

SugarCRM CE 6.1.1