Skip to main content

When field order is set, column names in Excel output do not match correct column values

Justin Kraemer
I'm using GVH 2.8.1 with GE 4.6.3 and having trouble with Excel exports from query results.

 

In the output XLSX file each column heading has the wrong data values under it.

 

The field display order is set in GE Manager.

 

But in Manager when I click Reset to Default in Sort Fields, and then save the site, reload the viewer, perform another query and then export to Excel, all columns and their headings line up as they should. Have I found a bug? I need control over the display order of fields, and as things stand, the only way to have proper Excel exports is to leave the default display order intact. Has anyone else found this, and know of a solution?

 

Thanks in advance for any consideration,

 

Justin
0

Comments

7 comments

Date Votes
  • Permanently deleted user
    I tried changing field order then exporting to excel, using 2.6.1 and 2.9.2 viewers (4.5.1 and 4.8.2 backends) and they both exported the data in the correct order with the correct headings.

     

    Does this happen with any field or just fields of a certain data type?  Is the data in the default order but headers in selected order or vice-versa?

     

    Peter
    0
  • Justin Kraemer

    Thanks for your reply, Peter. In the excel file, the data columns are in the default order, but the headers are in my desired order. 

    Since my initial post, I have tried specifying the desired order in the MXD and republishing, but this made no difference. I fear the solution is to recreate the feature class by specifying schema with the proper column order, load the existing feature class into it, and then republishing the service with the new feature class in the MXD. I am highly reluctant to do that, though, so am keen for an easier answer.

     

    But one more thing: I noticed today the attribute domain is missing from one of the fields when I view it in ArcMap layer properties Fields tab. But in the viewer when editing a road sign, the dropdown list works for that field as it should. Very strange, I think! Maybe this points to the need for a new feature class?
    0
  • Permanently deleted user
    I have this same issue.  It seems like a bug.  Kinda frustrating because it makes the Sort Fields control useless.
    0
  • Justin Kraemer
    I hear you Krystal. For yours and others' interest, I had opened a support case on this that was picked up by Esri Canada. Result is this has been submitted as bug ID: GE-9273 and it has been moved over to Latitude QA/Development to take over for further review.  Unfortunately they don't have any workarounds to offer at this time, and they are not sure when any updates might be available, but moving forward if you are looking for updates you can contact Esri Canada Support referencing the bug ID and they will provide you with the latest.

     

    My plan is to create a new feature class with the fields in the display order, but given this feature class is used by a field crew, I'm not rushing to do that given it might be resolved before next field season.

     

     
    0
  • Permanently deleted user
    I have the same issue. Hope there will be a solution soon. But for now I will probably create a new feature class and set the order of all fields the way I need. 

     

     
    0
  • Permanently deleted user
    That is shocking... hopefully users catch any errors before using the data....
    0
  • Justin Kraemer
    If any consolation, the Export to CSV gets around this mismatch. I might remove Export to XLSX from the list.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post