Hi
If I apply a Top summary as a percentage to a Pivot Grid in Server Mode it doesn't work correctly in that it always treats the top as a value rather than a percentage.
For example applying a top 50% generates sql that starts SELECT TOP (50) rather than SELECT TOP (50) PERCENT
Many Thanks
Pete
We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.
Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.
HI
I need to re-open this ticket as I don't believe the fix is working correctly.
For example we had a grid with only two rows. First we selected top 50% and it showed the 1 row. However, select top 10% selected both rows.
Also, on the record set we are currently running with that has over a million rows, the methodology you are implementing where your query builds a list of values for the top x% and then executes more queries providing that list as an 'in' list we get the following error: "The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information."
Many Thanks
Pete
Thanks for the additional information. I am afraid this might take some additional time to research the problem.
We will update this thread once I have any results. Thanks for your patience.
We have researched the issue, but have not found a suitable solution to either of the problems. We will require additional time to process each of them. To process each issue more efficiently, I have registered two separate bug reports regarding each of them.
Please refer to these reports for further correspondence on these items. We will update the threads once we have any results.
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Hi Pete,
We do not have an immediate answer. I have passed this ticket to our team for an additional researching.
I have managed to reproduce the described problem on my side. It will require some time to research it in greater detail. I have passed this issue to our developers for further research. We will update the thread once we have any results.
John
Any news on this as yet? If not is there a workaround I can apply myself?
Many Thanks
Pete
Hello Pete,
Although I cannot provide you with a precise time frame when this issue will be solved, I can say that we are keenly aware of just how needed it is. In fact, once we have any news, you will be automatically notified. We greatly appreciate your patience.
Maxim
Any news?
Pete