Skip to main content

RDLC Report - The tablix ‘Tablix1’ has a detail member with inner members. Detail members can only contain static inner members.

Hi Readers,

In This article we will discuss how to resolve an Issue that we face During Creation of a RDLC Report.

Applies To - NAV 2009 and Later (RDLC Reports)

Scenario -

You are creating Say a Document Report. There are multiple tables in Body. For Linking these tables you put all these tables inside a List.

When You want to save the Report, You get an Error Message -
Error while validating RDL content:
The tablix ‘Tablix1’ has a detail member with inner members. Detail members can only contain static inner members.




How To Resolve Error?

Select the List and From Row Group Select Group Properties.


Select Add in General Tab and Add the Group Fields for the List.



Save the Report.

You Need to Add the Fields based on Which you want to repeat all the tables inside List.

For Example If Its a Sales Order Report Then You want to Group on -
Document Type
Document No.

Hope it make sense and will help you if you face the Above issue.

Regards,
Saurav Dhyani

Comments

Post a Comment

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

How to Set Up NavUserPassword Authentication in Business Central.

Hi Readers, In this article we will discuss steps to Setup NAVUserPassword in Business Central on-prem. NavUserPassword is an authentication method that's handled by Business Central Server, but isn't based on Windows users or Active Directory. Each user is set up with a username and password that's configured inside Business Central only. The user is prompted for username/password credentials when they start the client. #msdyn365bc, #credentialtype

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.