Hey team, we're configuring a re-usable, open-source CommCare to anything*
integration (Ile Eftimov mentioned this on another thread—excited to
release it to your community!) and it would be wonderful if we could set up
data forwarding for forms and cases in JSON, rather than XML. Is this
supported currently (sorry if I've missed it) or is it in development?
This doesn't exist today but I'm going to look into it and see if it's
something that can be quickly added.
Will report back soon.
thanks,
Cory
···
On Thu, Aug 27, 2015 at 8:16 AM, Taylor Downs wrote:
Hey team, we're configuring a re-usable, open-source CommCare to anything*
integration (Ile Eftimov mentioned this on another thread—excited to
release it to your community!) and it would be wonderful if we could set up
data forwarding for forms and cases in JSON, rather than XML. Is this
supported currently (sorry if I've missed it) or is it in development?
···
On Thu, 27 Aug 2015 at 08:16 Taylor Downs wrote:
Hey team, we're configuring a re-usable, open-source CommCare to anything*
integration (Ile Eftimov mentioned this on another thread—excited to
release it to your community!) and it would be wonderful if we could set up
data forwarding for forms and cases in JSON, rather than XML. Is this
supported currently (sorry if I've missed it) or is it in development?
Hey team, we're configuring a re-usable, open-source CommCare to
anything* integration (Ile Eftimov mentioned this on another thread—excited
to release it to your community!) and it would be wonderful if we could set
up data forwarding for forms and cases in JSON, rather than XML. Is this
supported currently (sorry if I've missed it) or is it in development?
Hey team, we're configuring a re-usable, open-source CommCare to
anything* integration (Ile Eftimov mentioned this on another thread—excited
to release it to your community!) and it would be wonderful if we could set
up data forwarding for forms and cases in JSON, rather than XML. Is this
supported currently (sorry if I've missed it) or is it in development?
Hey team, we're configuring a re-usable, open-source CommCare to
anything* integration (Ile Eftimov mentioned this on another thread—excited
to release it to your community!) and it would be wonderful if we could set
up data forwarding for forms and cases in JSON, rather than XML. Is this
supported currently (sorry if I've missed it) or is it in development?
Hey team, we're configuring a re-usable, open-source CommCare to
anything* integration (Ile Eftimov mentioned this on another thread—excited
to release it to your community!) and it would be wonderful if we could set
up data forwarding for forms and cases in JSON, rather than XML. Is this
supported currently (sorry if I've missed it) or is it in development?
Hey team, we're configuring a re-usable, open-source CommCare to
anything* integration (Ile Eftimov mentioned this on another thread—excited
to release it to your community!) and it would be wonderful if we could set
up data forwarding for forms and cases in JSON, rather than XML. Is this
supported currently (sorry if I've missed it) or is it in development?
This has now been deployed. When you create a form repeater you can select
'JSON' as the format. If you have any problems with it please report an
issue.
Thanks
Simon
···
On 22 September 2015 at 12:20, Taylor Downs wrote:
Hey team, we're configuring a re-usable, open-source CommCare to
anything* integration (Ile Eftimov mentioned this on another thread—excited
to release it to your community!) and it would be wonderful if we could set
up data forwarding for forms and cases in JSON, rather than XML. Is this
supported currently (sorry if I've missed it) or is it in development?
Thanks very much! The web configuration looks good. Will test with
submissions today or tomorrow.
···
On Wed, 23 Sep 2015 at 09:27 Simon Kelly wrote:
Hi Taylor
This has now been deployed. When you create a form repeater you can select
'JSON' as the format. If you have any problems with it please report an
issue.
Hey team, we're configuring a re-usable, open-source CommCare to
anything* integration (Ile Eftimov mentioned this on another thread—excited
to release it to your community!) and it would be wonderful if we could set
up data forwarding for forms and cases in JSON, rather than XML. Is this
supported currently (sorry if I've missed it) or is it in development?
It seems as though JSON forwarding might have stopped working. Were there
any changes to data forwarding recently? When I select forward as JSON and
test an endpoint, I receive this:
So when it's stored as JSON in a DB we get only {"aspect":"body_params"}
Do you guys know anything about this? Thanks so much for you help! (Not to
sound alarmist, but there's at least one client who's using JSON forwarding
in a production system now.)
Best,
Taylor
···
On Wednesday, 23 September 2015 09:44:50 UTC-4, Taylor Downs wrote:
>
> Thanks very much! The web configuration looks good. Will test with
> submissions today or tomorrow.
>
> On Wed, 23 Sep 2015 at 09:27 Simon Kelly wrote:
>
>> Hi Taylor
>>
>> This has now been deployed. When you create a form repeater you can
>> select 'JSON' as the format. If you have any problems with it please report
>> an issue.
>>
>> Thanks
>> Simon
>>
>> On 22 September 2015 at 12:20, Taylor Downs wrote:
>>
>>> Thanks very much, Simon.
>>>
>>> On Tue, Sep 22, 2015, 12:05 PM Simon Kelly wrote:
>>>
>>>> Hi Taylor
>>>>
>>>> I'll take a look at adding this.
>>>>
>>>> On 22 September 2015 at 10:47, Taylor Downs wrote:
>>>>
>>>>> Hi Cory, is it possible to do the same thing for "forms" as well as
>>>>> "cases"? Thank you?
>>>>>
>>>>> Taylor
>>>>>
>>>>> On Fri, 28 Aug 2015 at 16:42 Taylor Downs wrote:
>>>>>
>>>>>> That's fantastic. Really appreciate the support. Thank you, Cory.
>>>>>>
>>>>>> Taylor
>>>>>>
>>>>>> On Fri, Aug 28, 2015 at 10:47 AM, Cory Zue wrote:
>>>>>>
>>>>>>> Hey Taylor,
>>>>>>>
>>>>>>> A change to support JSON formatting will go out on tonight's release
>>>>>>> and should be available by end of day.
>>>>>>>
>>>>>>> I've taken the liberty of updating the documentation ahead of time:
>>>>>>> https://confluence.dimagi.com/pages/viewpage.action?pageId=12224128
>>>>>>>
>>>>>>> cheers,
>>>>>>> Cory
>>>>>>>
>>>>>>> On Fri, Aug 28, 2015 at 7:23 AM, Taylor Downs < downs.taylor@gmail.com> wrote:
>>>>>>>
>>>>>>>> Thanks, Cory! Much appreciated.
>>>>>>>>
>>>>>>>> On Thu, 27 Aug 2015 at 08:16 Taylor Downs wrote:
>>>>>>>>
>>>>>>>>> Hey team, we're configuring a re-usable, open-source CommCare to
>>>>>>>>> anything* integration (Ile Eftimov mentioned this on another thread—excited
>>>>>>>>> to release it to your community!) and it would be wonderful if we could set
>>>>>>>>> up data forwarding for forms and cases in JSON, rather than XML. Is this
>>>>>>>>> supported currently (sorry if I've missed it) or is it in development?
>>>>>>>>>
>>>>>>>>> Have had great success with the "publish to JSON" feature on ODK
>>>>>>>>> Aggregate. Hoping for something like that. This is where I'm looking now:
>>>>>>>>> https://confluence.dimagi.com/pages/viewpage.action?pageId=12224128
>>>>>>>>>
>>>>>>>>> Taylor
>>>>>>>>>
>>>>>>>>> *The first destination use-case is Salesforce.com
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> ---
>>>>>>>>> You received this message because you are subscribed to a topic in
>>>>>>>>> the Google Groups "CommCare Developers" group.
>>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>>> https://groups.google.com/d/topic/commcare-developers/bbhjuLWyJnA/unsubscribe
>>>>>>>>> .
>>>>>>>>> To unsubscribe from this group and all its topics, send an email
>>>>>>>>> to commcare-developers+unsubscribe@googlegroups.com.
>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> ---
>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>> Groups "CommCare Developers" group.
>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>> send an email to commcare-developers+unsubscribe@googlegroups.com.
>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> ---
>>>>>>> You received this message because you are subscribed to a topic in
>>>>>>> the Google Groups "CommCare Developers" group.
>>>>>>> To unsubscribe from this topic, visit
>>>>>>> https://groups.google.com/d/topic/commcare-developers/bbhjuLWyJnA/unsubscribe
>>>>>>> .
>>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>>> commcare-developers+unsubscribe@googlegroups.com.
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>> --
>>>>>
>>>>> ---
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "CommCare Developers" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to commcare-developers+unsubscribe@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Simon Kelly
>>>> Senior Engineer | Dimagi South Africa
>>>>
>>>> --
>>>>
>>>> ---
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "CommCare Developers" group.
>>>> To unsubscribe from this topic, visit
>>>> https://groups.google.com/d/topic/commcare-developers/bbhjuLWyJnA/unsubscribe
>>>> .
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> commcare-developers+unsubscribe@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "CommCare Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to commcare-developers+unsubscribe@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Simon Kelly
>> Senior Engineer | Dimagi South Africa
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "CommCare Developers" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/commcare-developers/bbhjuLWyJnA/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> commcare-developers+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
I think the that's an oversight on our side where the 'test url' button
just always sends XML. But I think the real payload should still be JSON.
···
On 11 December 2015 at 17:07, Taylor Downs wrote:
Hi Simon and Cory,
It seems as though JSON forwarding might have stopped working. Were there
any changes to data forwarding recently? When I select forward as JSON and
test an endpoint, I receive this:
So when it's stored as JSON in a DB we get only {"aspect":"body_params"}
Do you guys know anything about this? Thanks so much for you help! (Not to
sound alarmist, but there's at least one client who's using JSON forwarding
in a production system now.)
Best,
Taylor
On Wednesday, 23 September 2015 09:44:50 UTC-4, Taylor Downs wrote:
Thanks very much! The web configuration looks good. Will test with
submissions today or tomorrow.
This has now been deployed. When you create a form repeater you can
select 'JSON' as the format. If you have any problems with it please report
an issue.
Hey team, we're configuring a re-usable, open-source CommCare to
anything* integration (Ile Eftimov mentioned this on another thread—excited
to release it to your community!) and it would be wonderful if we could set
up data forwarding for forms and cases in JSON, rather than XML. Is this
supported currently (sorry if I've missed it) or is it in development?
Hey Simon, just confirming that real data is being sent as XML also, not
just the test post. It appears to be different when I send to an HTTP
endpoint and when I send to an HTTPS endpoint. On HTTPS (that Phoenix app),
we're getting {"aspect":"body_params"}. I did get JSON on HTTP in the
Sinatra app, but am having a hard time replicating it.
···
On Friday, 11 December 2015 10:48:05 UTC-5, Taylor Downs wrote:
>
> Also potentially relevant information: We always carry a significant lag
> on the data forwarding. Right now there are 15 "pending" items. Do you know
> what might be causing this?
>
> All endpoints are configured to respond with either a 200 or a 202 and do
> so immediately when we send test posts.
>
> Taylor
>
> On Fri, 11 Dec 2015 at 10:44 Taylor Downs wrote:
>
>> Thanks for the swift response, Simon! I noticed this the other day
>> without having clicked the test button... when the post is stored as JSON
>> (using an Phoenix/Elixir app, for what it's worth) it just shows up as
>> {"aspect":"body_params"}. I've set up a listner that will store it as
>> plain old text in a Sinatra app to see what comes in over the next day.
>> Will keep you posted.
>>
>> Also, if you did have the chance to iron it out, sorting the JSON test
>> post would make configuring and testing the integrations much easier! In
>> the past, I'm pretty sure the JSON test post worked.
>>
>> Thanks again. I know it's getting late for you!
>>
>> TD
>>
>> On Fri, 11 Dec 2015 at 10:26 Simon Kelly wrote:
>>
>>> Hi Taylor
>>>
>>> I think the that's an oversight on our side where the 'test url' button
>>> just always sends XML. But I think the real payload should still be JSON.
>>>
>>> On 11 December 2015 at 17:07, Taylor Downs wrote:
>>>
>>>> Hi Simon and Cory,
>>>>
>>>> It seems as though JSON forwarding might have stopped working. Were
>>>> there any changes to data forwarding recently? When I select forward as
>>>> JSON and test an endpoint, I receive this:
>>>>
>>>> - Dec 11 06:55:36 openfn-listen
>>>>
>>>> app/web.1
>>>>
>>>> : <?xml version='1.0' ?>Test post from
>>>> CommCareHQ on 2015-12-11 14:55:36.464039
>>>>
>>>> So when it's stored as JSON in a DB we get only `
>>>> {"aspect":"body_params"}`
>>>>
>>>> Do you guys know anything about this? Thanks so much for you help! (Not
>>>> to sound alarmist, but there's at least one client who's using JSON
>>>> forwarding in a production system now.)
>>>>
>>>> Best,
>>>> Taylor
>>>>
>>>> On Wednesday, 23 September 2015 09:44:50 UTC-4, Taylor Downs wrote:
>>>>>
>>>>> Thanks very much! The web configuration looks good. Will test with
>>>>> submissions today or tomorrow.
>>>>>
>>>>> On Wed, 23 Sep 2015 at 09:27 Simon Kelly wrote:
>>>>>
>>>>>> Hi Taylor
>>>>>>
>>>>>> This has now been deployed. When you create a form repeater you can
>>>>>> select 'JSON' as the format. If you have any problems with it please report
>>>>>> an issue.
>>>>>>
>>>>>> Thanks
>>>>>> Simon
>>>>>>
>>>>>> On 22 September 2015 at 12:20, Taylor Downs wrote:
>>>>>>
>>>>>>> Thanks very much, Simon.
>>>>>>>
>>>>>>> On Tue, Sep 22, 2015, 12:05 PM Simon Kelly wrote:
>>>>>>>
>>>>>>>> Hi Taylor
>>>>>>>>
>>>>>>>> I'll take a look at adding this.
>>>>>>>>
>>>>>>>> On 22 September 2015 at 10:47, Taylor Downs >>>>>>>
>>>>>>>>> Hi Cory, is it possible to do the same thing for "forms" as well
>>>>>>>>> as "cases"? Thank you?
>>>>>>>>>
>>>>>>>>> Taylor
>>>>>>>>>
>>>>>>>>> On Fri, 28 Aug 2015 at 16:42 Taylor Downs wrote:
>>>>>>>>>
>>>>>>>>>> That's fantastic. Really appreciate the support. Thank you, Cory.
>>>>>>>>>>
>>>>>>>>>> Taylor
>>>>>>>>>>
>>>>>>>>>> On Fri, Aug 28, 2015 at 10:47 AM, Cory Zue wrote:
>>>>>>>>>>
>>>>>>>>>>> Hey Taylor,
>>>>>>>>>>>
>>>>>>>>>>> A change to support JSON formatting will go out on tonight's
>>>>>>>>>>> release and should be available by end of day.
>>>>>>>>>>>
>>>>>>>>>>> I've taken the liberty of updating the documentation ahead of
>>>>>>>>>>> time:
>>>>>>>>>>> https://confluence.dimagi.com/pages/viewpage.action?pageId=12224128
>>>>>>>>>>>
>>>>>>>>>>> cheers,
>>>>>>>>>>> Cory
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Aug 28, 2015 at 7:23 AM, Taylor Downs < downs.taylor@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Thanks, Cory! Much appreciated.
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, 27 Aug 2015 at 08:16 Taylor Downs < downs.taylor@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hey team, we're configuring a re-usable, open-source CommCare
>>>>>>>>>>>>> to anything* integration (Ile Eftimov mentioned this on another
>>>>>>>>>>>>> thread—excited to release it to your community!) and it would be wonderful
>>>>>>>>>>>>> if we could set up data forwarding for forms and cases in JSON, rather than
>>>>>>>>>>>>> XML. Is this supported currently (sorry if I've missed it) or is it in
>>>>>>>>>>>>> development?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Have had great success with the "publish to JSON" feature on
>>>>>>>>>>>>> ODK Aggregate. Hoping for something like that. This is where I'm looking
>>>>>>>>>>>>> now:
>>>>>>>>>>>>> https://confluence.dimagi.com/pages/viewpage.action?pageId=12224128
>>>>>>>>>>>>>
>>>>>>>>>>>>> Taylor
>>>>>>>>>>>>>
>>>>>>>>>>>>> *The first destination use-case is Salesforce.com
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>>
>>>>>>>>>>>>> ---
>>>>>>>>>>>>> You received this message because you are subscribed to a
>>>>>>>>>>>>> topic in the Google Groups "CommCare Developers" group.
>>>>>>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>>>>>>> https://groups.google.com/d/topic/commcare-developers/bbhjuLWyJnA/unsubscribe
>>>>>>>>>>>>> .
>>>>>>>>>>>>> To unsubscribe from this group and all its topics, send an
>>>>>>>>>>>>> email to commcare-developers+unsubscribe@googlegroups.com.
>>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>>
>>>>>>>>>>>> ---
>>>>>>>>>>>> You received this message because you are subscribed to the
>>>>>>>>>>>> Google Groups "CommCare Developers" group.
>>>>>>>>>>>> To unsubscribe from this group and stop receiving emails from
>>>>>>>>>>>> it, send an email to
>>>>>>>>>>>> commcare-developers+unsubscribe@googlegroups.com.
>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>>
>>>>>>>>>>> ---
>>>>>>>>>>> You received this message because you are subscribed to a topic
>>>>>>>>>>> in the Google Groups "CommCare Developers" group.
>>>>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>>>>> https://groups.google.com/d/topic/commcare-developers/bbhjuLWyJnA/unsubscribe
>>>>>>>>>>> .
>>>>>>>>>>> To unsubscribe from this group and all its topics, send an email
>>>>>>>>>>> to commcare-developers+unsubscribe@googlegroups.com.
>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> ---
>>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>>> Groups "CommCare Developers" group.
>>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>>> send an email to commcare-developers+unsubscribe@googlegroups.com.
>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Simon Kelly
>>>>>>>> Senior Engineer | Dimagi South Africa
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> ---
>>>>>>>> You received this message because you are subscribed to a topic in
>>>>>>>> the Google Groups "CommCare Developers" group.
>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>> https://groups.google.com/d/topic/commcare-developers/bbhjuLWyJnA/unsubscribe
>>>>>>>> .
>>>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>>>> commcare-developers+unsubscribe@googlegroups.com.
>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> ---
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "CommCare Developers" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>> send an email to commcare-developers+unsubscribe@googlegroups.com.
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Simon Kelly
>>>>>> Senior Engineer | Dimagi South Africa
>>>>>>
>>>>>> --
>>>>>>
>>>>>> ---
>>>>>> You received this message because you are subscribed to a topic in
>>>>>> the Google Groups "CommCare Developers" group.
>>>>>> To unsubscribe from this topic, visit
>>>>>> https://groups.google.com/d/topic/commcare-developers/bbhjuLWyJnA/unsubscribe
>>>>>> .
>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>> commcare-developers+unsubscribe@googlegroups.com.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>> --
>>>>
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "CommCare Developers" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to commcare-developers+unsubscribe@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Simon Kelly
>>> Senior Engineer | Dimagi South Africa
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "CommCare Developers" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/commcare-developers/bbhjuLWyJnA/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to
>>> commcare-developers+unsubscribe@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
Thanks for the swift response, Simon! I noticed this the other day without
having clicked the test button... when the post is stored as JSON (using an
Phoenix/Elixir app, for what it's worth) it just shows up as
{"aspect":"body_params"}. I've set up a listner that will store it as plain
old text in a Sinatra app to see what comes in over the next day. Will keep
you posted.
Also, if you did have the chance to iron it out, sorting the JSON test post
would make configuring and testing the integrations much easier! In the
past, I'm pretty sure the JSON test post worked.
Thanks again. I know it's getting late for you!
TD
···
On Fri, 11 Dec 2015 at 10:26 Simon Kelly wrote:
Hi Taylor
I think the that's an oversight on our side where the 'test url' button
just always sends XML. But I think the real payload should still be JSON.
It seems as though JSON forwarding might have stopped working. Were there
any changes to data forwarding recently? When I select forward as JSON and
test an endpoint, I receive this:
So when it's stored as JSON in a DB we get only {"aspect":"body_params"}
Do you guys know anything about this? Thanks so much for you help! (Not
to sound alarmist, but there's at least one client who's using JSON
forwarding in a production system now.)
Best,
Taylor
On Wednesday, 23 September 2015 09:44:50 UTC-4, Taylor Downs wrote:
Thanks very much! The web configuration looks good. Will test with
submissions today or tomorrow.
This has now been deployed. When you create a form repeater you can
select 'JSON' as the format. If you have any problems with it please report
an issue.
Hey team, we're configuring a re-usable, open-source CommCare to
anything* integration (Ile Eftimov mentioned this on another thread—excited
to release it to your community!) and it would be wonderful if we could set
up data forwarding for forms and cases in JSON, rather than XML. Is this
supported currently (sorry if I've missed it) or is it in development?
Also potentially relevant information: We always carry a significant lag on
the data forwarding. Right now there are 15 "pending" items. Do you know
what might be causing this?
All endpoints are configured to respond with either a 200 or a 202 and do
so immediately when we send test posts.
Taylor
···
On Fri, 11 Dec 2015 at 10:44 Taylor Downs wrote:
Thanks for the swift response, Simon! I noticed this the other day without
having clicked the test button... when the post is stored as JSON (using an
Phoenix/Elixir app, for what it's worth) it just shows up as
{"aspect":"body_params"}. I've set up a listner that will store it as
plain old text in a Sinatra app to see what comes in over the next day.
Will keep you posted.
Also, if you did have the chance to iron it out, sorting the JSON test
post would make configuring and testing the integrations much easier! In
the past, I'm pretty sure the JSON test post worked.
It seems as though JSON forwarding might have stopped working. Were
there any changes to data forwarding recently? When I select forward as
JSON and test an endpoint, I receive this:
So when it's stored as JSON in a DB we get only {"aspect":"body_params"}
Do you guys know anything about this? Thanks so much for you help! (Not
to sound alarmist, but there's at least one client who's using JSON
forwarding in a production system now.)
Best,
Taylor
On Wednesday, 23 September 2015 09:44:50 UTC-4, Taylor Downs wrote:
Thanks very much! The web configuration looks good. Will test with
submissions today or tomorrow.
This has now been deployed. When you create a form repeater you can
select 'JSON' as the format. If you have any problems with it please report
an issue.
Hey team, we're configuring a re-usable, open-source CommCare
to anything* integration (Ile Eftimov mentioned this on another
thread—excited to release it to your community!) and it would be wonderful
if we could set up data forwarding for forms and cases in JSON, rather than
XML. Is this supported currently (sorry if I've missed it) or is it in
development?
Sorry to hear that. We'll definitely get on to fixing that. We'll use Case
184464 to track the status and move future communications to that ticket.
Hey Simon, just confirming that real data is being sent as XML also, not
just the test post. It appears to be different when I send to an HTTP
endpoint and when I send to an HTTPS endpoint. On HTTPS (that Phoenix app),
we're getting {"aspect":"body_params"}. I did get JSON on HTTP in the
Sinatra app, but am having a hard time replicating it.
···
On Friday, 11 December 2015 10:48:05 UTC-5, Taylor Downs wrote:
>
> Also potentially relevant information: We always carry a significant lag
> on the data forwarding. Right now there are 15 "pending" items. Do you know
> what might be causing this?
>
> All endpoints are configured to respond with either a 200 or a 202 and do
> so immediately when we send test posts.
>
> Taylor
>
> On Fri, 11 Dec 2015 at 10:44 Taylor Downs wrote:
>
>> Thanks for the swift response, Simon! I noticed this the other day
>> without having clicked the test button... when the post is stored as JSON
>> (using an Phoenix/Elixir app, for what it's worth) it just shows up as
>> {"aspect":"body_params"}. I've set up a listner that will store it as
>> plain old text in a Sinatra app to see what comes in over the next day.
>> Will keep you posted.
>>
>> Also, if you did have the chance to iron it out, sorting the JSON test
>> post would make configuring and testing the integrations much easier! In
>> the past, I'm pretty sure the JSON test post worked.
>>
>> Thanks again. I know it's getting late for you!
>>
>> TD
>>
>> On Fri, 11 Dec 2015 at 10:26 Simon Kelly wrote:
>>
>>> Hi Taylor
>>>
>>> I think the that's an oversight on our side where the 'test url' button
>>> just always sends XML. But I think the real payload should still be JSON.
>>>
>>> On 11 December 2015 at 17:07, Taylor Downs wrote:
>>>
>>>> Hi Simon and Cory,
>>>>
>>>> It seems as though JSON forwarding might have stopped working. Were
>>>> there any changes to data forwarding recently? When I select forward as
>>>> JSON and test an endpoint, I receive this:
>>>>
>>>> - Dec 11 06:55:36 openfn-listen
>>>>
>>>> app/web.1
>>>>
>>>> : <?xml version='1.0' ?>Test post from
>>>> CommCareHQ on 2015-12-11 14:55:36.464039
>>>>
>>>> So when it's stored as JSON in a DB we get only `
>>>> {"aspect":"body_params"}`
>>>>
>>>> Do you guys know anything about this? Thanks so much for you help! (Not
>>>> to sound alarmist, but there's at least one client who's using JSON
>>>> forwarding in a production system now.)
>>>>
>>>> Best,
>>>> Taylor
>>>>
>>>> On Wednesday, 23 September 2015 09:44:50 UTC-4, Taylor Downs wrote:
>>>>>
>>>>> Thanks very much! The web configuration looks good. Will test with
>>>>> submissions today or tomorrow.
>>>>>
>>>>> On Wed, 23 Sep 2015 at 09:27 Simon Kelly wrote:
>>>>>
>>>>>> Hi Taylor
>>>>>>
>>>>>> This has now been deployed. When you create a form repeater you can
>>>>>> select 'JSON' as the format. If you have any problems with it please report
>>>>>> an issue.
>>>>>>
>>>>>> Thanks
>>>>>> Simon
>>>>>>
>>>>>> On 22 September 2015 at 12:20, Taylor Downs wrote:
>>>>>>
>>>>>>> Thanks very much, Simon.
>>>>>>>
>>>>>>> On Tue, Sep 22, 2015, 12:05 PM Simon Kelly wrote:
>>>>>>>
>>>>>>>> Hi Taylor
>>>>>>>>
>>>>>>>> I'll take a look at adding this.
>>>>>>>>
>>>>>>>> On 22 September 2015 at 10:47, Taylor Downs >>>>>>>
>>>>>>>>> Hi Cory, is it possible to do the same thing for "forms" as well
>>>>>>>>> as "cases"? Thank you?
>>>>>>>>>
>>>>>>>>> Taylor
>>>>>>>>>
>>>>>>>>> On Fri, 28 Aug 2015 at 16:42 Taylor Downs wrote:
>>>>>>>>>
>>>>>>>>>> That's fantastic. Really appreciate the support. Thank you, Cory.
>>>>>>>>>>
>>>>>>>>>> Taylor
>>>>>>>>>>
>>>>>>>>>> On Fri, Aug 28, 2015 at 10:47 AM, Cory Zue wrote:
>>>>>>>>>>
>>>>>>>>>>> Hey Taylor,
>>>>>>>>>>>
>>>>>>>>>>> A change to support JSON formatting will go out on tonight's
>>>>>>>>>>> release and should be available by end of day.
>>>>>>>>>>>
>>>>>>>>>>> I've taken the liberty of updating the documentation ahead of
>>>>>>>>>>> time:
>>>>>>>>>>> https://confluence.dimagi.com/pages/viewpage.action?pageId=12224128
>>>>>>>>>>>
>>>>>>>>>>> cheers,
>>>>>>>>>>> Cory
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Aug 28, 2015 at 7:23 AM, Taylor Downs < downs.taylor@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Thanks, Cory! Much appreciated.
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, 27 Aug 2015 at 08:16 Taylor Downs < downs.taylor@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hey team, we're configuring a re-usable, open-source CommCare
>>>>>>>>>>>>> to anything* integration (Ile Eftimov mentioned this on another
>>>>>>>>>>>>> thread—excited to release it to your community!) and it would be wonderful
>>>>>>>>>>>>> if we could set up data forwarding for forms and cases in JSON, rather than
>>>>>>>>>>>>> XML. Is this supported currently (sorry if I've missed it) or is it in
>>>>>>>>>>>>> development?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Have had great success with the "publish to JSON" feature on
>>>>>>>>>>>>> ODK Aggregate. Hoping for something like that. This is where I'm looking
>>>>>>>>>>>>> now:
>>>>>>>>>>>>> https://confluence.dimagi.com/pages/viewpage.action?pageId=12224128
>>>>>>>>>>>>>
>>>>>>>>>>>>> Taylor
>>>>>>>>>>>>>
>>>>>>>>>>>>> *The first destination use-case is Salesforce.com
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>>
>>>>>>>>>>>>> ---
>>>>>>>>>>>>> You received this message because you are subscribed to a
>>>>>>>>>>>>> topic in the Google Groups "CommCare Developers" group.
>>>>>>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>>>>>>> https://groups.google.com/d/topic/commcare-developers/bbhjuLWyJnA/unsubscribe
>>>>>>>>>>>>> .
>>>>>>>>>>>>> To unsubscribe from this group and all its topics, send an
>>>>>>>>>>>>> email to commcare-developers+unsubscribe@googlegroups.com.
>>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>>
>>>>>>>>>>>> ---
>>>>>>>>>>>> You received this message because you are subscribed to the
>>>>>>>>>>>> Google Groups "CommCare Developers" group.
>>>>>>>>>>>> To unsubscribe from this group and stop receiving emails from
>>>>>>>>>>>> it, send an email to
>>>>>>>>>>>> commcare-developers+unsubscribe@googlegroups.com.
>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>>
>>>>>>>>>>> ---
>>>>>>>>>>> You received this message because you are subscribed to a topic
>>>>>>>>>>> in the Google Groups "CommCare Developers" group.
>>>>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>>>>> https://groups.google.com/d/topic/commcare-developers/bbhjuLWyJnA/unsubscribe
>>>>>>>>>>> .
>>>>>>>>>>> To unsubscribe from this group and all its topics, send an email
>>>>>>>>>>> to commcare-developers+unsubscribe@googlegroups.com.
>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> ---
>>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>>> Groups "CommCare Developers" group.
>>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>>> send an email to commcare-developers+unsubscribe@googlegroups.com.
>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Simon Kelly
>>>>>>>> Senior Engineer | Dimagi South Africa
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> ---
>>>>>>>> You received this message because you are subscribed to a topic in
>>>>>>>> the Google Groups "CommCare Developers" group.
>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>> https://groups.google.com/d/topic/commcare-developers/bbhjuLWyJnA/unsubscribe
>>>>>>>> .
>>>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>>>> commcare-developers+unsubscribe@googlegroups.com.
>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> ---
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "CommCare Developers" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>> send an email to commcare-developers+unsubscribe@googlegroups.com.
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Simon Kelly
>>>>>> Senior Engineer | Dimagi South Africa
>>>>>>
>>>>>> --
>>>>>>
>>>>>> ---
>>>>>> You received this message because you are subscribed to a topic in
>>>>>> the Google Groups "CommCare Developers" group.
>>>>>> To unsubscribe from this topic, visit
>>>>>> https://groups.google.com/d/topic/commcare-developers/bbhjuLWyJnA/unsubscribe
>>>>>> .
>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>> commcare-developers+unsubscribe@googlegroups.com.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>> --
>>>>
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "CommCare Developers" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to commcare-developers+unsubscribe@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Simon Kelly
>>> Senior Engineer | Dimagi South Africa
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "CommCare Developers" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/commcare-developers/bbhjuLWyJnA/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to
>>> commcare-developers+unsubscribe@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
Hi everyone, this problem has come back! It's in a production instance with about 60 submissions a day and has been serving up xml instead of JSON for the last two days. Can't get in touch with the support email id.
Would it be possible to speak to someone today? It would make all the difference in the world to be able to see whether the forwarding rule is set to xml or JSON, because the bug seems to be with the form post that creates the rule. Sometimes it gives xml, sometimes JSON no matter whether I select JSON or xml in the setup.
We got the ticket, but our team is a bit under-capacity post holidays and
we didn't get a chance to look into it yet. Someone will follow up there as
soon as we can (Monday at the latest).
thanks,
Cory
···
On Sat, Jan 9, 2016 at 10:33 AM, Taylor Downs wrote:
Hi everyone, this problem has come back! It's in a production instance
with about 60 submissions a day and has been serving up xml instead of JSON
for the last two days. Can't get in touch with the support email id.
Would it be possible to speak to someone today? It would make all the
difference in the world to be able to see whether the forwarding rule is
set to xml or JSON, because the bug seems to be with the form post that
creates the rule. Sometimes it gives xml, sometimes JSON no matter whether
I select JSON or xml in the setup.
Excellent. Thank you. Glad to know it's been received. Whenever someone
picks it up please know that they're welcome to call me directly. I can
help them reproduce the bug.
Taylor
···
On Sat, Jan 9, 2016 at 12:26 PM Cory Zue wrote:
Hey Taylor,
We got the ticket, but our team is a bit under-capacity post holidays and
we didn't get a chance to look into it yet. Someone will follow up there as
soon as we can (Monday at the latest).
Hi everyone, this problem has come back! It's in a production instance
with about 60 submissions a day and has been serving up xml instead of JSON
for the last two days. Can't get in touch with the support email id.
Would it be possible to speak to someone today? It would make all the
difference in the world to be able to see whether the forwarding rule is
set to xml or JSON, because the bug seems to be with the form post that
creates the rule. Sometimes it gives xml, sometimes JSON no matter whether
I select JSON or xml in the setup.
I'm available on 202-406-0418 for another week.
Taylor
--
You received this message because you are subscribed to the Google Groups
"CommCare Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
Thanks for taking the time to offline a fix with me. We'll get that fix
deployed as soon as possible.
Ben
···
On Sat, Jan 9, 2016 at 2:06 PM, Taylor Downs wrote:
Excellent. Thank you. Glad to know it's been received. Whenever someone
picks it up please know that they're welcome to call me directly. I can
help them reproduce the bug.
Taylor
On Sat, Jan 9, 2016 at 12:26 PM Cory Zue czue@dimagi.com wrote:
Hey Taylor,
We got the ticket, but our team is a bit under-capacity post holidays and
we didn't get a chance to look into it yet. Someone will follow up there as
soon as we can (Monday at the latest).
Hi everyone, this problem has come back! It's in a production instance
with about 60 submissions a day and has been serving up xml instead of JSON
for the last two days. Can't get in touch with the support email id.
Would it be possible to speak to someone today? It would make all the
difference in the world to be able to see whether the forwarding rule is
set to xml or JSON, because the bug seems to be with the form post that
creates the rule. Sometimes it gives xml, sometimes JSON no matter whether
I select JSON or xml in the setup.
I'm available on 202-406-0418 for another week.
Taylor
--
You received this message because you are subscribed to the Google
Groups "CommCare Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an