OK This might be complicated

[MooseGooseLoose]

So I have pretty layered question here that I cannot really answer atm. I'm trying to do a couple things with Power automate that I'm not sure is supported. I want to:

1.) Create a table out of a excel sheet that comes from sharepoint

2.) Have said table look for one column of data

3.) Look and count every instance of an instance taking place in said column

4.) Take those counted instances and place them in another column in another sheet that's in sharepoint

5.) Have the instances be populated by the corresponding parameters

6.) Have this refresh everyday (the original file is replaced, refreshed and upload everyday)

7.) Go to the next column in the 2nd sheet every  1st of the month

I'm pretty sure that doesn't exist but if there's a way to at least do it partially in a way that I can kind of jigger, that might be worth it

[Koen5]

Dear M,

What you describe seems well within the functionalities for PowerAutomate. I do not see any major obstacles here.

What is the particular problem that you have and you ask the forum for input?

Happy flowing,

Koen

[MooseGooseLoose]

Well I actually got the CSV ( I erred in the post above as the original file to be replaced was a CSV) into a JSON file, but what I'm actually asking is how to read and count members from a column in the JSON, how to create a table with the correct count , and then have that result automatically upload to a sharepoint excel file daily at a scheduled time

[abowen]

You could probably index the JSON table for the column you want and then use the length function, if I understand you correctly. For instance, an expression in a Compose action can look like:

length(outputs('JSON_file')['body/value']['Your Column Name'])

You can then use the output of the Compose as the input to your table. 

Do let me know if I'm misunderstanding!

[MooseGooseLoose]

The formula doesn't work since the CSV is parsed into a JSON file in the same flow I think. I think I messed up along the way and that's why it's screwing up

[abowen]

You can still index JSON files like this as they're stored in Automate. You should give it a try if you haven't. Be sure to look at the output of your JSON where it's created so you know how to structure the indexing query. 

[MooseGooseLoose]

Alright, so we ran that expression and it just didn't work. Is there another way you would  actually index or fix this?

[abowen]

Could you be more specific? How did it not work? Did you get an error message? What are your outputs for the JSON file?