Hi, My guess is that this is a bug in SF's template parsing. You can get around it, though, by using the "property=" parameter in the form field, to manually connect the field to a property.
-Yaron On Sat, Jun 20, 2009 at 5:48 AM, Martien <martien.van.steenber...@gmail.com>wrote: > > I have two string properties: > > Property:Is_written_in_language with allowed values Nederlands, > Engels, Duits, Frans, Spaans. > Property:Is_originally_written_in_language with allowed values > Nederlands, Engels, Duits, Frans, Spaans, Italiaans, Japans, Chinees. > > Both have their own unique lists of allowed values (see above) > Both are used in Form:Publication. > > Property:Is_written_in_language shows as a text field. > Property:Is_originally_written_in_language shows as a pop-up menu. > > Can't find out why there is this difference. > > Would like them both to be dropdown menus. > > See http://aardnoot.nl/Speciaal:GegevensToevoegen/Publikatie/Test. > > Any help appreciated. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Semantic Forms" group. To post to this group, send email to semantic-forms@googlegroups.com To unsubscribe from this group, send email to semantic-forms+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/semantic-forms?hl=en -~----------~----~----~----~------~----~------~--~---
