Hi Morten I have tried this with trunk (build # 19453) and assigning the optionSet now seems to function correctly.
However, removing the optionSet is still not possible. Should I be using any specific strategy / mergeStrategy for the remove to function? Many thanks for the quick turn around. Alan On Wed, Jun 17, 2015 at 6:39 PM, Morten Olav Hansen <[email protected]> wrote: > Hi > > Please try again with the latest version of 2.19 or trunk. > > -- > Morten > > On Thu, Jun 18, 2015 at 1:22 AM, Alan Hill <[email protected]> wrote: > >> Hi there >> >> I have a TrackedEntityAttribute created through the web api and want to >> perform an update to both add and remove an optionSet assignment. >> >> I have attempted to do this using a PUT, supplying the JSON previously >> retrieved via a GET and adding/remove the option set and setting the >> valueType accordingly. >> >> Here are the relevant JSON fields: >> >> *Assign* >> >> ... >> valueType: "optionSet", >> optionSet: {id: "<id>"}, >> optionSetValue: true, >> ... >> >> *Remove* >> >> ... >> valueType: "number", >> optionSetValue: false, >> ... >> >> >> However, this seems to make no difference to the attribute. >> >> If I try through the UI to change an attribute valueType from optionSet >> -> number, it still has the optionSet assignment so perhaps this is not >> possible...? >> >> Any advice greatly appreciated. >> >> Thanks >> >> Alan >> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~dhis2-devs >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~dhis2-devs >> More help : https://help.launchpad.net/ListHelp >> >> >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
