{"action":"created","issue":{"url":"https://api.github.com/repos/bmihelac/django-import-export/issues/210","labels_url":"https://api.github.com/repos/bmihelac/django-import-export/issues/210/labels{/name}","comments_url":"https://api.github.com/repos/bmihelac/django-import-export/issues/210/comments","events_url":"https://api.github.com/repos/bmihelac/django-import-export/issues/210/events","html_url":"https://github.com/bmihelac/django-import-export/issues/210","id":58044183,"number":210,"title":"Export order","user":{"login":"jeberger","id":930717,"avatar_url":"https://avatars.githubusercontent.com/u/930717?v=3","gravatar_id":"","url":"https://api.github.com/users/jeberger","html_url":"https://github.com/jeberger","followers_url":"https://api.github.com/users/jeberger/followers","following_url":"https://api.github.com/users/jeberger/following{/other_user}","gists_url":"https://api.github.com/users/jeberger/gists{/gist_id}","starred_url":"https://api.github.com/users/jeberger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeberger/subscriptions","organizations_url":"https://api.github.com/users/jeberger/orgs","repos_url":"https://api.github.com/users/jeberger/repos","events_url":"https://api.github.com/users/jeberger/events{/privacy}","received_events_url":"https://api.github.com/users/jeberger/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-02-18T09:24:03Z","updated_at":"2015-04-16T08:56:49Z","closed_at":"2015-02-24T08:31:38Z","body":"Is there a way to specify a partial export order ? For example, I'd like to specify that the first two columns should be \"id\" and \"name\", then I'd like to have all remaining fields in whatever order.\r\n\r\nCurrently I have two options: \r\n - Specify `export_order` in the resource's meta object, but any field that is not listed will not be included;\r\n - Not specify `export_order` in which case the export starts with the fields declared explicitly in the resource in no particular order followed by introspected fields in the order they were declared in the model.\r\n\r\nIdeally, what I would like is to have introspected fields first in order of declaration, then explicit fields. Since other applications may have different requirements, I would be happy with specifying a couple of fields explicitly in `export_order` so that those fields will come first and in the specified order, then have any remaining fields come after in no particular order."},"comment":{"url":"https://api.github.com/repos/bmihelac/django-import-export/issues/comments/93682758","html_url":"https://github.com/bmihelac/django-import-export/issues/210#issuecomment-93682758","issue_url":"https://api.github.com/repos/bmihelac/django-import-export/issues/210","id":93682758,"user":{"login":"rhunwicks","id":1317567,"avatar_url":"https://avatars.githubusercontent.com/u/1317567?v=3","gravatar_id":"","url":"https://api.github.com/users/rhunwicks","html_url":"https://github.com/rhunwicks","followers_url":"https://api.github.com/users/rhunwicks/followers","following_url":"https://api.github.com/users/rhunwicks/following{/other_user}","gists_url":"https://api.github.com/users/rhunwicks/gists{/gist_id}","starred_url":"https://api.github.com/users/rhunwicks/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rhunwicks/subscriptions","organizations_url":"https://api.github.com/users/rhunwicks/orgs","repos_url":"https://api.github.com/users/rhunwicks/repos","events_url":"https://api.github.com/users/rhunwicks/events{/privacy}","received_events_url":"https://api.github.com/users/rhunwicks/received_events","type":"User","site_admin":false},"created_at":"2015-04-16T08:56:49Z","updated_at":"2015-04-16T08:56:49Z","body":"I agree, which I think means that we need to change `get_fields()` so it's not based on `get_export_order()`.\r\n\r\nI wonder if many people have relied on `export_order` to control what fields get included, because that's how it worked. I know that's what I was doing - it seemed more DRY than creating both `fields` and `export_order`.\r\n\r\nI think that even from the point of view of exporting, we should probably implement Option 1. I can't see why you would want a field in the export twice, once with its Field name and once with its own Attribute name, which is I think what must be happening now."}}