Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I need to make changes to an existing report (CustVendPaymProposal) in AX 2012. I added two fields to the CustVendPaymProposalTmp table, and added the fields to the CustVendPaymProposal query, which is used in the actual report model.
In the report model, the fields showed up when I refreshed the dataset. I've added the fields to the report using the designer. Everything compiles with no errors. Next, I imported the customizations back into AX by right clicking on the CustVendPaymProposal project, and then clicking on Add CustVendPaymProposalReport to AOT. The import was successful. Lastly I deployed the customizations to the report server. The deployment was also successful.
When I try to run the report, I get the error "Reporting framework error: Dynamic packed query not found."
Does anyone know how to resolve the problem?
you are getting this error because AX have stored the last value of query and it is find that since the structure of query has changed.
Go to File ->Tools --> Options -Usage data -> Reset
I also thought that it would be stored in the usage data and cleared it completely, but I still get the error.
One thing that I've picked up though, is after importing the report model customizations into AX, and I go to the table on the SSRS report within AX, I can only see one of the fields that I've added. But I can see both fields in the report model in visual studio.
So I've tried to import the customizations again by clicking on Add CustVendPaymProposalReport to AOT. The import was successful, but still I can only see the one field on the SSRS report table within AX.
I read up on the troubleshoot issues (msdn.microsoft.com/.../gg731894(v=AX.60).aspx) that when the report model customizations are not visible in AX, that you can do the following:
"The AOT does not automatically refresh as Model Editor saves changes in the model store database. To view changes in the AOT, in the Development Workspace Tools menu, click Development tools, Application objects, and then Refresh runtime model data. "
I can't find the Development tools from the Tools menu, so I'm unable to Refresh the runtime model data.
Do you think that it could be that, because the SSRS report only contains one of the fields, that it's giving the error?
I have recently also experienced this error. After digging a little deeper, I found that the 'AX_CompanyName' parameter was missing from report. This is supposed to be populated by this command =Microsoft.Dynamics.Framework.Reports.BuiltInMethods.GetUserCompany(Parameters!AX_UserContext.Value). Does anyone know how to check that this rdl exists?
I got the same error message after I updated our customer object. Did you fix this problem? How should I do now?
I'm having the same error here. How did you solve this?
What is really strange here is that I have four instances, and only in one instance one report works perfectly well, and in the other three I keep getting:
Reporting framework error: Dynamic packed query not found.(S)\Classes\xInfo\add(S)\Classes\Info\add - line 94(S)\Classes\Global\error - line 3(S)\Classes\SRSQueryBuilder\initialize - line 21(S)\Jobs\
The four of them points to the same SSRS instance.
Should I make a full compile again?
I have not found a solution as yet. The workaround that I had was, to export the report from the development environment (where I got the error), and import it into the test environment (or any other environment), and run and test the report there. You'll see that the report runs fine in the test environment. The only thing is, it adds extra time to test the changes made.
I've also only experienced the problem when I changed existing reports, not with new reports. I'm not entirely sure, but I think it might have something to do with adding the report back from Visual Studio to AX 2012. The reason I say that, is because it's only the development environment that has the problem, once you add the report back to AX. But I could be wrong.
Hy Dylan. Maybe is not related to an environment like test, but could it be that only works fine with the first instance you install and linked to the instance of SSRS.
Maybe the solution here is to use more than one instance of SSRS.
I had the same issue when I run reports in a newly created Instance. This is a VM environment , which is a copy of another existing VM environment.
I reinstalled AOS.
Changed the Report Server name and validate. Deployed All reports from AX 2012 Management Shell.
- Go to: Start > Administrative Tools > Microsoft Dynamics AX 2012 Management Shell
- Then enter Publish-AXReport -ReportName *
Deleted all existing config entries and recreated Local Client and Business Connector Configuartion reflecting new instance name.
Deleted ALL Usage Data.
Reports are started working...
This is our solution for this issue. In our case, we had correctly setup the second instance of SSRS, and in AX System Admin module, we created our SSRS configuration pointing to the new instance.
However, a key step is the Report Deployment. This is done through the Publish-AXReport powershell command. This is really important:
Make sure your "AX 2012 configuration" (client configuration) is poiting to the correct AOS instance before running "Publish-AXReport". OR use the -ServicesFilePath parameter to choose a .axc file with the correct configuration.
Check out msdn.microsoft.com/.../jj720262.aspx for more parameters
I resolved this issue by making Business Connector to point to right configuration. I got multiple instance of AX on single machine and Business Connector was not pointing to correct instance.
Hope this resolve the issue.
Had the same problem.
My SSRS server configuration (under system administration) was pointing to the SSRS instance of another AOS instance.. woops :-)
Apparantly the client makes a record in the SRSReportQuery for the DynamicParameter (query) parameter. When the SSRS instance connects to the AOS, it doesnt find it as it was inserted in the database of the other AOS instance.
Solved it by configuring it correctly.
Business Applications communities