I have recently starting migrating one of my apps to the builder hub for centralized distribution, and ran into an issue with Interfaces that leverage a button action to open a form.
In the builder hub, the app functions perfectly fine - no issues at all. Once the app is distributed, the url of the form instance within the target base changes, but the url in the interface button does not - causing a button click to reference the builder hub version of the form and thus perform lookups, etc. from the builder hub base in lieu of the base in the target workspace.
It gets weirder though, as the managed app does know to store data in the correct base - its just lookups, filters, etc that do not function appropriately given anything inside the form leverages the base tied to the form itself.
I did verify that the FORM URL changes upon distribution and the interface button action FORM URL does not.
While it could be a simple configuration change in the target base (as a work-around), given the interface was distributed as part of the Managed app, the only way to update the interface button action seems to be to change the interface to unmanaged, which is what I have done as a short-term work-around, however, I would like to keep this as a self-contained managed app if possible.
Thoughts?
