Sorting/Filtering on New Report Wizard doesn't work

jkoo · Post by **jkoo** » Wed Apr 25, 2012 1:08 pm

When I add Sorting/Filtering on New Report Wizard dialog,
Sort/Filter is not saved. It shows "No Filters" and "Sort by undefined" as property grid.
And the preview throws an error.

And If I select one of default themes on Report Wizard Dailog, report doesn't work and the preview displays error.

Thanks

Post by **HighAley** » Thu Apr 26, 2012 9:14 am

Hello.

jkoo wrote:When I add Sorting/Filtering on New Report Wizard dialog,
Sort/Filter is not saved. It shows "No Filters" and "Sort by undefined" as property grid.
And the preview throws an error.

And If I select one of default themes on Report Wizard Dailog, report doesn't work and the preview displays error.

We've fixed problem with Sorting. You could check our next prerelease build in a few days.

The problem with filtering will be fixed next week.

Thank you.

jkoo · Post by **jkoo** » Fri May 04, 2012 1:25 pm

I tried a prelease version. It had another issue.
Report wizard does nothing. It doesn't create any control.
So cannot verify sorting/filtering issue.

Post by **Vladimir** » Tue May 08, 2012 4:08 am

Hello,

Sorry for the inconvenience, please see the updated designer's library in the attached archive. If you are a registered user and you need the full version immediately, please send a request to support[at]stimulsoft.com

Thank you.

jkoo · Post by **jkoo** » Tue May 08, 2012 12:58 pm

I need it immediately. I'm a registered user.
So I've just sent a request for that.

Thanks

jkoo · Post by **jkoo** » Tue May 08, 2012 6:46 pm

I'm happy I've just got the full version. Thanks a lot for quick response.
Most of issues were resolved.
But an issue with theme on Report Wizard Dailog is not fixed yet.
That is, If I select a default theme such as 'Red 100%',
I got the below error message on viewing preview

Unable to cast object of type 'System.String' to type 'Stimulsoft.Report.StiStyleCondition'.

Post by **Vladimir** » Thu May 10, 2012 7:12 am

Hello,

We have fixed this error. Please check your email for update.

Thank you.