Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Many crash scenarios don't have error messages. This means that I can't troubleshoot the issue mysellf and have to open a helpdesk ticket. This is very frustrating as there are many things that could go wrong. This issue persists across Power BI, but is most common with troubleshooting gateway refresh issues. In many cases the there is at least a 400-500 request error which is at least a clue. However there is usually no idication of where the process has failed and you have to test each individual part to find the problem. This is especially important when trying to dog-food products that are known to have issues.
In many cases the error message is {field-value}. This means that there is a placeholder to put an error message, but no actual error message was written. The user is then forced to open a helpdesk ticket and wait for something that they could solve themselves, or spend hours looking into every aspect of the process to find the one thing that has been switched.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.