Skip to main content
13-Aquamarine
October 13, 2025
Question

delete old objects present in old extensions

  • October 13, 2025
  • 2 replies
  • 849 views

For the production environment, we create a deployment package and upload the extension to production. The objects that are part of the extension change, and some have been removed. However, I noticed that there are objects in production tied to old extensions that cannot be removed. I thought that excluding the object from the extension would remove it. How can I remove these old objects tied to extensions that are no longer present in the system?

2 replies

16-Pearl
October 16, 2025

Hi @dbologna,

 

Can you please explain how the objects are tied to old extensions with concrete example if possible?

What errors are you getting when removing the old objects?

Can you try importing the old extensions first, then remove the old objects, lastly delete the imported old extension?

If the old extension is not available anymore, can you try recreating the missing dependent entities (with the exact entity name) and remove again?

 

Best,

dbologna13-AquamarineAuthor
13-Aquamarine
October 16, 2025

Hi TonyZhans,

First of all, we're in a production environment and it's not possible to delete/import extensions.

I can create a new extension to which I add the old Things, but once I've imported the extension, these Things can't be removed because they're part of an extension.

Is there a way to remove a Thing that's part of an extension?

BR

Dimitri

16-Pearl
October 16, 2025

Hi @dbologna,

 

To remove Things that are part of an extension, you have to delete the extension itself.

Please refer to Help Center for how to delete an extension.

You can then import the new extension without unwanted old Things.

If the imported extension has some issues, you should have detected this in Test or QA environment before going to production. It's a good chance to review your deployment process.

If the Things in extension have already been used by many other entities in Production, you may want to consider leaving the old Things as it is and simply mark them as deprecated or use permission control to hide the old things from developers.

 

Best,

16-Pearl
October 29, 2025

Hi @dbologna,

 

It appears that a response to this post answers your question. For the benefit of other Community Members who may have the same question, it would be great if you could designate it as the Accepted Solution.

In the event that this response did not answer your question, please post your current status so that we can continue to support.

 

Thanks for using the PTC Community!

 

Regards,

dbologna13-AquamarineAuthor
13-Aquamarine
October 29, 2025

Hi All,

I ran the same test as MA8731174 on an offline production environment, and indeed, the object that was present in the old deployment package and no longer present in the new deployment package was deleted from the system.

In my case, this didn't happen in cloud production.

I'll try adding one of the old objects and deleting it in the next deployment to see how it behaves.

I'll let you know.

BR

Dimitri