Partial Outageshare-external
[Blocker] Invalid format of dynamic data '${data.text-disclaimer.visible}' in the screen data model
1

I'm using Flow JSON version 3.1. Recently, there was an update, and it broke the behavior of flows. It was working for me two days back. I have used the "-" (dash) character data model name; see the example below. I have a few flows with the same pattern, and all were working, but now the flow builder is showing Invalid Flow JSON, which is blocking further development. Even if this support is being dropped then, please continue to support for old flow JSON. Team, please have a look on this. Flow JSON for quick testing:

{
    "version": "3.1",
    "screens": [
        {
            "id": "identifierPanel",
            "terminal": true,
            "title": "${data.identifierPanel}",
            "refresh_on_back": false,
            "data": {
                "text-disclaimer": {
                    "type": "object",
                    "properties": {
                        "visible": {
                            "type": "boolean"
                        },
                        "value": {
                            "type": "string"
                        }
                    },
                    "__example__": {
                        "visible": true,
                        "value": "Disclaimer"
                    }
                },
                "disclaimer-text": {
                    "type": "object",
                    "properties": {
                        "visible": {
                            "type": "boolean"
                        },
                        "value": {
                            "type": "string"
                        }
                    },
                    "__example__": {
                        "visible": true,
                        "value": "some long disclaimer text"
                    }
                }
            },
            "layout": {
                "type": "SingleColumnLayout",
                "children": [
                    {
                        "children": [
                            {
                                "type": "TextCaption",
                                "visible": "${data.text-disclaimer.visible}",
                                "text": "${data.text-disclaimer.value}",
                                "strikethrough": false,
                                "font-weight": "normal"
                            },
                            {
                                "type": "TextCaption",
                                "visible": "${data.disclaimer-text.visible}",
                                "text": "${data.disclaimer-text.value}",
                                "strikethrough": false,
                                "font-weight": "normal"
                            },
                            {
                                "type": "Footer",
                                "label": "Continue",
                                "enabled": true,
                                "on-click-action": {
                                    "name": "data_exchange",
                                    "payload": {
                                    }
                                }
                            }
                        ],
                        "type": "Form",
                        "name": "identifierPanel"
                    }
                ]
            }
        }
    ],
    "data_api_version": "3.0",
    "routing_model": {}
}
Deepak
Asked about 2 months ago
Selected Answer
1

Hello Deepak, Yes, there was an important bug fix where the dash character on data model resulted in incorrect data on mobile, even if the builder was not showing any errors. This resulted in run-time errors hard to debug and resolve. Please note that any of these flows that were already sent to mobile will keep working as before. Unfortunately dash on data model cannot be supported at this stage.

September 19 at 9:40 AM
Berni