Recently I was asked to help out on a Mendix project. In order to test changes in the Business Modeler, I needed to get a copy of the data from the Acceptance environment so I could use it locally. I hadn’t needed to do this before so I put together a quick guide to help walk me through the process. I thought it made sense to share on my blog for others that might need to do this.
Reporting with Mendix - Failures and Successes Explained
A month or two ago I wrote about using Document Templates for reporting. At that time I was pressed for time and needed to get a few reports in PDF form out the door. I even commented that I had tried to use the Report Pane and OQL built into Mendix but struggled with the process and didn’t really have time to dive into figuring it out. This past week, however, I couldn’t build the reports I needed to do using Data Grids or Document Templates. I went back to OQL feeling confident I could write the syntax to achieve what was needed and after a day and a half of trial and error, I figured it out. I’d like to share what I learned.
So Easy A Salesman Can Do It
Just the other day one of our client relationship directors demonstrated a unique use of Mendix with me that I simply had to share. I wish I could show you screenshots of this, but unfortunately there is no way to do so given the proprietary nature of what the application contained. Here's what happened...
Developers: A Call To Use Your Application!
These past few weeks have been incredibly busy. I actually didn’t have a chance to post anything last week because of the busy schedule of developing. That and the six-week old addition to my family. This last week however proved to be one of the most fruitful. Not only am I gathering requirements, designing solutions, developing and deploying at an unprecedented rate using Mendix, but I slowed down long enough to actually use the application. The insight was invaluable and something I’m going to spend a few minutes describing so that you, too, will remember how important this is.