locked
Changing publishers once fields have already been created RRS feed

  • Question

  • We created a solution (I'll call it Solution A) and started creating entities and fields for that solution using one Publisher.  We then realized that we wanted to use a different Publisher in the middle of this development (because this functionality should go in another solution, let's call it Solution B).  If I change the publisher of Solution A to the same one as Solution B, all future fields created in Solution A will have the Publisher prefix of Solution B, right?  Is there any way for me to change fields already created and prefixed with Solution A's Publisher?

    • Edited by wikky2007 Thursday, June 6, 2013 2:25 PM
    Thursday, June 6, 2013 2:25 PM

Answers

  • Hi,

    Unfortunately, once the fields have been created with a specific prefix, the only way of changing it is to delete and re-create under the correct solution publisher.

    hth


    Scott Durow
    Blog: www.develop1.net    Follow Me
    Rockstar365  Profile
    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Thursday, June 6, 2013 2:32 PM
    Answerer
  • Your assumption about changing publishers is correct - new fields will use the new prefix. You won't be able to change the previous fields in a supported way without re-creating them. 

    Jason Lattimer
    My Blog -  Follow me on Twitter -  LinkedIn

    Thursday, June 6, 2013 2:35 PM
    Moderator

All replies

  • Hi,

    Unfortunately, once the fields have been created with a specific prefix, the only way of changing it is to delete and re-create under the correct solution publisher.

    hth


    Scott Durow
    Blog: www.develop1.net    Follow Me
    Rockstar365  Profile
    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Thursday, June 6, 2013 2:32 PM
    Answerer
  • Your assumption about changing publishers is correct - new fields will use the new prefix. You won't be able to change the previous fields in a supported way without re-creating them. 

    Jason Lattimer
    My Blog -  Follow me on Twitter -  LinkedIn

    Thursday, June 6, 2013 2:35 PM
    Moderator