Skip to main content

HI!

I have an issue with displaying the data in a cell. We created a report in DevExpress and want to make it displayable in an excel sheet. All data is shown correctly in every cell. However in one cell the data is cut off and not all data is visible.

The cell has the options 'Can shrink', 'Can grow', 'Multiline' and 'Word Wrap' enabled.

What can I do to ensure that the entire text is visible?

Attached are printscreens of the report.

Kind regards,

Linde

 




 

 

Hi Linde,

Not sure how you exactly export the report to Excel. Is that through the Thinkwise platform with the Export to Excel report action?

I'm afraid few members here on the Community have experience with this exact issue. It could very well be that we have no control over the field height and that Excel decides to cut the height how it pleases. 

The domain used is using a varchar(max) or something else? 


I'd like to add to this topic with a few questions about DevExpress within Thinkwise instead of opening a  new one:

  1. Is there an internal document or guide that Thinkwise uses for DevExpress best practices?
    Something that handles more things than just the ‘standard’ stuff. This could include topics like:
    • Designing reports with multi-column layouts
    • Tricks with calculated expressions
    • Handling changes in sub-reports, especially with Indicium caching
    • Advanced tips and tricks for enhancing designs

If such a document exists, could it be shared or added as a dedicated DevExpress page in the Thinkwise documentation?

  1. Which version of DevExpress is currently available to us? The Indicium product update blog mentions version 23.2.5, but when I try to find the change log on the website, I'm presented with different version options.
     

     

  2. How do you navigate the DevExpress forum effectively? Many topics are outdated (some up to 15 years old), making the suggested solutions less relevant, useless even. Additionally, a lot of the C# code solutions contain inconsistencies and use outdated libraries. What's the best approach to deal with this?

Love to hear more about this.

With love, and (more than) a bit of frustration,

Thanks!


  

I'd like to add to this topic with a few questions about DevExpress within Thinkwise instead of opening a  new one:

  1. Is there an internal document or guide that Thinkwise uses for DevExpress best practic...

I’d like to see official subreport support too, since the current workaround via Indicium is not something I’d like to use since it’s horrible to maintain. 😅


  

I'd like to add to this topic with a few questions about DevExpress within Thinkwise instead of opening a  new one:

  1. Is there an internal document or guide that Thinkwise uses for DevExpress best practic...

I’d like to see official subreport support too, since the current workaround via Indicium is not something I’d like to use since it’s horrible to maintain. 😅

I actually started to play a bit with DevExpress reporting..  it's indeed a little puzzle. However you can probably work your way around sub reports using multiple detail report bands, I was able to create a report that basically consists out of 3 sub reports in this way. 


Hey @Linde van Dyck, did any reply here helped out?


I'd like to add to this topic with a few questions about DevExpress within Thinkwise instead of opening a  new one:

  1. Is there an internal document or guide that Thinkwise uses for DevExpress best practices?
    Something that handles more things than just the ‘standard’ stuff. This could include topics like:
    • Designing reports with multi-column layouts
    • Tricks with calculated expressions
    • Handling changes in sub-reports, especially with Indicium caching
    • Advanced tips and tricks for enhancing designs

If such a document exists, could it be shared or added as a dedicated DevExpress page in the Thinkwise documentation?

  1. Which version of DevExpress is currently available to us? The Indicium product update blog mentions version 23.2.5, but when I try to find the change log on the website, I'm presented with different version options.
     

     

  2. How do you navigate the DevExpress forum effectively? Many topics are outdated (some up to 15 years old), making the suggested solutions less relevant, useless even. Additionally, a lot of the C# code solutions contain inconsistencies and use outdated libraries. What's the best approach to deal with this?

Love to hear more about this.

With love, and (more than) a bit of frustration,

Thanks!

 

Can anyone please answer this?


Is there an internal document or guide that Thinkwise uses for DevExpress best practices?

Not that I'm aware of. I would have to turn to the Community members for this one.

 

Which version of DevExpress is currently available to us?

For reporting, as of 2024.1.14.3, Indicium, Windows GUI and report designer use DevExpress version 23.2

 

How do you navigate the DevExpress forum effectively?

I would expect the search bar to be the best way to effectively search. Topics being outdated makes it indeed difficult to find any solutions that may still work. Personally I have little experience with their forum.


@Linde van Dyck, were you able to resolve the original problem at hand? If so, please select the reply that resolved it or provide what you did to resolve it 😁


Hi @Mark Jongeling 

The problem arises because of the maximum column values in excel. In Devexpress it is quite readable, however when you export to excel it is unavoidable that the data is cut off. By making the columns extra wide, you ensure that as much data as possible gets in. However, in terms of user friendliness, this is anything but optimal. 

Is this something that can be improved in the DevExpress version of Thinkwise?

 


Hi Linde,

We are unable to change anything that affects the export. The export is fully done by DexExpress itself and we have no control over the exported file. All data is sent in it's entirety to the DexExpress module, after that DevExpress is responsible for exporting the report to a file.


Hi Mark,

That's a shame, this makes it hard to develop a user friendly report. 

This ticket can be closed