The easiest way to figure out what values to use are by inspecting the APIs
that the export tool uses. For case data you should look at the JSON format
of the case API https://confluence.dimagi.com/pages/viewpage.action?pageId=12224287,
which should make it clear how to reference any available properties.
row/number is not available as that is a unique construct to the built-in
exports.
Cory
···
On Sun, Oct 23, 2016 at 5:40 AM, Gurudayal Sahu wrote:
Hi,
I am trying to export the date from Commcarehq to the Ms-SQL server
through the Data Export API(https://confluence.dimagi.
com/display/commcarepublic/CommCare+Data+Export+Tool) ,and it is getting
exported successfully for all the defined columns except with the below
system generated column names (appearing under properties) :
I tried to define the above column name as similar name in the source
filed even tried to add as "info." and "properties.info.", but still not able to get any data after exporting into the SQL
server against the above column names.
Kindly suggest for the correct format for the above listed column names,
that should be defined in the source field in the configuration file (being
referred during the data export).
So looking for your suggestion for the applicable format for the above
column names that can be tried with.
Thanks once again.
With regards,
Gurudayal Sahu
···
On Mon, Oct 24, 2016 at 12:18 AM, Cory Zue wrote:
Hey Gurudayal,
The easiest way to figure out what values to use are by inspecting the
APIs that the export tool uses. For case data you should look at the JSON
format of the case API https://confluence.dimagi.com/pages/viewpage.action?pageId=12224287,
which should make it clear how to reference any available properties.
row/number is not available as that is a unique construct to the built-in
exports.
I am trying to export the date from Commcarehq to the Ms-SQL server
through the Data Export API(https://confluence.dimagi.
com/display/commcarepublic/CommCare+Data+Export+Tool) ,and it is getting
exported successfully for all the defined columns except with the below
system generated column names (appearing under properties) :
I tried to define the above column name as similar name in the source
filed even tried to add as "info." and "properties.info.", but still not able to get any data after exporting into the SQL
server against the above column names.
Kindly suggest for the correct format for the above listed column names,
that should be defined in the source field in the configuration file (being
referred during the data export).
So looking for your suggestion for the applicable format for the above
column names that can be tried with.
Thanks once again.
With regards,
Gurudayal Sahu
On Mon, Oct 24, 2016 at 12:18 AM, Cory Zue czue@dimagi.com wrote:
Hey Gurudayal,
The easiest way to figure out what values to use are by inspecting the
APIs that the export tool uses. For case data you should look at the JSON
format of the case API https://confluence.dimagi.com/pages/viewpage.action?pageId=12224287,
which should make it clear how to reference any available properties.
row/number is not available as that is a unique construct to the built-in
exports.
I am trying to export the date from Commcarehq to the Ms-SQL server
through the Data Export API(https://confluence.dimagi.
com/display/commcarepublic/CommCare+Data+Export+Tool) ,and it is
getting exported successfully for all the defined columns except with the
below system generated column names (appearing under properties) :
I tried to define the above column name as similar name in the source
filed even tried to add as "info." and "properties.info.", but still not able to get any data after exporting into the SQL
server against the above column names.
Kindly suggest for the correct format for the above listed column
names, that should be defined in the source field in the configuration file
(being referred during the data export).
So looking for your suggestion for the applicable format for the above
column names that can be tried with.
Thanks once again.
With regards,
Gurudayal Sahu
On Mon, Oct 24, 2016 at 12:18 AM, Cory Zue czue@dimagi.com wrote:
Hey Gurudayal,
The easiest way to figure out what values to use are by inspecting the
APIs that the export tool uses. For case data you should look at the JSON
format of the case API https://confluence.dimagi.com/pages/viewpage.action?pageId=12224287,
which should make it clear how to reference any available properties.
row/number is not available as that is a unique construct to the
built-in exports.
I am trying to export the date from Commcarehq to the Ms-SQL server
through the Data Export API(https://confluence.dimagi.
com/display/commcarepublic/CommCare+Data+Export+Tool) ,and it is
getting exported successfully for all the defined columns except with the
below system generated column names (appearing under properties) :
I tried to define the above column name as similar name in the source
filed even tried to add as "info." and "properties.info.", but still not able to get any data after exporting into the SQL
server against the above column names.
Kindly suggest for the correct format for the above listed column
names, that should be defined in the source field in the configuration file
(being referred during the data export).
I'm not sure what to try next if none of those are working. If you have any
other error information or traces that might trigger something but
otherwise I'm afraid I'm out of ideas. My next guess would be something to
do with date typing/parsing, but that's just a shot in the dark.
···
On Mon, Oct 24, 2016 at 2:20 PM, Gurudayal Sahu wrote:
Dear Cory,
Thanks for your continuous support !
I tried the below combinations with all the above columns.
*properties.*date_opened
date_opened (no prefix)
*properties.info http://properties.info.*date_opened
But still continuing with the same issue.
With regards,
Gurudayal Sahu
On Mon, Oct 24, 2016 at 5:48 PM, Cory Zue czue@dimagi.com wrote:
Hi Gurudayal,
Did you try using:
properties/date_opened
closed (no prefix)
date_closed (no prefix)
looking at the API format this is what I would expect to work for those
three.
So looking for your suggestion for the applicable format for the above
column names that can be tried with.
Thanks once again.
With regards,
Gurudayal Sahu
On Mon, Oct 24, 2016 at 12:18 AM, Cory Zue czue@dimagi.com wrote:
Hey Gurudayal,
The easiest way to figure out what values to use are by inspecting the
APIs that the export tool uses. For case data you should look at the JSON
format of the case API https://confluence.dimagi.com/pages/viewpage.action?pageId=12224287,
which should make it clear how to reference any available properties.
row/number is not available as that is a unique construct to the
built-in exports.
I am trying to export the date from Commcarehq to the Ms-SQL server
through the Data Export API(https://confluence.dimagi.
com/display/commcarepublic/CommCare+Data+Export+Tool) ,and it is
getting exported successfully for all the defined columns except with the
below system generated column names (appearing under properties) :
I tried to define the above column name as similar name in the source
filed even tried to add as "info." and "properties.info.", but still not able to get any data after exporting into the SQL
server against the above column names.
Kindly suggest for the correct format for the above listed column
names, that should be defined in the source field in the configuration file
(being referred during the data export).