自定义SO.SOOrder DAC字段后REST API报错：对象当前状态无效

Since you only updated the DisplayName property of the External Reference field on SO.SOOrder and immediately hit this REST API error, let’s walk through the most likely fixes—this is almost always tied to metadata caching or deployment gaps in Acumatica.

Step 1: Verify Your Customization is Published & Active #

First, double-check that your custom DAC extension was properly deployed:

• Go to Customization > Customization Projects in your Acumatica instance.
• Locate your project, ensure it’s marked as Published, and confirm in the Instance Details tab that it’s set to Active.
• If it wasn’t published, click Publish and wait for the process to complete—half the time, this is the root cause.

Step 2: Clear Acumatica’s Server Caches #

Acumatica aggressively caches DAC metadata, and your DisplayName change might be stuck in old cached data:

1. Navigate to System > Management > Cache Management.
2. Click Clear All Caches and wait for the operation to finish.
3. If you’re running Acumatica on IIS, restart the application pool for your instance to ensure all cached data is flushed.

Step 3: Refresh & Validate REST API Metadata #

Next, confirm the API is picking up your new DisplayName:

• Call the metadata endpoint for the SOOrder entity, e.g.:

  /entity/Default/[YourAcumaticaVersion]/SOOrder?$metadata
  

  Replace [YourAcumaticaVersion] with your instance’s version (like 20.200.001).
• Look for the External Reference field in the metadata—if it still shows the old DisplayName, regenerate your API endpoint:
  1. Go to Integration > Integration > Endpoints.
  2. Find your Default endpoint (or the one you’re using), click Regenerate, then save the endpoint.

Step 4: Double-Check Your Field Attribute Syntax #

While your code looks correct at a glance, it’s worth verifying there are no subtle syntax errors:

[PXDBString(40, IsUnicode = true)] 
[PXUIField(DisplayName = "Some Text Here...")]

• Ensure DisplayName is spelled correctly, all quotes are closed, and there are no missing commas between attributes. Even a tiny typo can throw off metadata generation.

Step 5: Dig Into Acumatica Logs for Detailed Errors #

If the above steps don’t fix it, check the server logs to get more context:

• Logs are usually located in [YourAcumaticaInstance]/Website/App_Data/Logs.
• Open the most recent log file and search for the error message: "Operation is not valid due to the current state of the object".
• The associated stack trace will point to exactly where the error is occurring—this can help identify if there’s a conflict with other customizations or a deeper metadata issue.

Step 6: Rule Out Customization Conflicts #

Even if you only changed the DisplayName, other active customizations might be modifying the same SOOrder field. Try temporarily disabling all other custom projects, then test the REST API again. If it works, you’ll know there’s a conflict to resolve between your customization and another one.

内容的提问来源于stack exchange，提问作者Aaron St Clair