Troy Spjute

My feedback

  1. 30 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Troy Spjute commented  · 

    Would it make sense to implement a plugin interface that is compatible with Xrm Toolbox plugins? Instead of re implementing all of the functions already available we could use them from within visual studio. As long as you don't actually copy their code I wouldn't think that licensing would be an issue.
    With that said, the ability to modify OptionSets, Convert one type to another, convert local to global or rename an attribute all sound like useful features. I'm not too worried about bulk updates as there are already tools to do that and it doesn't seem to fit as much into a developer tool set to me.

  2. 43 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Troy Spjute commented  · 

    While this may be a nice feature, I usually only set up On Load and use JavaScript to apply all of the onChange functions (Xrm.Page.getAttribute("").addOnChange()). This way you don't need to deal with setting up all of those onChange functions within CRM, just make sure that onLoad works.

Feedback and Knowledge Base