Changes to Export Format

Hi Users,

This is just a heads up that we are hoping to deploy some minor
changes to the current excel/csv export format for forms in hopes of
making them slightly simpler (though the format could still be much
improved). The main changes are as follows:

  1. The table/sheet/file names used will all lose a leading “#.” (the
    root table would go from #.# to just #, and all other tables would
    change accordingly).
  2. The headings and IDs will be separated by the pipe character "|“
    instead of the dot. This is to prevent Excel from hiding IDs that say
    "1.0” and make them look like “1”. This will also affect column names.
    So for example, form.case.user_id would become form|case|user_id.
  3. ID’s will all lose the second digit (which was always “0”).

So the net result of steps 2 and 3 above would cause an ID like
"1.0.2" to turn to “1|2”.

This is all pretty small/obscure stuff that shouldn’t affect the
readability of the files, so this should only affect anyone who has
written something that automatically gets an export and parses it with
a computer program. If you are concerned that these changes might
break you, please let us know and we’ll work with you to get your
scripts migrated.

We will automatically migrate all custom exports to this new format as well.

thanks,
Cory

Hi Cory,

Do you have this new version available on a non-production server that I
can use to test some scripts?

Thanks,
Jon

··· On Wed, Feb 1, 2012 at 1:00 PM, Cory Zue wrote:

Hi Users,

This is just a heads up that we are hoping to deploy some minor
changes to the current excel/csv export format for forms in hopes of
making them slightly simpler (though the format could still be much
improved). The main changes are as follows:

  1. The table/sheet/file names used will all lose a leading “#.” (the
    root table would go from #.# to just #, and all other tables would
    change accordingly).
  2. The headings and IDs will be separated by the pipe character "|“
    instead of the dot. This is to prevent Excel from hiding IDs that say
    "1.0” and make them look like “1”. This will also affect column names.
    So for example, form.case.user_id would become form|case|user_id.
  3. ID’s will all lose the second digit (which was always “0”).

So the net result of steps 2 and 3 above would cause an ID like
"1.0.2" to turn to “1|2”.

This is all pretty small/obscure stuff that shouldn’t affect the
readability of the files, so this should only affect anyone who has
written something that automatically gets an export and parses it with
a computer program. If you are concerned that these changes might
break you, please let us know and we’ll work with you to get your
scripts migrated.

We will automatically migrate all custom exports to this new format as
well.

thanks,
Cory

Hi Cory,

Do you have this new version available on a non-production server that I can
use to test some scripts?

I’ll get it deployed to our staging server
(http://staging.commcarehq.org/) as soon as possible and let you know
when I do.

thanks,
Cory

··· 2012/2/1 Jonathan Payne :

Thanks,
Jon

On Wed, Feb 1, 2012 at 1:00 PM, Cory Zue czue@dimagi.com wrote:

Hi Users,

This is just a heads up that we are hoping to deploy some minor
changes to the current excel/csv export format for forms in hopes of
making them slightly simpler (though the format could still be much
improved). The main changes are as follows:

  1. The table/sheet/file names used will all lose a leading “#.” (the
    root table would go from #.# to just #, and all other tables would
    change accordingly).
  2. The headings and IDs will be separated by the pipe character "|“
    instead of the dot. This is to prevent Excel from hiding IDs that say
    "1.0” and make them look like “1”. This will also affect column names.
    So for example, form.case.user_id would become form|case|user_id.
  3. ID’s will all lose the second digit (which was always “0”).

So the net result of steps 2 and 3 above would cause an ID like
"1.0.2" to turn to “1|2”.

This is all pretty small/obscure stuff that shouldn’t affect the
readability of the files, so this should only affect anyone who has
written something that automatically gets an export and parses it with
a computer program. If you are concerned that these changes might
break you, please let us know and we’ll work with you to get your
scripts migrated.

We will automatically migrate all custom exports to this new format as
well.

thanks,
Cory

Hi Cory,

Do you have this new version available on a non-production server that I
can
use to test some scripts?

I’ll get it deployed to our staging server
(http://staging.commcarehq.org/) as soon as possible and let you know
when I do.

These updates are now live on the staging server, and we hope to be merging
them into production by the end of the week.

Let us know if you have any concerns.

thanks,
Cory

··· 2012/2/1 Cory Zue > 2012/2/1 Jonathan Payne :

thanks,
Cory

Thanks,
Jon

On Wed, Feb 1, 2012 at 1:00 PM, Cory Zue czue@dimagi.com wrote:

Hi Users,

This is just a heads up that we are hoping to deploy some minor
changes to the current excel/csv export format for forms in hopes of
making them slightly simpler (though the format could still be much
improved). The main changes are as follows:

  1. The table/sheet/file names used will all lose a leading “#.” (the
    root table would go from #.# to just #, and all other tables would
    change accordingly).
  2. The headings and IDs will be separated by the pipe character "|“
    instead of the dot. This is to prevent Excel from hiding IDs that say
    "1.0” and make them look like “1”. This will also affect column names.
    So for example, form.case.user_id would become form|case|user_id.
  3. ID’s will all lose the second digit (which was always “0”).

So the net result of steps 2 and 3 above would cause an ID like
"1.0.2" to turn to “1|2”.

This is all pretty small/obscure stuff that shouldn’t affect the
readability of the files, so this should only affect anyone who has
written something that automatically gets an export and parses it with
a computer program. If you are concerned that these changes might
break you, please let us know and we’ll work with you to get your
scripts migrated.

We will automatically migrate all custom exports to this new format as
well.

thanks,
Cory

These updates are now live on the staging server, and we hope to be
merging them into production by the end of the week.

These updates are now deployed. You’ll notice some small tweaks to the
export format, but otherwise everything should be working as before. Let us
know if you experience any problems!

thanks,
Cory

··· > > Let us know if you have any concerns. > > thanks, > Cory > > >> >> thanks, >> Cory >> >> > Thanks, >> > Jon >> > >> > On Wed, Feb 1, 2012 at 1:00 PM, Cory Zue wrote: >> >> >> >> Hi Users, >> >> >> >> This is just a heads up that we are hoping to deploy some minor >> >> changes to the current excel/csv export format for forms in hopes of >> >> making them slightly simpler (though the format could still be much >> >> improved). The main changes are as follows: >> >> >> >> 1. The table/sheet/file names used will all lose a leading "#." (the >> >> root table would go from #.# to just #, and all other tables would >> >> change accordingly). >> >> 2. The headings and IDs will be separated by the pipe character "|" >> >> instead of the dot. This is to prevent Excel from hiding IDs that say >> >> "1.0" and make them look like "1". This will also affect column names. >> >> So for example, form.case.user_id would become form|case|user_id. >> >> 3. ID's will all lose the second digit (which was always "0"). >> >> >> >> So the net result of steps 2 and 3 above would cause an ID like >> >> "1.0.2" to turn to "1|2". >> >> >> >> This is all pretty small/obscure stuff that shouldn't affect the >> >> readability of the files, so this should only affect anyone who has >> >> written something that automatically gets an export and parses it with >> >> a computer program. If you are concerned that these changes might >> >> break you, please let us know and we'll work with you to get your >> >> scripts migrated. >> >> >> >> We will automatically migrate all custom exports to this new format as >> >> well. >> >> >> >> thanks, >> >> Cory >> > >> > >> > >