# Valuelist provider inconsistency

**URL:** <https://community.bloomreach.com/t/valuelist-provider-inconsistency/2236>\
**Category:** Experience Manager (PaaS/OnPrem)\
**Created:** [November 16, 2020, 11:47am UTC](https://community.bloomreach.com/t/valuelist-provider-inconsistency/2236 "2020-11-16T11:47:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jesper\_Volkers](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/jesper_volkers/32/146_2.png) [@Jesper\_Volkers](https://community.bloomreach.com/u/Jesper_Volkers)\
**Post date:** [November 16, 2020, 11:47am UTC](https://community.bloomreach.com/t/valuelist-provider-inconsistency/2236/1 "2020-11-16T11:47:43Z")

</div>

Hi!

After struggling with custom value lists I found out a really inconvenient inconsistency. The issue is the following:

When creating a custom value list provider, you need to extend the following class:  
_org.onehippo.forge.selection.frontend.provider.IValueListProvider_  
Which contains the following property: `String SERVICE = "valuelist.provider";`

When reading the following [documentation](https://documentation.bloomreach.com/14/library/concepts/plugins/selections/configuration.html), it will tell me to use valuelistProvider

Although when using the default DynamicDropdown field (_org.onehippo.cms.channelmanager.content.documenttype.field.type.DynamicDropdownFieldType_) , the following value is used  
_org.onehippo.forge.selection.frontend.plugin.Config_ -\>  
`public static final String VALUELIST_PROVIDER = "valuelistProvider";`

So when using a _org.onehippo.forge.selection.frontend.plugin.DynamicMultiSelectPlugin_, you need to configure the property **valuelist.provider** , but when using the DynamicDropdown you need to use **valuelistProvider**.

This took me a while to find out, especially when the difference is so small. So I hope this could change into the same value to make this more convenient in the future. In the mean time, I hope other developers will find this post before having to deep dive into this topic again. Maybe a short time fix would be to include a note into the documentation?

Have a nice day!

Cheers,  
Jesper