cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Arpful
Level: Power Up

Combining two GET Requests sorted and joined by a key/value identifier and more

Here is the scenario: 

I have several devices to pull info from, but all accessible through a single GET request. However, the model number is not included on the first request. I have to do a second to get that information. Then I need to make the two request data into a multiple entries with the data joined together. Finally, I need to replace the model numbers with their more friendly names. Bonus - Create a count of all Model X vs Model Ts in the entirity of the request and include in the same CSV. 

 

Request 1: 

GET / app-json

Device ID: 00000

user: Jane Smith

OS: 

Warranty: 

Serial:

 

Request 2: 

GET / app-json

Device ID: 00000

Model number: XXXXXX12

 

I need to combine sorted by Device ID: 00000 (So that the information matches each other.)

 

Compose and replace: 

Then - Replace the model number with a friendly one ex. XXXXXX12 subsituted with Model X. 

 

So far I have:

HTTP  x2

Parse x2

Select x2 (the information I need - bunch of extra stuff I don't)

?

 

Then 

Create CSV Table

Attachment CSV Table

and hopefully end up with something like this. 

 

Device ID: 00000

user: Jane Smith

OS: XX

Warranty:  Some Date

Serial: Serial

Model: Model X

 

If possible add a quanity count of running total of Model X (or other model friendly name) on a seperate table, but within the same CSV created. 

 

2 REPLIES 2
Community Support Team
Community Support Team

Re: Combining two GET Requests sorted and joined by a key/value identifier and more

Hi @Arpful,

 

Have you take a try to achieve the requirement within microsoft flow?

What is the trouble you meet when you try to achieve the needs?

Please share more details so we would try to provide a proper workaround for you.

 

Best regards,

Alice

Arpful
Level: Power Up

Re: Combining two GET Requests sorted and joined by a key/value identifier and more

Yes I have.

The details are in the original message.

 

To be honest, I assume this is probably a built in function - It would seem crazy to me that a dev team wouldn't put that on the list of a basic feature, especially with everything flow interacts with.

Helpful resources

Announcements
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 Kudoed Authors (Last 30 Days)
Users online (4,765)