Fix: New lookup fields automatically add entities to your solution (Whether you want them or not)

genericBeing able to pick individual components for a solution is great for deploying a new feature without fear of overwriting components that you didn’t modify (or for managing parallel dev tracks).



When you add a new lookup field, if the parent entity is not already in your solution, CRM will (generously) add that entity for you with all of its components.



To avoid this, add the parent entity first (metadata only), then create your new lookup field.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s