All IT leaders face challenges of outdated technology. Sometimes it’s time to build or buy a new application. But nowadays, it might make more sense to refresh the new old one. I explore those challenges and provide real client examples where I’ve used low code to help in both cases.
I share my thoughts on the recent acquisition of AppGyver by SAP and how that does or doesn’t relate to their SOLEX partner, Mendix.
The world is battling a war on two fronts: our health is threatened by COVID-19 and our economies have slowed and even stopped in certain sectors. As an App Developer, does my work really matter in such times?
After years of delivering, leading, and coaching leaders in Rapid App Development, I give you my perspective on what skills and profile it takes to be a ‘Great’ RAD Maker.
It’s been 1 year since I first wrote the post, “Extending SAP: Fiori or Mendix?” and a lot has changed. Because of the changes, this older post has gotten a lot of renewed interest so I thought I would take a look at my opinions from a year ago and see if they differ. If you haven’t already, please refer to the original article to have context for this one.
IT should be an expert “SWAT” team with precise skills to tackle the toughest app challenges, not a bottleneck to solving business problems.
I thought I would pass on some information I struggled through and also record it for my own sake. The documentation on how to use the Format String widget is unclear. Read on if you want to save yourself some frustration.
I was asked the following question recently:
Do you know if it is possible to use a new-line character when creating an attribute in Mendix? I've created an attribute that I would like to display as such:
Attribute Name
Entry 1
Entry 2
Entry 3
...
Where each Entry is generated via a loop. I've tried every new-line character combination and trick I know and can find on the internet ( '\n', '\\n', 'newline', hard coding the return, hard coding the return with a character in the first and last slot, hard coding spaces, etc.). All of the questions about this topic that I've run into on the Mendix forums have claimed that '\n' or '\\n' work but these do not work for me. I ran into one question on the forums (whichI can't seem to find now) where someone asked the exact question I have and also said that none of the answers he received worked.
The good news is that I can help. I, too, struggled with this topic early on in my Mendix development. I'm sure I read many of the same forum posts this individual did as well as I recognize the proposed solutions. Here's how I deal with line breaks in my Mendix strings.
