I'm repeatedly getting error when updating the business assets.

Hey Dhanoordaran V,

it sounds like you’re running into a 500 error when updating certain classic business assets in Purview—even after tearing down and recreating the Business System V2 and re-linking everything. A few things can trigger this, most commonly broken or mismatched relationships and service‐side glitches. Here’s how you can dig in:

1. Check service health & retry • 500 errors can be transient—double-check the Azure Purview status page and retry after a few minutes. • If you have Azure Service Health alerts set up, see if there were any incidents around your request IDs.
2. Validate relationships • Since your business assets link to files and tables created via REST, make sure those assets still exist in the same Purview account and collection. • Pull the asset via REST or UI (GET /catalog/api/atlas/v2/entity/guid/{assetGuid}) and inspect the “relationshipAttributes.” Any stale or invalid GUID here can cause a 500. • If possible, strip out all relationships, update just the business metadata, then re-add relationships one by one to isolate which one is failing.
3. Use the REST API for a controlled update • In the REST API call to update, ensure you’re sending the full entity definition (both “attributes” and “relationshipAttributes”), not just the fields you want to change. Missing required bits can lead to an unexpected server error. • Example: PATCH https://{your-account}.catalog.purview.azure.com/catalog/api/atlas/v2/entity Body: {

   “entity”: {  
   
     “typeName”: “your_business_asset_type”,  
   
     “attributes”: { … your updated metadata … },  
   
     “relationshipAttributes”: { … existing relationships … }  
   
   }  
   

   }
4. Turn on diagnostic logs • In the Azure portal, navigate to your Purview account > Diagnostic settings > send the logs to a Log Analytics workspace. • After reproducing the error, review the “RequestFailed” entries around your Request ID—this can give you a clearer internal error message.
5. Permissions & roles • Confirm your user/service principal has the Data Curator or greater role on the collection that holds these assets. Insufficient permissions sometimes bubble up as 500s.
6. If it still fails • Gather the Request IDs, timestamps, asset GUIDs, and the exact payload you posted. • Open an Azure support ticket so the Purview team can look at the backend logs with your IDs.

Hope this helps you pinpoint what’s getting stuck! Let me know how it goes or if you spot a particular relationship that’s causing the issue.

Reference docs

1. Manage classic business assets in Purview (UI + REST) https://learn.microsoft.com/azure/purview/catalog-manage-classic-types
2. Purview REST API reference – update entities https://learn.microsoft.com/azure/purview/catalog-rest-api#update-business-asset
3. Azure Purview service status https://learn.microsoft.com/azure/purview/service-status