CRM Parameter Browser

A few months ago I read a question in Stack Overflow where someone was trying to find out all the available Input/Output parameters in plugins. Unfortunately, there’s no single source that provides the full list of parameters (until now) and the suggested approach was to take a look of the specific request/response in the MSDN (they’re listed under the “Properties” section).

There’s nothing wrong with that answer, but I started to think that it would be great to actually have that list containing all the the possible parameters. Sometimes I need to work with some messages that I’m not very familiar with and it’s necessary to spend some time going trough documentation and/or debugging the plugin to see what information is available in the context.

Parameter Browser

With this idea I’ve created a small web application to put together this information in one single place. Now it’s possible to browse all the messages and have access to the Input and Output Parameters in a really easy way.

I haven’t had the chance to put my hand on a Dynamics 365 On Premise database yet so for now this information is available for CRM 2011, 2013, 2015 and 2016.

You can use it from here. I hope that you find it helpful.
Parameter Browser

Extraction Query

All the data has been extracted from CRM On Premise databases. I based my query in the one available in Michael Palmer’s blog. I added a couple of columns and played a little bit with the types’ name (to make them more readable) but basically the query is still the same.

You can have a look of it here:

https://gist.github.com/fedejousset/f2cc28665dc7740e31d5bdbc0bf376af

Final comments

The project is available in GitHub open to any contribution.

Due to the large number of information, it was not possible for me to test that every parameter in every message is 100% accurate so please let me know if you spot any error with the input/output parameters so I can fix it.

Federico Jousset Written by:

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *