Azure / LogicAppsUX

https://learn.microsoft.com/azure/logic-apps
MIT License
65 stars 64 forks source link

Unable to open expression editor for short expressions #4728

Open kalarusp opened 2 weeks ago

kalarusp commented 2 weeks ago

Describe the Bug with repro steps

When I define short expression in logic app (i.a. body('Parse_json')?['prop']) and then leave expression editor, I'm not able to open epxression editor again by clicking LMB. Attached screenshot (highlighted expression which I want to edit using LMB):

image

I'm adding also logic app ARM template attachment.

What type of Logic App Is this happening in?

Consumption (Portal)

Are you using new designer or old designer

New Designer

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
        "workflows_lap_gip_new_ga_designer_bug_dev_name": {
            "defaultValue": "lap-gip-new-ga-designer-bug-dev",
            "type": "String"
        }
    },
    "variables": {},
    "resources": [
        {
            "type": "Microsoft.Logic/workflows",
            "apiVersion": "2017-07-01",
            "name": "[parameters('workflows_lap_gip_new_ga_designer_bug_dev_name')]",
            "location": "northeurope",
            "identity": {
                "type": "SystemAssigned"
            },
            "properties": {
                "state": "Enabled",
                "definition": {
                    "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
                    "contentVersion": "1.0.0.0",
                    "parameters": {
                        "$connections": {
                            "defaultValue": {},
                            "type": "Object"
                        }
                    },
                    "triggers": {
                        "When_a_HTTP_request_is_received": {
                            "type": "Request",
                            "kind": "Http",
                            "inputs": {
                                "method": "POST"
                            }
                        }
                    },
                    "actions": {
                        "Parse_json": {
                            "runAfter": {},
                            "type": "ParseJson",
                            "inputs": {
                                "content": {
                                    "prop": "val"
                                },
                                "schema": {
                                    "type": "object",
                                    "properties": {
                                        "prop": {
                                            "type": "string"
                                        }
                                    }
                                }
                            }
                        },
                        "Compose": {
                            "runAfter": {
                                "Parse_json": [
                                    "Succeeded"
                                ]
                            },
                            "type": "Compose",
                            "inputs": "@body('Parse_json')?['prop']"
                        }
                    },
                    "outputs": {}
                },
                "parameters": {
                    "$connections": {
                        "value": {}
                    }
                }
            }
        }
    ]
}

Screenshots or Videos

No response

Browser

Chrome

Additional context

No response

Eric-B-Wu commented 2 weeks ago

@kalarusp thanks for reporting this, this was a previous made feature request that expressions that were outputs get converted to output tokens and not expression tokens, as there was some confusion when we had separated output and expression token pickers. A consideration overlooked was that users may still want to access the expression editor from the created output token. I'm going to look to implement this future in an upcoming release.