CustomString Widget - Causing Deprecated Message in Console?

0
Hi – I’m very fond of the “CustomString” widget from the app store. In my Console, however, I suspect my usage of CustomString is causing the following warning? Any ideas why or a workaround? I know one workaround would be to create separate entities to store the summary results of my microflows, but CustomString makes the output so much easier and efficient. I hope I don’t have to relinquish it!   DEPRECATED: mx.ui.action. Use mx.data.action directly instead. -- will be removed in version: 10.0
asked
4 answers
1

Found this earlier tip so will try the Show Message approach with a parameter – thanks Mike!!

https://forum.mendix.com/link/questions/7374

answered
0

Looks like that widget is on its way to being deprecated.

You could check out the FormatString widget.  It requires a context object, however, its very flexible in the type of output you can produce.

answered
0

Hi SL

In Mendix 8 there is not always a need for the Custom String and Format String widgets. The standaard core Text widgets shipped with the modeler, can now use text templates. https://docs.mendix.com/refguide/text#1-introduction 

Cheers, Andries

answered
0

So in my case, I have a microflow that outputs a summary field … Seems like I’ll have to create separate entities for all of these. Has anyone found a workaround to this that doesn’t involve using a widget like CustomSTring? I appreciate both suggestions above; however, both would require me to create separate entities for nine summary fields that I need to display.

answered