publishing customization from CPE fails, but works from SM204505

• CPE version vs. Acumatica build
  • Make sure the CPE you're using is the version intended for 26.100.0175.4.
  • An older/newer CPE can sometimes validate successfully but fail when the publish request compares the customization document hash.
• Try exporting the project and publishing the exported package
  • Export the customization project/package from the instance.
  • Create a fresh customization project/package from that export.
  • Then try publishing that through CPE.
  • This helps determine whether the problem is related to the project metadata/document itself rather than the CPE connection.
• Try a brand-new trivial customization
  • Create a new project containing something extremely simple, e.g. a small DAC extension or screen customization.
  • Publish it through CPE.
  • If even the trivial project fails, that strongly points toward a CPE/instance compatibility issue rather than your customization.
• Check whether CPE is modifying the package during validation
  
   

  The strongest diagnostic test

   

  Create a completely new, empty/simple customization project → save it → publish it using CPE.

  If that also fails: almost certainly CPE/version/client-side issue.
  If that succeeds: the issue is specific to the existing customization project's document/package.
  If an exported/reimported copy succeeds: the original project's customization document is likely carrying some metadata/state that CPE doesn't like.

   

Try to search for Zero Width No-Break Space characters in your ASPX and ASPX.cs files and remove them.

​@FarhanaM60  - if you’re using AI to generate your answers, please indicate that in your post.

Hi ​@FarhanaM60,

I would recommend first checking the exact Acumatica version/build on which the customization project was created. Make sure it matches the version/build of the instance where you are currently trying to publish the customization. Remove any spaces or special characters (if any) from your customization project name.

If the versions are the same, I would suggest creating a new customization project, importing everything from the existing project into the new project, and then trying to publish it from the Customization Project Editor (CPE).

Since I’m not sure what your customization contains, it’s difficult to suggest a specific solution. However, the above scenario should help determine whether the issue is related to the existing customization project itself.

I would also recommend putting the site into Maintenance Mode and then trying to publish the customization once from CPE. This will help rule out any interference from other users or processes modifying the customization project during the validation/publishing process.

Hope this helps!

Thanks for the suggestion.  i searched all ASPX and .cs files in the project, and sadly, this was not the issue - none of them had embedded Zero width no-break space characters.

thanks for your suggestions.

i’ve been working with the customization project in this version/build of acumatica for some time, and something has caused it to go wonky.  i tried maintenance mode, even though i had already tried publishing from my dev box after a reboot, with no IDE open, no automation schedules or biz events active, etc.  i have the same issue when attempting to publish on 2 other servers - publishing from CPE fails, while publishing from SM204505 works. 

i suspect there might be something in the project causing the long running validation processes to hang in the CPE, whereas the delay when acumatica prompts to publish is long enough for it to finish.

i was hoping to avoid creating a new project - it contains both screen and workflow changes to 15+ acumatica screens, adds 10 new pages, database scripts for multiple custom tables and additions to Acumatica tables, a DLL, site map entries, GIs, etc.   folding all of the changes into a new project will be a bit tedious.

if i find the culprit while building the new project, i will report back here to hopefully save someone else the same headache/time suck.   as i am often heard saying, if it were simple, first graders could do our jobs.

I would suggest creating a small, separate customization package with only a few simple screen customizations and minimal or no business logic. If any logic is required, keep it to very basic business logic.

Try publishing this package through CPE. If it publishes successfully, we can narrow down the issue and suspect that something within the business logic or a specific customization in the larger project is causing the publishing problem.

You can then gradually add the customizations from the original project to the new package and identify which component is causing the issue.

Hi ​@jim71,

I can understand that creating new project with many screens and other objects becomes tedious. However, you can try saving the project and open the project in following manner by creating new project. This way you do not have to add all object manually. Check if that resolves the issue.

1. First, you can save the project to your local drive, from your existing customization project

2. Second, create a new customization project (Make sure you unpublish the current project and remove it completely).

3. Third, open the project, from your new customization project