Styling the data in desired way for doc format

Created on 14 May 2015, almost 10 years ago
Updated 6 December 2024, 5 months ago

Hi All,

I recently started using this module for doc export for the first time. This is good to export the view in doc format if the view has very limited columns. But what if there are a lot of columns? The last columns will not be displayed. :(

So could someone please help me how to get this fixed. There should be an option to export it in landscape mode rather than portrait mode. But I think that will also support to some extent only(for limited number of columns). So it will be better if we are provided with an option to export the view to doc in row format rather than in column format. I mean the same export which is happening vertically should be done horizontally. So an option in the UI level with 2 radio buttons 1. Horizontal and 2. Vertical would be a great help for people like me who are having a lot of columns to export in doc format.

Not only doc format, it would be better to give this option to other formats wherever it is applicable.

Also an option to remove the empty columns will also help to reduce the number of columns to be exported.

Thanks in advance
Manoj

✨ Feature request
Status

Closed: won't fix

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States manoj.surala

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡¬πŸ‡§United Kingdom steven jones

    Sorry for the lack of attention to your issue, please accept my apologies.

    Drupal 7 is going to be end-of-life'd by the community in approximately 1 month. β†’

    As such, I am closing all non-critical looking, non-PHP compatibility issues for Views Data Export to tidy up the issue queues and reduce the noise. You can read about this on πŸ“Œ Close down Drupal 7 issues Active .

    If you feel like this issue has been closed by mistake, please do comment about re-opening it.
    If you feel like the ticket is still relevant for the 8.x-1.x version of the module, then please search for a duplicate issue first, and if there really isn't one (and you've looked properly) then change the version on the ticket and re-open.

    Thanks to everyone involved in this issue: for reporting it, and moving it along, it is truly appreciated.
    The Drupal community wouldn't be what it is today without your involvement and effort, so I'm sorry that we couldn't get this issue resolved. Hopefully we'll work together in a future issue though, and get that one resolved :)

Production build 0.71.5 2024