Hello,
This is our situation:
We develop several application for one customer in one zone.
The applications have there own deployment schedule and we don't want to to deploy all at once.
The different applications share some common/shared objects
So we created a "Common" application with all common objects. Examples of these objects VAT, Relation, Address and so on.
Let say we have two other appliactions, called Project Initiation and Resource Demand.
Project initiation has a Lead object which is related to the Relation object.
Resource demand has a Supplier Quote object which is also related to the relation object.
One of the strength of Rollbase is that when you do this the view page of a relation automatically show you the Leads and Supplier quotes of the relation, our customer loves this.
The problem now is that the Common application is now dependend from the two other applications.
Generate xml will come up with an error that there is an dependency with the other appliactions. Removing the views of the leads and the supplier quotes from the relations viewpage solves this problem.
But our customer still want this page!!!!
So my question is:
How can i create a view on relations that shows the leads and suppliers quotes without having this dependency conflict
As of today this is not possible in Rollbase. The only way to do this is to for you to hand code the Page (not use Rollbase Generated Page) by using APIs. You should gracefully handle the case where the dependent objects are not present in the hand coded Page UI.
Hello,
You can just put all objects as core objects in your Common application.
You will then be able to generate the XML.
Romain.
Hi,
We also have a similar situation with our apps, and second what Romain said. You can put all objects as core in the common app.
One **very important** thing to keep in mind. You MUST generate a new version of all apps every time you modify some core object shared by all the apps, or you run the risk of accidentally deploying an old version of a component inadvertently.
For example,
1. Say you update the Leads view which is not part of the "Common" app, but present on the Relation page..
2. Then you publish an update to "Project Initiation" app only.
3. Now if you install the "Common" app to a customer/tenant that has the updated "Project Initiation" app, it will "downgrade" the version of Leads view embedded with "Common" app.
4. As a result, you inadvertently revert shared components to an older version.
To avoid this risk, publish an update to all apps every time you make any change to any of them.
Hope this helps,
~ Kurt