Tweet
I export an app from DEV to PROD. The app has a button. On click, it’s supposed to launch another app. After installing it to PROD, said button does not work. Does not do anything.
I had the exact same thing happen with 2 different apps actually. Both apps were supposed to launch the same app on Click button PRINT.
I get into the app with NAB in PROD and I see this:
click action bug.png
I update the app that’s supposed to be launched on Click to the correct app; yes, it exists does exist in PROD and yes, it does have the same name in PROD and DEV and QA. Now it works!
The app to be launched on-click has a different App ID in PROD than in DEV and QA and I suspect that under the covers, NAB is storing the App ID of the app to be launched on Click rather than the name, but that’s a total guess on my part:
Instance App ID Act Category ID SortSeq App Name
DEV 1130 1 2 11 Report Routing Settings
QA 1051 1 2 11 Report Routing Settings
PROD 1043 1 2 11 Report Routing Settings
If that theory is correct then I should be seeing the same issue in QA after promoting an app like that from DEV and I don’t recall seeing it there. We push from DEV to QA by doing instance moves. Can’t do that with PROD because PROD is on a different box, so that’s done via an export file and NAB import in PROD. I don’t know if these 2 methods vary under the covers. I’ll try do some more testing to see if I can prove out my theory but in the meantime can you guys take a look at this?
I had the exact same thing happen with 2 different apps actually. Both apps were supposed to launch the same app on Click button PRINT.
I get into the app with NAB in PROD and I see this:
click action bug.png
I update the app that’s supposed to be launched on Click to the correct app; yes, it exists does exist in PROD and yes, it does have the same name in PROD and DEV and QA. Now it works!
The app to be launched on-click has a different App ID in PROD than in DEV and QA and I suspect that under the covers, NAB is storing the App ID of the app to be launched on Click rather than the name, but that’s a total guess on my part:
Instance App ID Act Category ID SortSeq App Name
DEV 1130 1 2 11 Report Routing Settings
QA 1051 1 2 11 Report Routing Settings
PROD 1043 1 2 11 Report Routing Settings
If that theory is correct then I should be seeing the same issue in QA after promoting an app like that from DEV and I don’t recall seeing it there. We push from DEV to QA by doing instance moves. Can’t do that with PROD because PROD is on a different box, so that’s done via an export file and NAB import in PROD. I don’t know if these 2 methods vary under the covers. I’ll try do some more testing to see if I can prove out my theory but in the meantime can you guys take a look at this?
Comment