Recently I encountered an issue when installing reporting extensions.
An error occurred during setup of Reporting Services extensions.
Reason: Version string portion was too short or too long.
System.ArgumentException: Version string portion was too short or too long.
at System.Version..ctor(String version)
at Microsoft.Dynamics.Setup.ReportsServerInstaller.GetOrCreateServerConfiguration(String instanceName, String sharePointServiceApplicationSite, Boolean& createdConfiguration)
at Microsoft.Dynamics.Setup.Components.ReportingServicesExtensions.InstallConfigurationFiles(String instanceName, String sharePointServiceApplicationSite, Boolean& createdConfiguration)
When trying to process a new installation of Analysis server with the AX anaylsis entensions installed, you may get the following error message: The provider ‘SQLNCLI10.1’ is not registered.
Adding a timeout control to a no yes dialog box has some value. While the standard system does not allow you to control a form in this way for boxes, it is possible to modify the system to achieve this.
You may encounter an error when installing some of the components on AX. The error message will read:
The AOS ‘<server>@<port>’ cannot be reached. Setup cannot continue. Verify that you are entering the correct server information and that the AOS service is running.
If you want to include line breaks (\n) in your labels, displaying in box or dialog screens then you need to use the strFmtLB control to make sure the label is displayed correctly.
@DAX123 = “Some text\nAnother line”
So you would like to create a custom lookup for the inventory table (Inventtable). As part of your design you include itemId and the display method ItemName. When you run the lookup you find the item name column is blank.
When dealing with performance, there is a new control under the AX query system called Query::Insert_Recordset. This allows mutliple records to be inserted into a table, with a single SQL call, in the same way the insert_recordset command works.
While this command is great for performance, there is a problem with the standard crosscompany control when using the query::Insert_recrodset comamnd. The crosscompany controls only build the extended select statement to include the comapny control (dataareaid) when the queryrun class is used. If since the query::insert_recordset does not use the the queryrun class, the crosscompany control does not work, and will not filter the data across companies based on any rules you apply. It will however extract data for all companies.
The only work around that I have found is to add the dataareaid into the query, selecting the companies you want to use, this then includes the company control into the SQL statement ensuring only the companies you are interested in are processed.