# valuelist issue

**URL:** <https://forum.servoy.com/t/valuelist-issue/7798>\
**Category:** Classic Servoy\
**Created:** [July 11, 2007, 3:00am UTC](https://forum.servoy.com/t/valuelist-issue/7798 "2007-07-11T03:00:40Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![faheemhameed](https://avatars.discourse-cdn.com/v4/letter/f/7ea924/32.png) [@faheemhameed](https://forum.servoy.com/u/faheemhameed)\
**Post date:** [July 11, 2007, 3:00am UTC](https://forum.servoy.com/t/valuelist-issue/7798/1 "2007-07-11T03:00:40Z")

</div>

I am not sure why I am getting this error in the developer.

> The valuelist was already created for type: INTEGER  
> for the dataproviders: stone\_color  
> So it can’t be uses also for type: TEXT for the dataprovider: stone\_color  
> Please check these dataproviders of this valuelist: product$stoneColor

I had wrongly assigned this valuelist to product$stoneColor firstly.  
Then I tried to assign this to the correct dataprovider.  
But I get the above error message.

Thanks.

---

<div class="post-metadata">

**Author:** ![patrick](https://avatars.discourse-cdn.com/v4/letter/p/b2d939/32.png) [@patrick](https://forum.servoy.com/u/patrick)\
**Post date:** [July 11, 2007, 6:27am UTC](https://forum.servoy.com/t/valuelist-issue/7798/2 "2007-07-11T06:27:04Z")

</div>

Servoy remembers the first assignment. Do you also get this error after a restart?

---

<div class="post-metadata">

**Author:** ![faheemhameed](https://avatars.discourse-cdn.com/v4/letter/f/7ea924/32.png) [@faheemhameed](https://forum.servoy.com/u/faheemhameed)\
**Post date:** [July 11, 2007, 6:33am UTC](https://forum.servoy.com/t/valuelist-issue/7798/3 "2007-07-11T06:33:41Z")

</div>

Yes I get the error after the restart of the developer.

---

<div class="post-metadata">

**Author:** ![patrick](https://avatars.discourse-cdn.com/v4/letter/p/b2d939/32.png) [@patrick](https://forum.servoy.com/u/patrick)\
**Post date:** [July 11, 2007, 7:40am UTC](https://forum.servoy.com/t/valuelist-issue/7798/4 "2007-07-11T07:40:59Z")

</div>

And you are 100% sure that this value list is now used “correctly”?

---

<div class="post-metadata">

**Author:** ![faheemhameed](https://avatars.discourse-cdn.com/v4/letter/f/7ea924/32.png) [@faheemhameed](https://forum.servoy.com/u/faheemhameed)\
**Post date:** [July 11, 2007, 7:57am UTC](https://forum.servoy.com/t/valuelist-issue/7798/5 "2007-07-11T07:57:47Z")

</div>

Yes it is. I mean it is just used for a text field now called stone\_color

---

<div class="post-metadata">

**Author:** ![SV-Kelvin](https://avatars.discourse-cdn.com/v4/letter/s/b3f665/32.png) [@SV-Kelvin](https://forum.servoy.com/u/SV-Kelvin)\
**Post date:** [July 12, 2007, 1:41am UTC](https://forum.servoy.com/t/valuelist-issue/7798/6 "2007-07-12T01:41:11Z")

</div>

I have the same problem before. Please check your other form that  
use this valuelist. It may attched to different field type.

Kelvin

---

<div class="post-metadata">

**Author:** ![janteque](https://avatars.discourse-cdn.com/v4/letter/j/848f3c/32.png) [@janteque](https://forum.servoy.com/u/janteque)\
**Post date:** [November 14, 2007, 5:45pm UTC](https://forum.servoy.com/t/valuelist-issue/7798/7 "2007-11-14T17:45:08Z")

</div>

I’me getting the same problem:

The valuelist was already created for type: INTEGER  
for the dataproviders: aborto\_repe\_bt  
So it can’t be uses also for type: TEXT for the dataprovider: rs\_tb\_pro\_esterilidad\_tb\_tto\_prev\_ext.fecundacion\_bt  
Please check these dataproviders of this valuelist: L\_Si\_no

But dataprovider fecundacion\_bt is of type INTEGER. I don’t get why I’m getting this error…

---

<div class="post-metadata">

**Author:** ![janteque](https://avatars.discourse-cdn.com/v4/letter/j/848f3c/32.png) [@janteque](https://forum.servoy.com/u/janteque)\
**Post date:** [November 14, 2007, 6:43pm UTC](https://forum.servoy.com/t/valuelist-issue/7798/8 "2007-11-14T18:43:37Z")

</div>

We got it solved.

The field _fecundacion\_bt_ was in a portal and the problem was that we’d changed the relation in which it was based, so instead of _rs\_tb\_pro\_esterilidad\_tb\_tto\_prev\_ext_ the portal now uses another relation.

Surprisingly, the portal worked fine, and showed the results, but we got this alert every time the form was loaded.

We’ve fixed the dataprovider and now everything works.