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

Community site session details

Session Id :

Quick Query integration with customization Manager in Dynamics SL

Ram Peru Profile Picture Ram Peru 2,830

I got one forum Question about the launching of Quick Query from standard screen customization during the button click event like custom report printing. I haven’t tried this before.

I just thought of using launch function to launch the Quick Query from standard screen. It’s working perfectly when launching the Quick Query Viewer using the launch functionality from standard screen. But one of forum mate has raised another scenario. The scenario is, if the customer wants to view the specific customized Quick Query directly from button click.

For better understanding,

If the customer customized & stored the Inventory Transaction – Quick query based on the Issues and Receipts & Tran Type. Now user wants to open the Inventory Transaction Quick Query for the Receipts. How can we handle this scenario on standard screen customization?

Please follow the below steps to call the Specific Quick Query from the standard customization.

For instance I am taking the Voucher & Adjustment Entry screen to explain this Quick Query Integration with customization manager.

  1. Open the Voucher & Adjustment Entry screen and Press (Ctrl + Alt + C) to initiate the customize mode.
  2. Press F6 to open up the insert object wizard (91.252.00) and add the button control from unbound control.
  3. Select the button which you added and press F7 to open the Visual Basic Editor.
  4. Add the below code in Button click event.

Dim ParmStr$

ParmStr = “QQVIE00.EXE ” + PRMSEP + “QQ_Apdoc”

serr1 = Launch(ParmStr, True, True, 0)

You can found the Quick Query view name in the QVCatalog table. This table is available in the system database.

This blog post explains about  launching the Quick Query from the standard screen itself.


This was originally posted here.

Comments

*This post is locked for comments