deploy form and others not showing in TEST after moving from DEV
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
I deleted the deployed TEST and then did a redeploy from DEV after having gotten 26 transaction errors.
The deploy worked but now some of the artifacts such as Forms are not in TEST.
In addition, the application does not show in the WorkSpade drop down.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago - last edited an hour ago
Hi @GabeF how are you?
Hi,
From the screenshot and your description, this looks less like a normal deployment issue and more like an application/package integrity problem after deleting the deployed application in TEST and redeploying it.
A few points I would check:
Do not rely only on the application file count
The fact that DEV has Forms and TEST does not usually means the deployment did not bring all related sys_metadata records, or some records were skipped because of conflicts/errors.
Review the deployment logs / install logs
Since you mentioned 26 transaction errors, I would start there. Even if the redeploy completed, some artifacts may have failed during insert/update. Check:
- Application installation logs
- Deployment history
- Skipped records
- Collision/conflict records
- Cross-scope privilege errors
Check whether the Forms are captured as application files
In DEV, open the missing Form records and confirm:
- They belong to the correct application scope
- They are included as application files
- They are not marked as customer updates only outside the app package
- They are not related to another dependency/app
Workspace dropdown issue
If the application does not appear in the Workspace dropdown, check whether the related workspace records were deployed correctly, such as:
- UX App Configuration
- Workspace experience records
- Application menu/module records
- Roles required to access the workspace
- User criteria or audience configuration, if applicable
Avoid deleting the deployed app in TEST as a normal fix
Deleting the app from TEST can leave orphaned records, deleted application files, or dependency inconsistencies. A better approach is usually to fix the deployment errors, publish a clean version from DEV, and install/update that version in TEST.
My recommendation would be:
- Go back to the 26 transaction errors and resolve them first.
- Confirm the missing Forms are actually part of the application package in DEV.
- Create a new clean application version from DEV.
- Install/update it again in TEST.
- If TEST is now inconsistent because of the deletion, you may need to clean up orphaned records or clone/refresh TEST before redeploying.
If this answer helps, please mark it as helpful.
Regards,
Dan
