Import just the contact entity via solution

(0) Share

Report

Posted on by Seamus

1,577

I have a contact entity which I would like to import to a new crm instance. It is heavily customised and has too many dependencies (7 pages worth) to go through individually single-clicking to include in the solution. However, the import fails without these dependencies. Does anyone know of a way I can import/export just the single entity and its form and fields without having to wade through all these dependencies - including them is so labour-intensive that I may as well recreate the contact entity manually on the target system. Many thanks.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (2)

Verified answer

Bhuvaneswary Rajase... 405 on at

Like (0)

Report

Hi Seamus,

if the dependent entities are custom entities, u have to add those. No way u can skip that.

Thanks

Was this reply helpful? Yes No
Suggested answer

ScottDurow 21 on at

Like (0)

Report

The only way you can do this is to export the solution, unzip and copy the attributes and relationships - then do the same on your target and paste in the attributes and relationships,then rezip and reimport.

Be careful and always keep a database backup!

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

The dependencies are there for a reason - the system is "depending" on them in order to work.

For example, if you have a sub-grid on the Contact form of some custom entity, or fields in a Contact view from a parent custom entity then that entity must exist in the target system in order for that form or view to work.

If you have scripts referenced in your Contact form, then you need to include those web resources for the scripts to be available.

The list of dependencies identified during solution export are written into the solution file, and are one of the first things checked during import. If those dependencies all exist already in the target system, then this passes and lets you install. If not, you cannot import the Solution because it would not function.

You can reasonably ignore dependencies that are for system components that you know you have not modified, since they must already be in the target system. Look in particular for custom entities and web resources. Once you spot one, cancel out of the export process, add that component and go again - especially for entities you might see several dependency rows for the same entity such as for a couple of views and several fields.

Was this reply helpful? Yes No
Seamus 1,577 on at

Like (0)

Report

Thanks everyone. I have no need for all the dependencies on the target side. It is a complete pain adding them to the solution so I am just going to have to manually recreate. Just double-checking - it doesn't matter whether it is a managed or unmanaged solution, - neither will do what I need in terms of being able to circumvent the dependencies??

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Correct - manage or unmanaged, dependencies are required components.

Was this reply helpful? Yes No