Hello everyone! I hope you all are doing well. This is the second installment in our report development series. If you haven’t already watched the first video, which covers the basics of report components, I recommend checking out the playlist to get a foundational understanding before diving into this guide. In today’s post, we’ll take a step forward and start building a document report, specifically a Sales Order Report . While working on this report, we’ll cover many essential aspects of RDLC report development that are crucial to understanding the overall process. This guide will focus on printing the report body , and in future posts, we’ll tackle the header and footer.
Hi everyone, I hope you're all doing well! Today, I’m excited to introduce a new blog series focused on RDLC Report Development in Microsoft Dynamics. Throughout this series, I'll share insights, best practices, and step-by-step guides on how to develop reports in Dynamics NAV. As a developer, I’ll be covering everything I know, so if this interests you, make sure to stay tuned! In this first post, we’ll go over the basics: what a report is, its components, and how RDLC reports function in the developer environment. For the demonstration, I’ll be using Microsoft Dynamics NAV 2016, but most of the concepts discussed will apply to NAV 2013 R2, NAV 2015, and even newer versions with only minor changes.