Cannot select Publisher when creating custom solution RRS feed

  • Question

  • We have a managed solution that has been installed at a customer site (which also added our Publisher as well, with a custom prefix of "tss"). For this customer, we are also creating a custom solution for additional custom work. When creating the new custom solution, we would like to select the Publisher we created and imported as part of the original managed solution. however, our Publisher is not available from the list.

    We have a workaround, i.e. create a new publisher with the same prefix we are using and then select it. But I would prefer not to do that for every client that needs custom work. it would be nice to just leverage the one Publisher we use for our managed solution so that its all in one publisher reference.

    is there a setting that controls this?

    Tuesday, April 8, 2014 3:15 PM

All replies

  • No settings - you just aren't able to select a publisher that was created by a managed solution. You might just create a "base" unmanaged solution which includes your publisher record to apply your client specific customizations to. 

    After all, if you were distributing some sort of IP you probably wouldn't want somebody grabbing your publisher info and distributing a solution (possibly bad) under your name.

    Jason Lattimer
    My Blog -  Follow me on Twitter -  LinkedIn

    Tuesday, April 8, 2014 4:54 PM
  • When you export your solution, you can edit the XML section <SolutionManifest></Publisher> to refer to the desired publisher UniqueName and CustomizationPrefix when you re-import. 

    However, there are good reasons for why you are prevented from referring to existing managed solution publishers in the UI.  If you have a main 'published' solution and you are adding on customizations for individual clients you may want to consider that it will be easier to track client-specific changes and dependencies if the Custom Prefix is different from that of your main solution.  It is also possible to set different non-conflicting Option Set Value ranges in the custom solution.  Some of the tracking and enforcement then gets handled transparently through CRM.  If it comes down to problem solving and debugging, you may be very glad you have a different publisher assigned to your custom solution.

    Tuesday, April 8, 2014 6:16 PM