Table column ordering depends on document field arrangement

[GoogleCodeExporter]

What steps will reproduce the problem?

  1. Create a format and create a new record.
  2. Use the developer API form code snippet to create a new form with the same fields, but reorder them and submit a new record.
  3. The new records values will show up in submission order, and so not under the correct column header or in line with previous records.

What is the expected output? What do you see instead?

  The ordering of submitted fields should be ignored, and the WYSIWYG form ordering from the format's page should be used instead.

Original issue reported on code.google.com by p...@google.com on 25 Jun 2010 at 12:09

[GoogleCodeExporter]

Changing this a bit.  It was actually a dependency on document field ordering.  
So now the format is used for ordering and the miscellaneous ordering is fixed. 
 Also, missing values are now supported as a result.  You submit a bug, you get 
it fixed and a feature for free!

One new issue though.  The way GViz API works, the ordering of the table for 
charts has meaning, so for maps the lat/lng columns have to be first.  To 
conserve some time, I also use that mapping for the data table view.  So 
leaving this open as a reminder to decouple that.

Original comment by p...@google.com on 25 Jun 2010 at 4:04

• Changed title: Table column ordering depends on document field arrangement