lundi 12 janvier 2015

Custom List inheriting wrong content type



I have created a sandbox solution with 2 custom lists, each with their own custom content type. When I deploy & activate the solution on my local environment and then activate the schema feature, both lists have been created, but they're both inheriting the same Content type. It seems that which ever content type is added 1st to the feature is the one that gets used.


When I try the same solution and process on a fellow employee's machine & local environment, they do not have the same problem? So is it something to do with my visual studio? Is this a common bug?








0 commentaires:

Enregistrer un commentaire