Skip to main content

RTC Report Development 1.

Hi all,

we all have some known and unknown issues while creating a Report For Role Tailored Client.
we will try to create a standard report by deleting its Layout and creating a new RDLC Layout from Scratch.

I have saved Standard Report 406 Purchase - Invoice as 5000 Purchase - Invoice 1.
Then I deleted its existing layout by using Tools->Delete Layout.

Now lets create the Layout from Scratch.
Now lets see what Layout suggestion suggest for this report, by using Tools -> Create Layout Suggestion.



Yep, something Creepy Layout will Come up, as we know because we keep on trying this option first and for some small reports it work sometime.

But this suggestion also help us for complex reports too. we will see same in next post. 

Don't forget to comment if you can share something I missed, if you want to know anything else or if i am wrong somewhere.

For Next article please read here.

Regards,
Saurav Dhyani

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.