Hi Morten,
Some more information on this:
On an empty DHIS database, I ran the options payload only.
{
options: [{
code: b64365ac185,
id: b64365ac185,
name: One
}, {
code: b65ad0e22c5,
id: b65ad0e22c5,
name: One
}]
}
After that, I
This is now fixed in the latest trunk + 2.17
--
Morten
On Mon, Dec 1, 2014 at 3:19 PM, Simanta Jyoti Handique
shandi...@thoughtworks.com wrote:
Hi Morten,
Some more information on this:
On an empty DHIS database, I ran the options payload only.
{
options: [{
code:
Great, thanks!
On Mon, Dec 1, 2014 at 2:06 PM, Morten Olav Hansen morte...@gmail.com
wrote:
This is now fixed in the latest trunk + 2.17
--
Morten
On Mon, Dec 1, 2014 at 3:19 PM, Simanta Jyoti Handique
shandi...@thoughtworks.com wrote:
Hi Morten,
Some more information on this:
On
Hello Lars,
We are trying to create 'options' and 'optionSets' on empty Database.
Request Payload:
{
optionSets: [{
id: b73c773,
name: Hours,
options: [{
code: b64365ac185,
id: b64365ac185,
name: One
}]
}, {
Hi
Please remember that the way we handle options/optionSets have been changed
now. You need to have options option code=codea name=Option A /
/options optionSets optionSet optionsoption code=codea /
/options /optionSets
This now works as any other metadata... you first define the options, then
5 matches
Mail list logo