You can easily send a D365FO report in email just by configuring print destination to Email and setting a few properties. You can do the same from code, where you can also set the body. You must create an instance of SrsReportEMailDataContract class, fill it values and pass it to SRSPrintDestinationSettings.parmEMailContract(). Here is an example: …
A comment below my blog post Printing reports from code in AX2012 asked me to provide an example for D365FO. Here is it. The code is virtually identical. Only writing a file to a shared folder doesn’t make a good sense in cloud, therefore I changed the code to return the file to user for download. …
I recently had to move a form to another package, because we decided to extract some functionality to its own independent package. I moved files, built both packages and everything looked fine, so I started making changes for a new requirement. But later I noticed something strange in the form. When I opened the form, …
Continue reading ‘Weird behaviour after moving a form to another package’ »
A few days ago I was getting latest changes from VSTS to an AX 7 development box when it failed on a certain (custom) .dll file, because Visual Studio wasn’t able to overwrite the file. I made sure that all AX services are down, but it made no difference. Then I looked at file permissions …
Continue reading ‘‘Get latest’ failed on a file without permissions’ »
I’ve recently run into a problem with Recurring Integrations Scheduler and I think I won’t be the only one, therefore I’m going to explain it here. The Recurring Integrations Scheduler (RIS) supports both the old recurring integrations API (enqueue/dequeue) and the new package API, which is the recommended approach. With the package API, you can …
Continue reading ‘Recurring Integrations Scheduler: File already exists’ »