Possible Bug using Managed Apps - Form urls in Interface buttons do not function as expected

[mumpspro]

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?

[KevinMorris]

t sounds like you've run into an issue with URL persistence between the managed and distributed versions of your app. Here are a few steps to try that might help solve the problem while keeping the app as managed:

Dynamic URL Generation: Instead of hardcoding the form URL in the button action, consider implementing a dynamic URL generator within your app’s script or formula fields. This way, the URL can adapt based on the current base context, ensuring the correct form instance is referenced.

Base Context Check: Some managed app environments allow context-sensitive operations. If you can, configure the app to detect its base context dynamically and adjust any button action URLs accordingly.

Use of App Environment Variables: Check if Builder Hub allows storing target base-specific URLs in environment variables. You could leverage environment variables to switch the form URL depending on whether it’s in the Builder Hub or a distributed environment.

Feedback from Support/Community: Since you’re aiming to keep this app managed, it might also be worth reaching out to the Builder Hub support team. They could confirm if there’s an upcoming feature or a known workaround for this exact scenario.

Hopefully, one of these approaches can help resolve the interface button action issue without needing to switch to unmanaged.

[mumpspro]

Thanks for your response, Kevin.  I agree with your thoughts on this - the app is build purely using out of the box Airtable features/functions with no additional scripting, etc.  I agree that this must be a limitation within the Builder Hub and/or distribution mechanisms there-in.