Query Builder Basics: Preventing issues with Query Builder
Building queries in Microsoft Dynamics 365 Business Central (Business Central) with the Query Builder is straightforward, but knowing a few best practices helps you avoid the most common pitfalls. This article answers the most common setup and execution questions and shares best practices for getting dependable results.
Configure your connectors correctly
Setting up Query Builder starts with making sure your connectors are configured correctly in Popdock — that’s what allows you to publish and create lists and embedded widgets smoothly.
The key is the connection parameters, specifically the Publish company. This section of the connector settings uses the database name for the company rather than the display name. You can find the correct name for your company by following the steps in this guide on finding your company information in Business Central.
Once you have the correct name, you can check that it is set correctly for the Publish company in Popdock by following these steps:
1. From the main menu, select Connectors.
2. Find your sandbox connector and then click the Edit button.
3. Click Edit settings and verify the name in the Publish company field.
To keep everything running smoothly, follow these best practices when configuring your connectors:
| Best practice | Why it helps |
| Publish to production by pulling from the sandbox first. | Business Central is designed to publish to production through the sandbox, so this ensures your publish completes successfully. |
| Use a single connector per environment. | Keeping one connector per environment avoids conflicting extensions and keeps all your Query Builder lists working reliably. |
Always publish everything
When publishing your Query Builder lists to your sandbox, select Select all before publishing. This one step keeps every list and embedded widget intact and is the best way to protect your work.
This matters because publishing only includes the items you check. Any Query Builder list or embedded widget left unchecked is removed from the extension, and its entity ID is deleted. If you republish those items later, they receive a new entity ID rather than the original — so any custom work built on top of them will break and need to be rebuilt. Because Query Builder in Popdock has no backup system, selecting everything up front is what keeps your queries, widgets, and downstream work safe.
Choose Select all each time you publish your sandbox queries and widgets, and everything stays connected and intact.
Publish from the correct sandbox
Query Builder includes several safeguards to help you publish to production confidently, and following a few simple practices keeps everything working as expected. The most important: always publish from the correct sandbox. Publishing the wrong one to production will break any custom lists that rely on a Query Builder list and recovering means publishing the correct sandbox to production and then rebuilding those custom lists.
The easiest way to stay on track is to keep just one sandbox connector in your Popdock account. Query Builder runs on a one-to-one system, so a single sandbox connector is all you need. If you do need a second one for any reason, set the Is sandbox dropdown to False. This keeps it out of the publish dropdown entirely.
Popdock also gives you a built-in checkpoint before publishing to production. Before the publish runs, a menu displays all the changes that will be made. If you see that your Query Builder lists would be deleted, cancel the publish and confirm you are publishing from the correct sandbox. A quick double-check of your source sandbox will keep your production custom lists safe and intact.
If you have any questions about how to address issues with Query Builder, please reach out to support@eonesolutions.com. Our team will be happy to assist.
