Have you ever been walking through a process in Business Central, and realize you want to debug, but don’t want to wait to publish, and get back to the exact spot where you were testing something? Or for some reason you were debugging something, and the debugger stopped, and you want to jump right back in to the process you were examining. This is where “Attach Debugger to this session” comes in handy,
Guess what day it is?! 🐫 Time for some more #HumpDayHacks, brought to you in part by Copilot.
If you are working in Business Central version 24, you may have accidently clicked the Copilot button instead of the Search 🔎 If you are really set on using the Search button, you can use the shortcut ALT + Q (and skip inadvertently opening Copilot). You can actually use the hotkey of ALT throughout Business Central to quickly navigate with your keyboard.
Copilot inside Business Central doesn’t have a hotkey (yet…) but it is available in US BC24 environments with at no additional cost. You can check if it’s enabled in your environment by searching for Copilot & AI capabilities.
I decided it’s time to start sharing some #HumpDayHacks 🐫 to help get you through working with Business Central.
First up, some Microsoft Dynamics 365 Business Central hacks when working with the Page Inspection tool. You can open it with Ctrl + Alt + F1, or by clicking ❓ Help > Help & Support (at the bottom) >Under Troubleshooting click Inspect Pages and data.
The Page Inspection tool is a cornucopia of information. What objects are you interacting with (be it a page, report, query, XMLPort, etc). You can see the underlying table, and even click “View Table” 🔍 to see the data in the table. More information right at your fingertips are the extensions you are interacting with, the underlying fields and datatypes
Now pay attention: 🤓 If you click on a field, if the field is on the page, it will locate it for you, and take you to it. Much faster than opening VSCode and trying to determine where a field is located on a page.