Customisation publishing

Hi ​@Jupiter ,

Yes, you can update or republish a single customization without unpublishing the others, but every publish must include all the projects you want to stay live.

Each time you publish, the system unpublishes any previously published projects that weren't selected. So the steps are:

1. Update the project (edit it in the Customization Project Editor, or use Replace Highlighted Project Content to import a new package).
2. In Customization Projects (SM204505), tick Included for the updated project and every other project that should remain live.
3. Click Publish.

If you tick only the changed project, the rest will be unpublished. Publishing recompiles the site and applies to all tenants, so do it off-hours, and export your current projects first as a backup.

​@Jupiter Acumatica/MYOB Advanced, the safest approach is usually to publish the required set of active customization packages together, because the system validates the combined customization layer. You do not normally need to unpublish everything unless there is a conflict, dependency issue, or you are intentionally changing the active package set.

• Add an article to your custom wiki describing the new fields and how users should use them on that screen.
• Add or confirm that wiki under Customization Project Editor → Wikis. After later article edits, use Reload from Database before exporting the updated project. beacon.acumatica.com
• Link users to that article from the customized screen or its help content, and test the link after publishing in a target tenant. Acumatica documents an article ID convention for linking a form reference article to a form, but test how it behaves for your standard screen before relying on it to replace the existing Help (?) destination.

To Link an Article to a Form • System Administration Guide • Acumatica Beacon

​@mohammadnawaz51 - I suspect your last post was meant for this question?