cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
WingnutPLD
Level: Powered On

Object variable parameter references being removed

I've created an object type variable to hold some values to be used in an approval flow. The definition looks like:
{

    "someValue": value1,

    "someValue2": value2,

    "someValue3": value3

}

 

When applied to the details section of the approval connector I've tried both:
    variables('myVariable').someValue

and
    variables('myVariable')?['someValue']

 

Both of these work correctly (display the proper values) until I reopen the Approval connector to make any changes, When I do, instead of seeing my custom expression, I'm presented with a call to the variable itself (just the purple box that says the variable name with the tool tip saying "variables('myVariable')" )

 

I don't think this has happened with other connectors so it may be an issue with the Approval connector specifically. 

2 REPLIES 2
Community Support Team
Community Support Team

Re: Object variable parameter references being removed

Hi @WingnutPLD,

 

I did the test on my side, and the result is the same as what you described, just the purple box that says the variable name with the tool tip.

Then I used the Compose-action test again and found that this situation still appeared. So this may not be an issue with the Approval connector specifically.

18.PNG

When using Expression in many connectors, Flow will translate according to the composition and parameters of the expression, in order to better express the composition of the expression.

However, the hint after translation does not show which property is called. This is something to be concerned about. We will continue to pay attention to this issue. thanks for sharing.

 

 

Best Regards,

Barry

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
WingnutPLD
Level: Powered On

Re: Object variable parameter references being removed

Yeah, I've subsequently tested other connectors and they behave similarly. However when used with a condition they remain as the appropriate expression which is editable after the fact. 

 

The primary issue here not simply that the hint is incorrect, but that we have no idea what value is being used from the object. Without it being presented properly, you can't edit it either without completly retyping the expression. The way variables as dynamic content are handled vs the way expressions are handled are totally different. 

 

For the time being, until this is addressed, I just instantiated individual variables rather than relying on a single object type var. Hopefully this will be addressed soon since it makes testing/refactoring totally untennable. 

Helpful resources

Announcements
firstImage

Power Platform Online Conference

Speakers, submit your sessions now! Call for speakers ends Feb. 10!

firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

firstImage

Incoming: New and improved badges!

We've given our badges an overhaul and also added some brand new ones!

fifthimage

Microsoft Learn

Learn how to build the business apps that you need.

sixthImage

Power Platform World Tour

Find out where you can attend!

seventhimage

Webinars & Video Gallery

Watch & learn from the Power Automate Community Video Gallery!

Top Solution Authors
Top Kudoed Authors (Last 30 Days)
Users online (2,109)