In the applications we create with SF, there are tables that are used in multiple applications. We call these “basic data” tables. For example, the tables for countries, states and cities are the same for all our applications.
We would like to share these tables without the need to copy them from 1 project to another. This becomes cumbersome when there is a change in the table, we need to manually update all projects that incorporate this table.
We did a research project, where we created a base project. This base project contained the tables that we wanted to share. We then imported this base project in a “normal” work project. This resulted in the tables to become available in the SF. Allowing the creation of relations between the tables in the base project and the tables in the work project. Updating the base project resulted in a warning that are is an update of this base project, and that it needs to be updated again.
However, when we generate a version of the work project, all imported base projects are reimported. E.g. tables are removed and inserted. As a result, all references between the tables are removed and need to be manual recreated again. As you can imaging, this is an error prone process.
TL/DR:
Provide a method for sharing table configurations between multiple projects from a single source. When the source is updated, there should be a convenient way to update the depended projects with the new configuration. Where the references in the work project are maintained during the update process.
- 678 replies
Hi Edwin,
There's a project planned to no longer throw away all generated objects when generating a project version, but to merge the changes instead. This would allow you to put any shared tables in base projects again. Would this solve your problem?
There's a project planned to no longer throw away all generated objects when generating a project version, but to merge the changes instead. This would allow you to put any shared tables in base projects again. Would this solve your problem?
- Sidekick
- 12 replies
Hi Jasper,
yes this probably would solve the issue. As the created foreign keys from the "base/generated" tables to "project" tables are no longer removed. Any idea when this feature is planned?
yes this probably would solve the issue. As the created foreign keys from the "base/generated" tables to "project" tables are no longer removed. Any idea when this feature is planned?
+9Updated idea statusPlanned→Working on it!
+9Updated idea statusWorking on it!→Next release
+9Updated idea statusNext release→Completed
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.