QuickFix: [Solved] SSRS Report Deployment failed - The number of defined parameter is not equal to the number of cell definitions in the parameter panel

While duplicating an SSRS report for customization sometimes you may face this error at the time of report deployment. 

Error Message:

"SSRS Report Deployment failed - The number of the defined parameters is not equal to the number of cell definitions in the parameter panel."

Solution: 

The first thing you need to check for any extra parameter is this report, compare with the standard report. There are two places you need to compare

1. DataSet parameters

2. Report Parameter

There might be an extra parameter(s), try to remove this extra parameter from the report. In case you are unable to delete it from the front end you need to open the report in XML (Right-click on the report in solution and select open with > Open with XML Text editor).

In the XML file search for this parameter and carefully remove it from everywhere. If you are not familiar with XML better to take help. Save your changes and build the solution. This time your report should be deployed without any error. 

-Harry Follow us on Facebook to keep in rhythm with us. https:fb.com/theaxapta

[Solved] Issue with Database import in Dev Box

[Updated on 19 Oct, 2023]

Hi Folks, 

While trying to import the UAT database into the dev box or any other tier-1 box (You might have tried this MS document), 

*** Changes to connection setting default values were incorporated in a recent release.  More information is available at https://aka.ms/dacfx-connection

*** Error importing database: Could not import package.

Changes to connection setting default values were incorporated in a recent release.  More information is available at https://aka.ms/dacfx-connection

Unable to connect to target server 'localhost'. Please verify the connection information such as the server name, login credentials, and firewall rules for the target server.

A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)

The certificate chain was issued by an authority that is not trusted.

*** The settings for connection encryption or server certificate trust may lead to connection failure if the server is not properly configured.

That's because of recent changes in encryption policies on SQL. To fix this issue you need to update the import SQL command below

SqlPackage.exe /a:import /sf:J:\MSSQL_BACKUP\UATbackup.bacpac /tsn:localhost /tdn:AXDB_UAT /p:CommandTimeout=1200 /TargetEncryptConnection:False

Update on 19 Oct, 2023:

Now you have to use the new parameters below 

SqlPackage.exe /a:import /sf:J:\MSSQL_BACKUP\UATbackup.bacpac /tsn:localhost /tdn:AxDb_UAT /p:CommandTimeout=1200 /TargetUser:"axdbadmin" /TargetPassword:"<DB adm pwd>" /TargetTrustServerCertificate:True

-Harry Follow us on Facebook to keep in rhythm with us. https:fb.com/theaxapta