I've created my own datatype in umbraco... how can I expose it so that it can be used as a macro datatype option?

Unfortunately the datatypes and the macro parameter types are not the same, and as far as I have been told, it is not a easy task to create a new macro parameter type, as you would need to modify the source for that purpose.

What are you ultimately trying to achieve? Maybe there is another way to get it done?

---

Well, one quick fix could be to create 14 (its a lot, I know) "bool" buttons, one for each department, and then use a switch in your usercontrol to find out which department is marked "true".

Another way to go is what it seems like you have already thought about: Making a document type specifically for this macro. Here is how I would do that:

In your content tree, create a folder called "Contact Lists".
Under that folder you then create x number of documents of the type "list".

The "list" documenttype will contain your three fields, and will only be used for storing these options.

What you then do is create a macro that takes _one_ parameter: a contentpicker.

In your usercontrol you then take the nodeId, and look up the setting from that node, and then you display your list based on those parameters.

The downside is that there is a bit more work for the editor the first time they need to create a list. On the other hand, the settings can be reused on another page, since they only have to enter the department header and department info once.

Which one of the above options best could fit your needs is up to you, but I think both of them are quite a bit faster to develop, than to create a new macro parameter type.

---

This is not correct, you don't need to modify the source to add new macro parameter types (I helped a pro customer with this last week, so I know for sure :-D)

---

Jeeeez, did I really start this :-)

I figured out how to do it - just had to look through the source. you just have to have your subclassed web control inherit the umbraco macroRenderings interface (look at the umbraco.macroRenderings project classes for great examples and more population specifics), compile your project, place your dll in the umbraco bin and then add the item to the macroProperties table... doesn't take long at all... amazingly cool stuff Niels - you rock!

forgot to also mention in step one you'll also need to add/customize class members/properties. in my test project subclassing the dropdownlist control I just modified the init method while retaining the value property settings since I didn't need to add any additional parameters... I used the tabPicker object as a template. consult the source umbraco.macroRenderings projects for lots of good samples...

Just thinking out loud here... maybe it is possible to make a macro property type, that functions as a proxy for a regular datatype? That way if you have a datatype with prevalues that is used in a document type, then it could be reused in a macro. :hmm: how to do...

---

Excellent John - any chance you could turn your post into a book?

btw: This topic has been covered on the past two level 2 courses. The format of the level 2 course has changed a bit leaving more time for neat tricks on the last half of day two :)

/n

---

Jeeeez, did I really start this :-)

John,

Instructions on writing an umbraco Book:
http://umbraco.org/documentation/books/books-to-write-list/how-to-get-started-contributing-a-book

Heather

Heather - thanks so much. that's exactly what I need. now I just need to find some time to write it up. I also had a decent post on integrating spell checking into tinyMCE a while back too - that might make a helpful book as well.

Ismail - cool - sounds great. I agree, I think having the ability to populate macro data types really opens up so many doors. Normalizing option data is a big plus and can make things so much easier for the CMS users as well.