Hi
Any run into an issue where collection values pulled from Power Automate flow do not show in a gallery? I see all the data in the collection when I select the Values icon, however not of that data show's up in the gallery. Anyone know how to get the actual column values to show up in a gallery or datatable?
Solved! Go to Solution.
@Pstork1 I'm not seeing an array property. In Flow I use an HTTP action to query Microsoft Graph then parse that output in a Parse JSON action, where I tried to use the schema, however it fails with "message": "Invalid type. Expected Array but got Object." when I test the Flow.
In your original schema that you posted for the object returned by the graph you listed this:
{
"type": "object",
"properties": {
"@@odata.context": {
"type": "string"
},
"value": {
"type": "array",
"items": {
The property 'value' is of type 'array'. That is what you need to isolate and send back to Power Apps.
@Pstork1 yeah I tried that. I doesn't look like it's going to work. The columns make it to a collection, however the data does not. So maybe it's just not supported.
Are you using the respond to power apps or the HTTP request response action to return the data? The respond to power apps can't return an array only simple data. If you are using the request response make sure you add the appropriate JSON schema to that action under advanced or you won't get the data.
@Pstork1 see image. Columns are created in the collection, however no data is sent to the collection.
You can't load the Body in as Input. That contains more than the array required and doesn't match the schema. You need to isolate the value array and send that back.
@Pstork1 humm, ok, HTTP dynamic content only offers "Body, Headers, and Status Code". How do I isolate it and what do I add as the Body?
You may have to do a Parse Json on the full body so that you can get at the array inside.
@Pstork1 yes tried that too, only the columns are added to the collection, no data is populated in the columns though.
If you feed the Body of the JSON into the Parse that should surface the properties in the JSON. But then you have to use those properties, not the Body when doing the return. You are still passing the body.
User | Count |
---|---|
261 | |
110 | |
98 | |
56 | |
40 |