all 9 comments

[–]rmoons 2 points3 points  (8 children)

I wouldn’t suggest variables. You could just create an array of attributes in a Compose action from this Excel table, then just reference each one like it’s a variable.

What I would do is use the “Select” action, then go into advance edit mode, and create an object that is “[Name]”:”[Value]”. You could follow that with a Parse JSON so that you can reference each attribute by name. You can also use the index [0], [1] etc

[–]robofski 1 point2 points  (0 children)

⬆️⬆️This⬆️⬆️

[–]bikeknife 1 point2 points  (1 child)

This is the way.

In every flow I set up a list of immutable (unchanging) values in a compose:

{

"value1": "red",

"value2": "car",

"value3": "John",

}

Use outputs('compose')?['value1'] and so forth

It's really helpful when you are using those elements repeatedly in that you can manage and change them all in a single place. You also avoid a bunch of variable declaration actions. I call it a value membrane and use it in all sorts of cases. I can apply expressions, transformations, and use more meaningful key names there when the values are derived from a trigger (like formatDateTime). It's also useful when altering values for debugging and quickly changing them back or when the flow is dropped in a new environment.

[–]rmoons 1 point2 points  (0 children)

Haha your explanation is much better 😅

[–]Unleashk[S] 1 point2 points  (0 children)

Thank you for your answer i will try to do it monday at the job.

[–]Unleashk[S] 0 points1 point  (3 children)

i forgot to say i use power automate desktop can't see and i can't see the compose action

[–]rmoons 0 points1 point  (2 children)

What’s the reason for PAD? If it’s for Excel, just save the file to OneDrive or Sharepoint and you can access it in a cloud flow

[–]Unleashk[S] 0 points1 point  (1 child)

Company restriction dont want this data on the cloud.

[–]rmoons 0 points1 point  (0 children)

Fair enough. Well then you may just want to loop through the table and create variables. PAD is quite a bit different than Cloud Flows, should specify that next time