web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / Quick Query losing row...
Microsoft Dynamics SL (Archived)

Quick Query losing rows when exported

(0) ShareShare
ReportReport
Posted on by Community Member

When exporting quick queries, sometimes rows are lost.

Example: When running Journal Transactions QQ and filtering

Journal type is GJ

Account greater than and includes 5000

period to post is 201604

the query results in 1145 rows.  When exported to excel, there are only 839 rows.  It also appears that one row's columns are off.  (date in the batch # column)

They are using SL2011 FP1.  Any suggestions?

*This post is locked for comments

I have the same question (0)
  • Erich Strelow F Profile Picture
    Erich Strelow F 16 on at

    This is pretty odd. I'll give you some tips, but more information is needed in order to discard some issues.

    • Check weather you have Quick Quiery on "Paging mode". You would see additional reverse and forward buttons in the toolbar to move between pages. This feature was introduced in SL2011 FP1 and is described in the ReleaseNotes2011SP1.pdf doc. Beware that this feature is provided on a DIY basis. If you turn Paging on in your solomon.ini, you are supposed to also populate a lot of metadata yourself by using sp_dropextendedproperty calls. If you don't setup the proper metadata, one symptom are indeed incomplete excel exports. Still, 1145 rows are too few for this to trigger.
    • Check your qqvie00.exe version info. There are some hotfixes published.
    • Check on any character map issues. Some versions of qqvie00.exe might malfunction if columns headers or filters has wide characters. If your SL version is native English based, then this tip is meaningless.
    • Quick Query does have a hide/show column feature that might get messed. In theory you could restore it to factory settings, but a direct sql sentence is required.
    • Beware that many qq options are user-based customizable. That includes private versions of solomon.ini, private filter settings and hide/show columns.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans