Skip to main content

SSRS - D365 FO SAT-box annoyance

WHY oh WHY, does the developer-box not tell you, that you can not use custom code in an SSRS-report ?

Working with a SSRS-report on Dynamics 365 FO, I came across the following annoyance, with Microsofts setup virtual boxes in Azure.

I was working with getting the report to present the filters and chosen parameters from the report dialog that the user is running the report with.
At some stage, I thought making a function with custom code in the report properties, was the way to go, but I abandoned that approach in favour of another - AND forgot all about the code.

This meant that the custom coded was checked into dev.azure.com, and included in the build on the build box. So I got the deployable package and uploaded it into asset library in LCS, and applied to the SAT-environment.

No worries. Right until the users started tested the report in the SAT-environment, because they got:




So this meant going back to the dev-box, cleaning out the custom code, doing the building and applying to SAT all over again.

Why could the build-box not just check for this, and warn me? :-(

Lesson learned do NOT use custom code in SSRS-reports for D365 FO.



Comments

Post a Comment

Popular posts from this blog

Suppressing the infolog

Supressing the infolog is often useful in D365FO when augmenting code. When augmenting code using COC (Chain Of Command), you can have new code run either before or after the code you are augmenting. This means that any infolog-messages that the standard application code does, will be shown to the user, even if your augmentation supports a scenario where there must be no infolog-messages. How do you avoid the standard application infolog-messages ? To the rescue comes temporary supression of the infolog. The suppression consists of: 1) Saving the current infologLevel 2) Setting the infologLevel to SysInfologLevel::None 3) Run your code 4) Restoring the saved infologLevel to the infolog For example a table could have a validatewrite-method that validates that you are only allowed to use 3 out of 6 options in an enum-field, and you need to allow for a fourth one. Table a - validateWrite method: boolean validateWrite() {     Switch (this.enumField)     {     ...
Post a Comment
Read more

Dynamics AX 2012 ValidTimeState tables and form changing view from current to all

Valid Time State tables are new i AX 2012 a gives the developer the possibility to easily create tables that hold e.g. current setup data for various purposes, and at the same time keeping a "history" of the changes of the data in the table. For more reading: http://msdn.microsoft.com/en-us/library/gg861781.aspx I was tasked with doing a setup table with rates for calculating Vendor Bonus and I chose to base this a valid time state table. The customer asked for a button on the form, where you maintain the vendor bonus calculation setup data, so you could toggle viewing "Current setup" or "All setup" records (changing the view from actual to all records and vice versa in the form). I found that you can not change the ValidTimeStateAutoQuery property on the form data source in a form at run-time. It simply does not change anything, so I came up with the following solution: A boolean class member in the classdeclation method of the form: boolean ...
Post a Comment
Read more

Subtle but important difference between _ds.executeQuery() and ds.Research()

This is actually an old entry. Been tumbling with a problem for the last few days. A form in our Dynamics AX module for Preventive Maintenance Control was not behaving. The form has "explicit" filter fields that the user can see without having to activate the form filter (CTRL+F3), for setting up filters most commonly used in an easy way. And this is working ok. However at this customer site, the form has been adjusted so that the user can have the form refreshed automatically periodically, and when the users at the customer site were making use of the "explicit" filter combined with the AX's normal filtering (CTRL+F3), the form simply threw away the normal form filtering. I discovered a subtle but very important difference between writing _ds.executeQuery(); (which was the way our code was doing it) and _ds.Research(); The difference is that _ds.Research() will retain the filter ranges in the forms query as they are right now. _ds.executeQuery() will NOT. It ...
Post a Comment
Read more