Import issue

[KN_9954684]

When importing Thing(Database or Mailserver) entity, configuration details are also getting imported.Tried different import options(disabling overwrite property values etc..) but existing configuration is getting replaced .Please let me know if it is possible to not disturb existing configuration.

[abjain]

@KN_9954684 : When we import any entity, everything related to it get imported and it will replace the previous entity with the imported one.Don't think that you can keep the original configs as is on import. Better would be to add the previous entity configurations to the new one.  

[KN_9954684]

Everytime I export from my local,the configuration values are getting imported to client machine when they import.It is not practical for them to update values always and it is not safe as it is carrying my local configuration.Is there any other workaround for this problem as It is a serious problem.

[abjain]

@KN_9954684 You can duplicate the entity in your local and then import it so that it has different name in the client machine when its imported there.

Then compare the configuration and make changes in the thing. 

Unfortunately there is no way to selectively import some part of the thing without making changes to original one while importing. 

[KN_9954684 · Accepted solution]

Thank you for the clarification!!

[VladimirRosu]

The Configuration Tables will not be overridden if your entities are imported as part of an Extension.

If so, the system will keep the previous values.

However, if you import them singularly, as files, the values will be overridden - the behavior in this case is different. I'm working to clarify this in the Help Center, since this behavior is not known widely.

[DanWolf]

I know this is a couple years old but I just found it referenced in a PTC article.  I use Thing Templates to update database services (queries, etc.).  I have a Dev, QA, and Prod environment.  Each one has a connector for each external database I use and that connector Thing never gets overwritten.  The Thing Template for the database contains all of the properties and services and that gets deployed from Dev to QA to Prod, so I never need to update the actual DB connector Thing.