You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two separate environments - APEX and DB. One was created as a clone of the other one. Recently, I started using SQLcl to export and import page changes from Dev to Prod. I used it for one deployment, but now it fails for the second deployment.
If I try to export a page and then import it, I see the page got updated in the Admin's list of pages, but if I try to access it, the page loader hangs indefinitely. If I try to access the page from a client session, then a message is logged:
"Page template ... does not exist. Check your theme configuration!"
The page template identifier is MINIMAL_NO_NAVIGATION, part of '42. Universal Theme'.
The text was updated successfully, but these errors were encountered:
After further testing, it seems the SQLcl export puts some strange/random IDs for page/button templates. If I export the same page from the APEX Admin UI, the IDs are different (and can be crosschecked with, e.g., TEMPLATE_ID-s from the APEX_APPLICATION_TEMPLATES view).
If I import the page exported via UI, everything will be fine. If I import the one exported via SQLcl, it fails to render correctly due to the invalid template.
I have two separate environments - APEX and DB. One was created as a clone of the other one. Recently, I started using SQLcl to export and import page changes from Dev to Prod. I used it for one deployment, but now it fails for the second deployment.
If I try to export a page and then import it, I see the page got updated in the Admin's list of pages, but if I try to access it, the page loader hangs indefinitely. If I try to access the page from a client session, then a message is logged:
"Page template ... does not exist. Check your theme configuration!"
The page template identifier is MINIMAL_NO_NAVIGATION, part of '42. Universal Theme'.
The text was updated successfully, but these errors were encountered: