I have an extension app in my LC that contains some FVC event triggers. In the data tenant, I have cusomizations over the HD, Header and Detail apps to be able to generate and launch them.
When another user creates a customization over the same apps in base (data tenant), does it have an effect on the items in the LC? I am seeing that the event triggers no longer fires when this happens.
Might need some additional context, but the short answer should be no. If your extension exists in a lifecycle, the app is customized in your lifecycle, and you are testing in that lifecycle, a base customization of the app should not affect your experience. In short, if every object is in your lifecycle, no base metadata changes should affect your testing.
If, however, the HD app is not customized in your lifecycle, your testing will read the base version of that app, which is the other customized version, in this case.
Here’s how customizations flow when you have lifecycles, development tenants and child _test tenants. Consider the following places a customization can exist and where you might be working on and testing metadata:
| ID | Tenant | Lifecycle |
|---|---|---|
| 1 | xxx | base |
| 2 | xxx | nonbase |
| 3 | xxx_test | base |
| 4 | xxx_test | nonbase |
Rules
a. If you are in 1, the only customization that will operate will be one that is also in 1.
b. If you are in 2, the order in which customizations will operate is 2 then 1.
c. If you are in 3, the order in which customizations will operate is 3 then 1. 2 will never operate.
d. If you are in 4, the order in which customizations will operate is 4 then 3 then 2 then 1.
What I have seen catch people out frequently is situation d. where intuition might suggest that the sequence is 4 then 2 then 3 then 1. However that is not the case. A customization in xxx_test base lifecycle trumps a customization in xxx nonbase lifecycle.
Nextworld’s recommendation for solution developers is not to customize in 1 or 2. But that does create some additional overhead usually in 4 when testing work that is under development, and frequently gets forgotten from what I’ve seen.
Not sure if this helps explain the situation you’re in.