Easier Way to Manage Plugin Step and Image Configuration

(0) Share

Report

Posted on by Community Member

Good day,

I have previously been using the SDK Plugin Registration Tool in order to register new plugin steps and images.

Now, me as the developer doing this isn't too bad. If I accidentally misconfigure a step and create create an infinite update loop or something, I know where the problem is and can fix it. The problem is that I am now handing this project over to less technical users who will need to occasionally rebuild and reregister plugins. Unfortunately, with the SDK Plugin Registration Tool this process is tedious and lots can go wrong.

Is there a better way to configure this data programmatically (for instance in the IPlugin class)? Or at the very least, a configuration file would be ideal. This would remove the chance of simple human error.

Thanks,

BGS

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Aric Levin - MVP 30,190 Moderator on at

Like (0)

Report
Copy link

Link copied!

You can publish and create plugins from code if necessary. Take a look at the SDK samples, or you can use the following example:

community.dynamics.com/.../publishing-plugin-steps-from-code

Hope this helps.

Was this reply helpful? Yes No
Suggested answer

Mahendar Pal 45,095 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Another option is to use developer toolkit, where you can write and deploy your code from visual studio itself.

marketplace.visualstudio.com/items

Thanks

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hey Aric,

I did look into doing this programmatically similar to your post. For our situation I don't think this type of approach is streamlined/simple enough. For instance, how would one specify which fields to trigger an update step on?

It would be nice if someone (but, of course, not *me* ;) ) could put together a library/tool that would make calls like this much easier. (Basically replicating the Plugin Registration Tools forms, but programmatically.)

Thanks for the suggestion though.

Was this reply helpful? Yes No