I'm stumped on this one, folks.
I am taking JSON data from an online form, parsing it, and converting it into a .csv for import. I have built and tested a flow that works exactly as needed - almost.
The online form gives users the option to enter information for anywhere from 0 to 10 children (family law intake). So, the JSON can contain data for 0 to 10 children. Incoming data for the fields contains either a six-or-eight-character Code, and then an explanation (it's in a drop-down on the online form). I need to export only a substring of that data (either the left 6 or 8 characters) into the .csv for import.
Problem is, I can't use Initialize Variable to do this within a loop (that will run x times, where x = 0 to 10).
Is there a way to substring just the raw parsed JSON data so I only grab the characters I need for inclusion in the variable table I have created for the data (prior to export to .csv)? I have tried to use the 'substring' expression, but it won't even let me select the variable I need from within the sub-data for "CHILDINV" - I'm stuck.
Solved! Go to Solution.
Absolutely, @ArchieGoodwin, here's a solution which produces all the rows, all the headers, and the full 10 kids.
I'll admit that were this me I'd space out the logic a bit more so that others won't be blinded by the long expressions on show. One of the main things I try to show folks in a work environment that Power Automate makes an office less reliable on Jon/Janey and their wizard excel formulas. As soon as you start sprinkling long 'formula' everywhere here, anyone taking over the management of it might still be a bit taken aback.
If I were to do that here, I might make the two sides of that union in the CSV separate object variables then reference them.
Solution
This solution is transferrable if you want to apply it to more than one array in the original data.
@Paulie78 thanks for the help, and for the range fiddle, too! I had originally done ten fields that long way, and thought that there *had* to be a way to get it done with less typing. 😅
Code
kidsVAR
This just counts the number of kids, and subtracts it by one. This saves overcomplicating the multiple if() statements in the Select action.
sub(length(variables('jsonInputVAR')?['body']?['CHILDINV']), 1)
SelectKidsData
In the 'From' field this uses a trick that Paulie taught me elsewhere, the range() function. So it iterates through 10 items, regardless.
range(0, 10)
In the 'Map' 'key' fields (left), this uses some basis logic looking at the current item() number in the range, and adds 1. This provides your child number.
add(item(), 1)
In the 'Map' 'value' fields (right), this uses a simple condition. If the current item() number is greater than the number returned in the kidsVAR variable, then it places nothing ('') in the field, otherwise it picks the child data that is correspondent to the current item() number. It looks like more than it is. 👍
if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['Id'])
if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['C1NAME'])
if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['C1BD'])
if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['Gender'])
if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['C1LEGAL'])
if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['C1PHYS'])
if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['C1VISIT'])
if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['FIELD8'])
if(greater(item(), variables('kidsVAR')), '', variables('jsonInputVAR')?['body']?['CHILDINV'][item()]['ItemNumber'])
Create CSV Table
This one is basically constructing an array for the Create CSV Table action to make its data from. Don't forget to place the square brackets around it in the 'From' field:
union(removeProperty(variables('jsonInputVAR')?['body'], 'CHILDINV') , json(replace(join(body('SelectKidsData'), ', '), '}, {', ',')))
The union() function is usually used to join two arrays together, but it works with objects, too, so the main thing here is ensuring that the child data is represented as an object instead of an array, after the previous Select action has done its thing.
So, in the second section of that union function this is done by:
The first part is getting all the non-child data by simply using the removeProperty() function to strip the CHILDINV data out of the original object.
Additional Arrays
To apply this to other fields in the original JSON just requires a few tweaks. Let's look at the potential for the DOCUMENTS array field to need it.
union(removeProperty(removeProperty(variables('jsonInputVAR')?['body'], 'CHILDINV'), 'DOCUMENTS') , json(replace(join(body('SelectKidsData'), ', '), '}, {', ',')) , json(replace(join(body('SelectDocsData'), ', '), '}, {', ',')))
If there is no set limit to the documents, then take the docsVAR and add 1 to it for the other side of the range() expression.
EDIT - I've tested this on ten children ... and they're all still alive to tell the tale!
If I'm reading you right (I might not be) I don't see any reason why not, but I think if anyone is going to help here we might need to know a bit more.
Could you put up an example of the received data from a form in its JSON format, please?
It can be fake data, but the data how it looks before the Parse JSON action (what you'd have used to create the parse) would be wonderful.
Additionally, if you're appending that data to a CSV, you'll need to create rows if you intend to capture more than one item (with headers, etc). So I would suggest creating a String variable that contains a single carriage return (I tend to call them 'carriageVAR') and placing that at the start of each of these Append to string variable actions.
Placing new lines at the start avoids spurious additional lines in documents.
No matter what I do, I cannot post the JSON. I have stripped out the headers, everything. It keeps getting marked as SPAM and my replies deleted.
Very frustrating.
OK, I have had to resort to taking screen snips of the JSON.
Ouf, if that's real data, you might wanna scrub it again, quicksharp, mate!
((( did you try the code button? </> )))
NOT real data. All fake.
Phew! 😅
Alright, for starters, with regards to ...
Variables
You initialise any variables (using the Initialize variable action) that you want at the start of your flow, have them sitting waiting for the data.
Then, when the time comes, you use the Set variable action to set the variable.
Calling JSON Data Directly
Now, it's entirely possible that you're not calling the data correctly in the Apply to each action that you're running there which you have named "Child DATA from JSON Entries" up above.
If you are not running a Parse JSON action, and working off of that (by fair the easiest way to pick values), then for each fieldname that you want to call, you need to use this syntax:
items('NAME_OF_APPLY_TO_ALL_ACTION_THIS_IS_IN')?['NAME_OF_FIELD']
So, in your case, a typical field would be:
items('Child_DATA_from_JSON_Entries')?['C1NAME']
Now, if you want to work that into a variable, so that it's useful within the same Apply to each loop run, then you place it in an expression, there, then just pick the variable up wherever needed.
Running the Whole Thing Without An Apply to each action
This is unwise, but it can be done.
It's unwise because:
Anyway, if you wish to reference a particular item from that asdasd array in the JSON, then you would just use something like (name 'JSON_Input' right according to your flow):
body('JSON_Input')?['CHILDINV'][0]?['C1NAME']
Now some might raise an eyebrow about the question marks and that [0] placement, but I'm pretty sure that flow is intelligent enough to follow that (it has for me, before).
Here's an example that's not quite analogous of me using that to grab the first result from a Filter array action that I know will get 1 response every time:
body('Filter_array')[0]?['Id']
Thanks for your help so far. To clarify, the Append to String Variable above is working. Basically, this flow doubles as a schema to map the JSON over to the formats (date from US to normal, removing extra characters, etc.) and creating a header row that matches the names of the data fields in the Advantage database we will be importing the results to:
So, as you can see, I'm able to initialize variables and create expressions to convert the data to the format I need, grab the substring, etc. - for all the data EXCEPT the data about children, because once I call CHILDINV, it goes into a loop. What I need is to be able to <formatDateTime> the child's birthday (C1BD), and <substring> custody status (C1PHYS, C1LEGAL) and visitation (C1VISIT), for 1 to 10 sets of data.
I can initialize variables and create my conversion expressions for the top-level data, but not for the data in the loop.
I suppose could create another flow that grabs the final CSV from Sharepoint, converts the data, and then saves it to a new CSV, but I was hoping to figure out how to do this before I created the matters.csv file.
So, in essence, how do I do this:
...for the data inside the CHILDINV part of the JSON / parsed data.
Hope this helps, and thanks again.
Got ya, gimme a second! 🙂
I was going to put this in the solution post, but I have a feeling that it would've just made it stupidly long ... which is something I do, anyway. 😏
Here's the JSON data that I was working from:
{
"body": {
"FIRST": "Harvey",
"MIDDLE": "Weinstein",
"LAST": "Wallbanger",
"MAIDEN": "Smith",
"DOB": "2001-01-01",
"CLASS": "CLI0LGMR - Legally Married",
"ADDl": "123 Sesame Street",
"LABEL2": "Apartment 7",
"LABEL4": "R.R. #2",
"CITY": "Trenton",
"ZIP": "K8V 1R6",
"Province": "Ontarlo",
"JURISDICr": "4 years",
"PRIVEMAIL": true,
"EMAIL": "glenn@xasdasd.ca",
"PREFEMAIL": true,
"PHONE4": "343-263-4643",
"PRIVPHONEC": true,
"DAYPHONE": "613-966-777'",
"PRIVPHONE": true,
"COMPANY": "KDA Law",
"REFERREDBY": "Jeff van de K2e-t",
"FIRST2": "Karen",
"MIDDLE2": "Snarf",
"LAST2": "Wallbanger",
"MAIDEN2": "deKaren",
"DOB2": "1998-01-24",
"CLASS2": "OPP-LG1 - Legally Married",
"ADD12": "123 Complaint Bouleva~d",
"LABEL22": "Apartment 2",
"LABEL42": "R.R. 17",
"City2": "Picton",
"Province2": "Ontario",
"ZIP2": "K7L 2E4",
"JURISDICT2": "3 months",
"OpposingPartysEmailAddress": "ka~e~Sw'~ine~.ccr~",
"PHONE42": "613-966-7771",
"DAYPHONE2": "647-265-8597",
"COMPANY2": "Nestle Quinte West",
"COUNTY": "Hastings",
"COHABITATE": true,
"DATEMARRY": "2020-01-16",
"STATEMARRY": "Ontario",
"DATESEP": "2021-08-02",
"STATESEP": "Ontario",
"FIELDl": "Belleville",
"PRENUPTUAL": false,
"ISFATHER": true,
"ISMOTHER": true,
"DOM": "2000-01-27",
"DIVDATE": "2004-07-29",
"CHILDREN": true,
"ISRELATED": true,
"CHILDINV": [
{
"Id": "3klAhq",
"C1NAME": "aaaaa aaaaa",
"C1BD": "2020-10-01",
"Gender": "Male",
"C1LEGAL": "CLIENT - You",
"C1PHYS": "CLIENT - You",
"C1VISIT": "CL-DISCR - Visitation at t~e Discretion of Client",
"FIELD8": "Lots of comments because I like to counent on stuff.",
"ItemNumber": 1
},
{
"Id": "3UM0Xn",
"C1NAME": "bbbbb bbbbb",
"C1BD": "2020-10-02",
"Gender": "Male",
"C1LEGAL": "CLIENT - You",
"C1PHYS": "CLIENT - You",
"C1VISIT": "CL-DISCR - Visitation at t~e Discretion of Client",
"FIELD8": "Lots of comments because I like to counent on stuff.",
"ItemNumber": 2
},
{
"Id": "2s3wBA",
"C1NAME": "ccccc ccccc",
"C1BD": "2020-10-03",
"Gender": "Male",
"C1LEGAL": "CLIENT - You",
"C1PHYS": "CLIENT - You",
"C1VISIT": "CL-DISCR - Visitation at t~e Discretion of Client",
"FIELD8": "Lots of comments because I like to counent on stuff.",
"ItemNumber": 3
},
{
"Id": "lhgNwf",
"C1NAME": "ddddd ddddd",
"C1BD": "2020-10-04",
"Gender": "Male",
"C1LEGAL": "CLIENT - You",
"C1PHYS": "CLIENT - You",
"C1VISIT": "CL-DISCR - Visitation at t~e Discretion of Client",
"FIELD8": "Lots of comments because I like to counent on stuff.",
"ItemNumber": 4
}
],
"CHILDINV_Minimum": 0,
"INCMECY": 35000,
"INCMESY": 35000,
"OWNHOME": true,
"JTRE": 350000,
"HOUSEOWNED": 200000,
"HOUSETITITLEE": "TICOMM - Tenancy in Common",
"SELLRES": true,
"JTCASH": 15000,
"JTINS": 15000,
"JTPTY": 65000,
"JTRET": 47000,
"BIRTHEXP": 28500,
"DOCUMENTS": [],
"AGREFEE": true,
"AGREFEE_Amount": 335,
"AGREFEE_QuantitySelected": 1,
"AGREFEE_Price": 365,
"WILL": false,
"SELFPROVED": false,
"PUBLICASST": false,
"Id": "1-3",
"INCMECY_IncrementBy": 1,
"INCMESY_IncrementBy": 1,
"JTRE_IncrementBy": 1,
"HOUSEOWNED_IncrementBy": 1,
"JTCASH_IncrementBy": 1,
"JTINS_IncrementBy": 1,
"JTPTY_IncrementBy": 1,
"JTRET_IncrementBy": 1,
"BIRTHEXP_IncrementBy": 1
}
}
Solution
OK, so this might seem daunting if you haven't been exposed to some of this, but I'll be honest, I only *barely* understand how XML works, and all I do know is that these bits and bobs are pure magic.
This has heavy thanks to @JohnLiu (hope that's the right userID!) whom I pilfered this a while back for some other stuff (on here, and elsewhere).
XML & XPATH
So, this uses XML to parse the JSON data, and convert it into XML data. As far as I can fathom it, the XML data can be either an array or an object, but it still finds a way to get what you need.
You'll see two expressions used more than once below, the columnName if() statement, and the columnValue xpath() statement. I'm utilising these generic statements to grab the header information from the various fields, and then equally grab the values from those fields.
The key part in both of them is item(), which in a Select or Filter action will always be referring to a generic individual item in the array that they are processing.
Field Name if() Expression (columnName)
This really just ensures that when the field name is extracted from the XML it is formatted correctly, accounting for potential issues with code in the name, or strange alphaNumeric strings.
if(startsWith(string(xpath(item(), 'name(/*)')), '_x003'), if(equals(length(string(xpath(item(), 'name(/*)'))), 7), substring(string(xpath(item(), 'name(/*)')), 5, 1), concat(substring(string(xpath(item(), 'name(/*)')), 5, 1), substring(string(xpath(item(), 'name(/*)')), 7))), string(xpath(item(), 'name(/*)')))
Field Value xpath() Expression (columnValue)
This is much simpler, and just grabs the value of a given field.
xpath(item(), 'string(//*)')
SELECT
You'll also note that in my initial flow, here, I'm using some vanilla Select actions, too. I'm doing this to separate out the logic because I know I'm not a genius(!), and to make the layout a little more obvious as to what goes where.
For the Kids' stuff, it's actually helpful that I've gone focused on this pass, when I post the more generic version, you'll be able to understand where the changes are, and why.
The Flow
As you can see, there's two branches working simultaneously, on the left you're gathering the generic data, and on the right the kids data.
Here's a deeper drill down into the flow:
OK, now on to the specifics.
General Data Side
This side took a while, as I was uhming and ah'ing about the most expedient way to put everything togther, mostly in the csvVAR at the end, but because of that, I had to keep reconsidering this part and re-testing.
The xpath() expression in that first select is:
xpath(xml(json(concat('{ "root": { "columns": ', string(variables('jsonInputVAR')?['body']), ' } }'))), '/root/columns/*')
Essentially, this is;
All that magic is then readable by the Select action, and the Map expressions can get to work on pulling what you really want from it.
From this data, it produces data like this:
[
{
"columnName": "FIRST",
"columnValue": "Harvey"
},
{
"columnName": "MIDDLE",
"columnValue": "Weinstein"
},
{
"columnName": "LAST",
"columnValue": "Wallbanger"
},
{
"columnName": "MAIDEN",
"columnValue": "Smith"
} ...
Then the rest is quite simply a filter to remove that CHILDINV part, and then producing the arrays that I'll generate the general data headers (SelectHeaders) and data (SelectValues) from.
The Kids Side
That initial variables() call is referring directly to the CHILDINV field in the original data.
variables('jsonInputVAR')?['body']?['CHILDINV']
Here you can see the if() statement spelled out, and similar xpath() expressions that were used on the other side, initially. However the big deal on this side is the part that you had issues with, iterating the CHILDINV data.
Looking at that first SelectKidsData action, you'll see field/column names defined and values also. Every single piece of dynamic data in that set is simply done with:
item()?['FIELD_NAME']
Where item()?['FIELD_NAME'] is one of the names presented in the CHILDINV array, like item()?['Gender'].
So, you can see, your ItemNumber field is SUPER useful here, by looking at example data from what it spouts out:
[
{
"C1ID": "3klAhq",
"C1NAME": "aaaaa aaaaa",
"C1BD": "2020-10-01",
"C1SEX": "Male",
"C1LEGAL": "CLIENT - You",
"C1PHYS": "CLIENT - You",
"C1VISIT": "CL-DISCR - Visitation at t~e Discretion of Client",
"C1NOTES": "Lots of comments because I like to counent on stuff.",
"C1NUM": 1
},
{
"C2ID": "3UM0Xn",
"C2NAME": "bbbbb bbbbb",
"C2BD": "2020-10-02",
"C2SEX": "Male",
"C2LEGAL": "CLIENT - You",
"C2PHYS": "CLIENT - You",
"C2VISIT": "CL-DISCR - Visitation at t~e Discretion of Client",
"C2NOTES": "Lots of comments because I like to counent on stuff.",
"C2NUM": 2
}...
CSV Creation
Finally, this feels like the most straightforward part, the string variable just pulls all the data together into one place, and formats it for CSV with each CSV entry encased in speech marks just in case there are commas in the data that's sent through.
HEADERS
join(split(first(split(last(split(string(body('SelectHeaders')), '[{"columnName":"')), '"}]')), '"},{"columnName":"'), '","')
join(split(first(split(last(split(string(body('SelectKidsHeaders')), '[{"columnName":"')), '"}]')), '"},{"columnName":"'), '","')
DATA
join(split(first(split(last(split(string(body('SelectValues')), '[{"columnValue":"')), '"}]')), '"},{"columnValue":"'), '","')
join(split(first(split(last(split(string(body('SelectKidsValues')), '[{"columnValue":"')), '"}]')), '"},{"columnValue":"'), '","')
Each of the four parts in the csvVAR action are basically the same, just referring to different sources, you could do it all at separate points if you'd rather, and pool it here. Essentially each expression works thusly:
The rest of the csvVAR action is just framing that data with a couple more speech marks and commas!
That should be it!
EDIT - I'm going to leave optimising the Kids' side for now as it's both late, and I need to understand how to pull a value out of that XML!
You can do it easily with a select action. Take a look at this screenshot:
To make it simple for you to recreate, I copied my actions into a Scope. If you would like a working demonstration at your end, simply do the following:
Here is the code for you to copy:
{"id":"936a697a-e46e-41e6-b201-2d05-01ede363","brandColor":"#8C3900","connectionReferences":{},"connectorDisplayName":"Control","icon":"data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMzIiIGhlaWdodD0iMzIiIHZlcnNpb249IjEuMSIgdmlld0JveD0iMCAwIDMyIDMyIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPg0KIDxwYXRoIGQ9Im0wIDBoMzJ2MzJoLTMyeiIgZmlsbD0iIzhDMzkwMCIvPg0KIDxwYXRoIGQ9Im04IDEwaDE2djEyaC0xNnptMTUgMTF2LTEwaC0xNHYxMHptLTItOHY2aC0xMHYtNnptLTEgNXYtNGgtOHY0eiIgZmlsbD0iI2ZmZiIvPg0KPC9zdmc+DQo=","isTrigger":false,"operationName":"Scope","operationDefinition":{"type":"Scope","actions":{"Compose":{"type":"Compose","inputs":{"body":{"FIRST":"Harvey","MIDDLE":"Weinstein","LAST":"Wallbanger","MAIDEN":"Smith","DOB":"2001-01-01","CLASS":"CLI0LGMR - Legally Married","ADDl":"123 Sesame Street","LABEL2":"Apartment 7","LABEL4":"R.R. #2","CITY":"Trenton","ZIP":"K8V 1R6","Province":"Ontarlo","JURISDICr":"4 years","PRIVEMAIL":true,"EMAIL":"glenn@xasdasd.ca","PREFEMAIL":true,"PHONE4":"343-263-4643","PRIVPHONEC":true,"DAYPHONE":"613-966-777'","PRIVPHONE":true,"COMPANY":"KDA Law","REFERREDBY":"Jeff van de K2e-t","FIRST2":"Karen","MIDDLE2":"Snarf","LAST2":"Wallbanger","MAIDEN2":"deKaren","DOB2":"1998-01-24","CLASS2":"OPP-LG1 - Legally Married","ADD12":"123 Complaint Bouleva~d","LABEL22":"Apartment 2","LABEL42":"R.R. 17","City2":"Picton","Province2":"Ontario","ZIP2":"K7L 2E4","JURISDICT2":"3 months","OpposingPartysEmailAddress":"ka~e~Sw'~ine~.ccr~","PHONE42":"613-966-7771","DAYPHONE2":"647-265-8597","COMPANY2":"Nestle Quinte West","COUNTY":"Hastings","COHABITATE":true,"DATEMARRY":"2020-01-16","STATEMARRY":"Ontario","DATESEP":"2021-08-02","STATESEP":"Ontario","FIELDl":"Belleville","PRENUPTUAL":false,"ISFATHER":true,"ISMOTHER":true,"DOM":"2000-01-27","DIVDATE":"2004-07-29","CHILDREN":true,"ISRELATED":true,"CHILDINV":[{"Id":"3klAhq","C1NAME":"aaaaa aaaaa","C1BD":"2020-10-01","Gender":"Male","C1LEGAL":"CLIENT - You","C1PHYS":"CLIENT - You","C1VISIT":"CL-DISCR - Visitation at t~e Discretion of Client","FIELD8":"Lots of comments because I like to counent on stuff.","ItemNumber":1},{"Id":"3UM0Xn","C1NAME":"bbbbb bbbbb","C1BD":"2020-10-02","Gender":"Male","C1LEGAL":"CLIENT - You","C1PHYS":"CLIENT - You","C1VISIT":"CL-DISCR - Visitation at t~e Discretion of Client","FIELD8":"Lots of comments because I like to counent on stuff.","ItemNumber":2},{"Id":"2s3wBA","C1NAME":"ccccc ccccc","C1BD":"2020-10-03","Gender":"Male","C1LEGAL":"CLIENT - You","C1PHYS":"CLIENT - You","C1VISIT":"CL-DISCR - Visitation at t~e Discretion of Client","FIELD8":"Lots of comments because I like to counent on stuff.","ItemNumber":3},{"Id":"lhgNwf","C1NAME":"ddddd ddddd","C1BD":"2020-10-04","Gender":"Male","C1LEGAL":"CLIENT - You","C1PHYS":"CLIENT - You","C1VISIT":"CL-DISCR - Visitation at t~e Discretion of Client","FIELD8":"Lots of comments because I like to counent on stuff.","ItemNumber":4}],"CHILDINV_Minimum":0,"INCMECY":35000,"INCMESY":35000,"OWNHOME":true,"JTRE":350000,"HOUSEOWNED":200000,"HOUSETITITLEE":"TICOMM - Tenancy in Common","SELLRES":true,"JTCASH":15000,"JTINS":15000,"JTPTY":65000,"JTRET":47000,"BIRTHEXP":28500,"DOCUMENTS":[],"AGREFEE":true,"AGREFEE_Amount":335,"AGREFEE_QuantitySelected":1,"AGREFEE_Price":365,"WILL":false,"SELFPROVED":false,"PUBLICASST":false,"Id":"1-3","INCMECY_IncrementBy":1,"INCMESY_IncrementBy":1,"JTRE_IncrementBy":1,"HOUSEOWNED_IncrementBy":1,"JTCASH_IncrementBy":1,"JTINS_IncrementBy":1,"JTPTY_IncrementBy":1,"JTRET_IncrementBy":1,"BIRTHEXP_IncrementBy":1}},"runAfter":{}},"Select":{"type":"Select","inputs":{"from":"@outputs('Compose')['BODY']['CHILDINV']","select":{"Id":"@item()['Id']","C1NAME":"@item()['C1NAME']","C1BD":"@formatDateTime(item()['C1BD'], 'dd-MM-yyyy')","Gender":"@item()['Gender']","C1LEGAL":"@substring(item()['C1LEGAL'],0, 6)","C1PHYS":"@substring(item()['C1PHYS'],0, 6)","C1VISIT":"@substring(item()['C1VISIT'],0, 8)","FIELD8":"@item()['FIELD8']","ItemNumber":"@item()['ItemNumber']"}},"runAfter":{"Compose":["Succeeded"]},"description":"outputs('Compose')['BODY']['CHILDINV']"},"Create_CSV_table":{"type":"Table","inputs":{"from":"@body('Select')","format":"CSV"},"runAfter":{"Select":["Succeeded"]},"description":"body('Select')"}},"runAfter":{}}}
See how you get on and let me know if you need further guidance.
Blog: tachytelic.net
YouTube: https://www.youtube.com/c/PaulieM/videos
If I answered your question, please accept it as a solution 😘
He needs to iterate the children column names, though, @Paulie78 ... but my solution can be slimmed down a bit still (for example I'd put a removeProperty() in the xpath() on the main Select action and remove the filter action) but for now it shows the logic. I was wondering if the range trick would help there, and it would, but only if he hadn't already defined the child number.
Anyway, yeah, on the iterative headings: So if there are four children (like the example data I put above) then there will be four additional sets of nine columns in the CSV. Nine columns for each child.
"C1ID","C1NAME","C1BD","C1SEX","C1LEGAL","C1PHYS","C1VISIT","C1NOTES","C1NUM","C2ID","C2NAME","C2BD","C2SEX","C2LEGAL","C2PHYS","C2VISIT","C2NOTES","C2NUM","C3ID","C3NAME","C3BD","C3SEX","C3LEGAL","C3PHYS","C3VISIT","C3NOTES","C3NUM","C4ID","C4NAME","C4BD","C4SEX","C4LEGAL","C4PHYS","C4VISIT","C4NOTES","C4NUM"
Wow...Lots to take in there, but I'm up for the challenge! I will take a look at it in more detail later today, and try to get it working tonight - I'll keep you posted!
That's the real trick...It doesn't really matter what the data is called in the schema or the flow, all that matters is that it comes out in the CSV with the right header row above it, and the right data field name.
Cheers, @ArchieGoodwin, I've definitely got it working with the sample data above, I'm just working on slimming it down some.
If you want to make it less cumbersome in your head, just look at the parts where I say what to do, rather than the explanations. If, like me, you're a 'learn by doing' person (kineathetic learner!) then by implementing it you'll probably get to the understanding (or maybe fiddling around with a copy).
With regards to the slimming ... Like I say, removing the property negates the need for the filter action, which is good, and I think I'm on to removing the need for the final action and changing that to a generic CSV, just playing with that child data, and some of Paulie's tricks from elsewhere!
I slightly misunderstood, but you can still do it easily in one action:
I haven't done every field, but enough to get you started off. Output produced from this is:
FIRST,MIDDLE,LAST,CHILD1_ID,CHILD1_NAME,CHILD2_ID,CHILD2_NAME
Harvey,Weinstein,Wallbanger,3klAhq,aaaaa aaaaa,3UM0Xn,bbbbb bbbbb
This was my input JSON:
{
"FIRST": "Harvey",
"MIDDLE": "Weinstein",
"LAST": "Wallbanger",
"MAIDEN": "Smith",
"DOB": "2001-01-01",
"CLASS": "CLI0LGMR - Legally Married",
"ADDl": "123 Sesame Street",
"LABEL2": "Apartment 7",
"LABEL4": "R.R. #2",
"CITY": "Trenton",
"ZIP": "K8V 1R6",
"Province": "Ontarlo",
"JURISDICr": "4 years",
"PRIVEMAIL": true,
"EMAIL": "glenn@xasdasd.ca",
"PREFEMAIL": true,
"PHONE4": "343-263-4643",
"PRIVPHONEC": true,
"DAYPHONE": "613-966-777'",
"PRIVPHONE": true,
"COMPANY": "KDA Law",
"REFERREDBY": "Jeff van de K2e-t",
"FIRST2": "Karen",
"MIDDLE2": "Snarf",
"LAST2": "Wallbanger",
"MAIDEN2": "deKaren",
"DOB2": "1998-01-24",
"CLASS2": "OPP-LG1 - Legally Married",
"ADD12": "123 Complaint Bouleva~d",
"LABEL22": "Apartment 2",
"LABEL42": "R.R. 17",
"City2": "Picton",
"Province2": "Ontario",
"ZIP2": "K7L 2E4",
"JURISDICT2": "3 months",
"OpposingPartysEmailAddress": "ka~e~Sw'~ine~.ccr~",
"PHONE42": "613-966-7771",
"DAYPHONE2": "647-265-8597",
"COMPANY2": "Nestle Quinte West",
"COUNTY": "Hastings",
"COHABITATE": true,
"DATEMARRY": "2020-01-16",
"STATEMARRY": "Ontario",
"DATESEP": "2021-08-02",
"STATESEP": "Ontario",
"FIELDl": "Belleville",
"PRENUPTUAL": false,
"ISFATHER": true,
"ISMOTHER": true,
"DOM": "2000-01-27",
"DIVDATE": "2004-07-29",
"CHILDREN": true,
"ISRELATED": true,
"CHILDINV": [
{
"Id": "3klAhq",
"C1NAME": "aaaaa aaaaa",
"C1BD": "2020-10-01",
"Gender": "Male",
"C1LEGAL": "CLIENT - You",
"C1PHYS": "CLIENT - You",
"C1VISIT": "CL-DISCR - Visitation at t~e Discretion of Client",
"FIELD8": "Lots of comments because I like to counent on stuff.",
"ItemNumber": 1
},
{
"Id": "3UM0Xn",
"C1NAME": "bbbbb bbbbb",
"C1BD": "2020-10-02",
"Gender": "Male",
"C1LEGAL": "CLIENT - You",
"C1PHYS": "CLIENT - You",
"C1VISIT": "CL-DISCR - Visitation at t~e Discretion of Client",
"FIELD8": "Lots of comments because I like to counent on stuff.",
"ItemNumber": 2
},
{
"Id": "2s3wBA",
"C1NAME": "ccccc ccccc",
"C1BD": "2020-10-03",
"Gender": "Male",
"C1LEGAL": "CLIENT - You",
"C1PHYS": "CLIENT - You",
"C1VISIT": "CL-DISCR - Visitation at t~e Discretion of Client",
"FIELD8": "Lots of comments because I like to counent on stuff.",
"ItemNumber": 3
},
{
"Id": "lhgNwf",
"C1NAME": "ddddd ddddd",
"C1BD": "2020-10-04",
"Gender": "Male",
"C1LEGAL": "CLIENT - You",
"C1PHYS": "CLIENT - You",
"C1VISIT": "CL-DISCR - Visitation at t~e Discretion of Client",
"FIELD8": "Lots of comments because I like to counent on stuff.",
"ItemNumber": 4
}
],
"CHILDINV_Minimum": 0,
"INCMECY": 35000,
"INCMESY": 35000,
"OWNHOME": true,
"JTRE": 350000,
"HOUSEOWNED": 200000,
"HOUSETITITLEE": "TICOMM - Tenancy in Common",
"SELLRES": true,
"JTCASH": 15000,
"JTINS": 15000,
"JTPTY": 65000,
"JTRET": 47000,
"BIRTHEXP": 28500,
"DOCUMENTS": [],
"AGREFEE": true,
"AGREFEE_Amount": 335,
"AGREFEE_QuantitySelected": 1,
"AGREFEE_Price": 365,
"WILL": false,
"SELFPROVED": false,
"PUBLICASST": false,
"Id": "1-3",
"INCMECY_IncrementBy": 1,
"INCMESY_IncrementBy": 1,
"JTRE_IncrementBy": 1,
"HOUSEOWNED_IncrementBy": 1,
"JTCASH_IncrementBy": 1,
"JTINS_IncrementBy": 1,
"JTPTY_IncrementBy": 1,
"JTRET_IncrementBy": 1,
"BIRTHEXP_IncrementBy": 1
}
This is how you do it:
Create a select action. For the from, just literally type [0]
For the Header records, just access them directly, examples:
outputs('Compose')['FIRST']
outputs('Compose')['MIDDLE']
outputs('Compose')['LAST']
For the array elements, as you know there will never be more than ten, you can just build columns for each one. Examples:
outputs('Compose')['CHILDINV']?[0]['Id']
outputs('Compose')['CHILDINV']?[0]['C1NAME']
outputs('Compose')['CHILDINV']?[1]['Id']
outputs('Compose')['CHILDINV']?[1]['C1NAME']
The above give the ID and name for child one and two, you would just continue to populate the select and then you'd have the whole thing on one line of a CSV.
As before, I have copied it into a scope for you so you can see how it works:
{"id":"8a8a92db-c996-4c42-bd8f-4367-c314d244","brandColor":"#8C3900","connectionReferences":{},"connectorDisplayName":"Control","icon":"data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMzIiIGhlaWdodD0iMzIiIHZlcnNpb249IjEuMSIgdmlld0JveD0iMCAwIDMyIDMyIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPg0KIDxwYXRoIGQ9Im0wIDBoMzJ2MzJoLTMyeiIgZmlsbD0iIzhDMzkwMCIvPg0KIDxwYXRoIGQ9Im04IDEwaDE2djEyaC0xNnptMTUgMTF2LTEwaC0xNHYxMHptLTItOHY2aC0xMHYtNnptLTEgNXYtNGgtOHY0eiIgZmlsbD0iI2ZmZiIvPg0KPC9zdmc+DQo=","isTrigger":false,"operationName":"Scope","operationDefinition":{"type":"Scope","actions":{"Compose":{"type":"Compose","inputs":{"FIRST":"Harvey","MIDDLE":"Weinstein","LAST":"Wallbanger","MAIDEN":"Smith","DOB":"2001-01-01","CLASS":"CLI0LGMR - Legally Married","ADDl":"123 Sesame Street","LABEL2":"Apartment 7","LABEL4":"R.R. #2","CITY":"Trenton","ZIP":"K8V 1R6","Province":"Ontarlo","JURISDICr":"4 years","PRIVEMAIL":true,"EMAIL":"glenn@xasdasd.ca","PREFEMAIL":true,"PHONE4":"343-263-4643","PRIVPHONEC":true,"DAYPHONE":"613-966-777'","PRIVPHONE":true,"COMPANY":"KDA Law","REFERREDBY":"Jeff van de K2e-t","FIRST2":"Karen","MIDDLE2":"Snarf","LAST2":"Wallbanger","MAIDEN2":"deKaren","DOB2":"1998-01-24","CLASS2":"OPP-LG1 - Legally Married","ADD12":"123 Complaint Bouleva~d","LABEL22":"Apartment 2","LABEL42":"R.R. 17","City2":"Picton","Province2":"Ontario","ZIP2":"K7L 2E4","JURISDICT2":"3 months","OpposingPartysEmailAddress":"ka~e~Sw'~ine~.ccr~","PHONE42":"613-966-7771","DAYPHONE2":"647-265-8597","COMPANY2":"Nestle Quinte West","COUNTY":"Hastings","COHABITATE":true,"DATEMARRY":"2020-01-16","STATEMARRY":"Ontario","DATESEP":"2021-08-02","STATESEP":"Ontario","FIELDl":"Belleville","PRENUPTUAL":false,"ISFATHER":true,"ISMOTHER":true,"DOM":"2000-01-27","DIVDATE":"2004-07-29","CHILDREN":true,"ISRELATED":true,"CHILDINV":[{"Id":"3klAhq","C1NAME":"aaaaa aaaaa","C1BD":"2020-10-01","Gender":"Male","C1LEGAL":"CLIENT - You","C1PHYS":"CLIENT - You","C1VISIT":"CL-DISCR - Visitation at t~e Discretion of Client","FIELD8":"Lots of comments because I like to counent on stuff.","ItemNumber":1},{"Id":"3UM0Xn","C1NAME":"bbbbb bbbbb","C1BD":"2020-10-02","Gender":"Male","C1LEGAL":"CLIENT - You","C1PHYS":"CLIENT - You","C1VISIT":"CL-DISCR - Visitation at t~e Discretion of Client","FIELD8":"Lots of comments because I like to counent on stuff.","ItemNumber":2},{"Id":"2s3wBA","C1NAME":"ccccc ccccc","C1BD":"2020-10-03","Gender":"Male","C1LEGAL":"CLIENT - You","C1PHYS":"CLIENT - You","C1VISIT":"CL-DISCR - Visitation at t~e Discretion of Client","FIELD8":"Lots of comments because I like to counent on stuff.","ItemNumber":3},{"Id":"lhgNwf","C1NAME":"ddddd ddddd","C1BD":"2020-10-04","Gender":"Male","C1LEGAL":"CLIENT - You","C1PHYS":"CLIENT - You","C1VISIT":"CL-DISCR - Visitation at t~e Discretion of Client","FIELD8":"Lots of comments because I like to counent on stuff.","ItemNumber":4}],"CHILDINV_Minimum":0,"INCMECY":35000,"INCMESY":35000,"OWNHOME":true,"JTRE":350000,"HOUSEOWNED":200000,"HOUSETITITLEE":"TICOMM - Tenancy in Common","SELLRES":true,"JTCASH":15000,"JTINS":15000,"JTPTY":65000,"JTRET":47000,"BIRTHEXP":28500,"DOCUMENTS":[],"AGREFEE":true,"AGREFEE_Amount":335,"AGREFEE_QuantitySelected":1,"AGREFEE_Price":365,"WILL":false,"SELFPROVED":false,"PUBLICASST":false,"Id":"1-3","INCMECY_IncrementBy":1,"INCMESY_IncrementBy":1,"JTRE_IncrementBy":1,"HOUSEOWNED_IncrementBy":1,"JTCASH_IncrementBy":1,"JTINS_IncrementBy":1,"JTPTY_IncrementBy":1,"JTRET_IncrementBy":1,"BIRTHEXP_IncrementBy":1},"runAfter":{}},"Hope__you":{"type":"Compose","inputs":"Enjoy :D","runAfter":{"Create_CSV_table":["Succeeded"]}},"Select":{"type":"Select","inputs":{"from":[0],"select":{"FIRST":"@outputs('Compose')['FIRST']","MIDDLE":"@outputs('Compose')['MIDDLE']","LAST":"@outputs('Compose')['LAST']","CHILD1_ID":"@outputs('Compose')['CHILDINV']?[0]['Id']","CHILD1_NAME":"@outputs('Compose')['CHILDINV']?[0]['C1NAME']","CHILD2_ID":"@outputs('Compose')['CHILDINV']?[1]['Id']","CHILD2_NAME":"@outputs('Compose')['CHILDINV']?[1]['C1NAME']"}},"runAfter":{"Compose":["Succeeded"]}},"Create_CSV_table":{"type":"Table","inputs":{"from":"@body('Select')","format":"CSV"},"runAfter":{"Select":["Succeeded"]}}},"runAfter":{}}}
Don't you still have to manually create those keys in the select, mate? When there's less than ten that's going to create pointless columns, no?
Yeah, but it is a one off operation. You'd want the column names to be static, so that your import was always consistent. You would still want a column for Child10_Name, even if there was no child 10. It's the whole operation wrapped in a single API action, so it will finish instantly and it can't get any more efficient than that.
What's the issue with manually creating the keys? Did I miss something?
So, this is closer - but I took a look at the scope, ran it, and the output appeared to be the same as your earlier answer above.
I need the output to actually be two rows, with the first row being the "header" row, and the second one being the data row.
It makes sense to me, how to compose the header row and then pull the data (not sure how you separate the two rows)?
After all the planning and preparing, the annual Microsoft Power Platform Conference is finally here! We are excited to see so many of our community in Las Vegas this week. To help make sure you don't miss any of the workshops, sessions, and events we have planned, make sure to check out this handy Community One-Sheet, and download the pdf today! Make sure to stop by the Community Lounge to meet @hugobernier, @EricArcher, @heaher_italent, and @AshleyFelts from our team!
Join us for the first-ever the Biz Apps Community User Group meeting live from the Power Platform Conference! This one hour user group meeting is all about discovering the value and benefits of User Groups! Discover how you can find a group in your local area or about specific topics where you can learn new skills and meet like-minded people as a user group member. Hear from User Group leaders about why they do what they do and what resources they receive to help them succeed as community ambassadors. If you have never attended a User Group meeting before, this will be a great introduction! We hope you are inspired to find a group that meets your unique interests! October 5th at 2:15 pm Pacific time If you're attending #MPPC23 in Las Vegas, join us in person! Find out more here: https://powerplatformconf.com/#!/session/Biz%20Apps%20Community%20User%20Group%20Meeting%20-%20Live%20from%20MPPC/6172 Not at MPPC23? Attend vvirtually by registering here: https://aka.ms/MPPCusergroupmeeting2023 If you can't attend this meeting live, don't worry! We will record this meeting and share it with the Community at powerusers.microsoft.com
We are excited to kick off our new #TuesdayTIps series, "Back to Basics." This weekly series is our way of helping the amazing members of our community--both new members and seasoned veterans--learn and grow in how to best engage in the community! Each Tuesday, we will feature new areas of content that will help you best understand the community--from ranking and badges to profile avatars, from Super Users to blogging in the community. Our hope is that this information will help each of our community members grow in their experience with Power Platform, with the community, and with each other! This Week's Tips: Account Support: Changing Passwords, Changing Email Addresses or Usernames, "Need Admin Approval," Etc.Wondering how to get support for your community account? Check out the details on these common questions and more. Just follow the link below for articles that explain it all.Community Account Support - Power Platform Community (microsoft.com) All About GDPR: How It Affects Closing Your Community Account (And Why You Should Think Twice Before You Do)GDPR, the General Data Protection Regulation (GDPR), took effect May 25th 2018. A European privacy law, GDPR imposes new rules on companies and other organizations offering goods and services to people in the European Union (EU), or that collect and analyze data tied to EU residents. GDPR applies no matter where you are located, and it affects what happens when you decide to close your account. Read the details here:All About GDPR - Power Platform Community (microsoft.com) Getting to Know You: Setting Up Your Community Profile, Customizing Your Profile, and More.Your community profile helps other members of the community get to know you as you begin to engage and interact. Your profile is a mirror of your activity in the community. Find out how to set it up, change your avatar, adjust your time zone, and more. Click on the link below to find out how:Community Profile, Time Zone, Picture (Avatar) & D... - Power Platform Community (microsoft.com) That's it for this week. Tune in for more Tuesday Tips next Tuesday and join the community as we get "Back to Basics."
Are you attending the Microsoft Power Platform Conference 2023 in Las Vegas? If so, we invite you to join us for the MPPC's Got Power Talent Show! Our talent show is more than a show—it's a grand celebration of connection, inspiration, and shared journeys. Through stories, skills, and collective experiences, we come together to uplift, inspire, and revel in the magic of our community's diverse talents. This year, our talent event promises to be an unforgettable experience, echoing louder and brighter than anything you've seen before. We're casting a wider net with three captivating categories: Demo Technical Solutions: Show us your Power Platform innovations, be it apps, flows, chatbots, websites or dashboards... Storytelling: Share tales of your journey with Power Platform. Hidden Talents: Unveil your creative side—be it dancing, singing, rapping, poetry, or comedy. Let your talent shine! Got That Special Spark? A Story That Demands to Be Heard? Your moment is now! Sign up to Showcase Your Brilliance: https://aka.ms/MPPCGotPowerSignUp Deadline for submissions: Thursday, Sept 28th How It Works: Submit this form to sign up: https://aka.ms/MPPCGotPowerSignUp We'll contact you if you're selected. Get ready to be onstage! The Spotlight is Yours: Each participant has 3-5 minutes to shine, with insightful commentary from our panel of judges. We’re not just giving you a stage; we’re handing you the platform to make your mark. Be the Story We Tell: Your talents and narratives will not just entertain but inspire, serving as the bedrock for our community’s future stories and successes. Celebration, Surprises, and Connections: As the curtain falls, the excitement continues! Await surprise awards and seize the chance to mingle with industry experts, Microsoft Power Platform leaders, and community luminaries. It's not just a show; it's an opportunity to forge connections and celebrate shared successes. Event Details: Date and Time: Wed Oct 4th, 6:30-9:00PM Location: MPPC23 at the MGM Grand, Las Vegas, NV, USA
The Reading Dynamics 365 and Power Platform User Group is a community-driven initiative that started in September 2022. It has quickly earned recognition for its enthusiastic leadership and resilience in the face of challenges. With a focus on promoting learning and networking among professionals in the Dynamics 365 and Power Platform ecosystem, the group has grown steadily and gained a reputation for its commitment to its members! The group, which had its inaugural event in January 2023 at the Microsoft UK Headquarters in Reading, has since organized three successful gatherings, including a recent social lunch. They maintain a regular schedule of four events per year, each attended by an average of 20-25 enthusiastic participants who enjoy engaging talks and, of course, pizza. The Reading User Group's presence is primarily spread through LinkedIn and Meetup, with the support of the wider community. This thriving community is managed by a dedicated team consisting of Fraser Dear, Tim Leung, and Andrew Bibby, who serves as the main point of contact for the UK Dynamics 365 and Power Platform User Groups. Andrew Bibby, an active figure in the Dynamics 365 and Power Platform community, nominated this group due to his admiration for the Reading UK User Group's efforts. He emphasized their remarkable enthusiasm and success in running the group, noting that they navigated challenges such as finding venues with resilience and smiles on their faces. Despite being a relatively new group with 20-30 members, they have managed to achieve high attendance at their meetings. The group's journey began when Fraser Dear moved to the Reading area and realized the absence of a user group catering to professionals in the Dynamics 365 and Power Platform space. He reached out to Andrew, who provided valuable guidance and support, allowing the Reading User Group to officially join the UK Dynamics 365 and Power Platform User Groups community. One of the group's notable achievements was overcoming the challenge of finding a suitable venue. Initially, their "home" was the Microsoft UK HQ in Reading. However, due to office closures, they had to seek a new location with limited time. Fortunately, a connection with Stephanie Stacey from Microsoft led them to Reading College and its Institute of Technology. The college generously offered them event space and support, forging a mutually beneficial partnership where the group promotes the Institute and encourages its members to support the next generation of IT professionals. With the dedication of its leadership team, the Reading Dynamics 365 and Power Platform User Group is poised to continue growing and thriving! Their story exemplifies the power of community-driven initiatives and the positive impact they can have on professional development and networking in the tech industry. As they move forward with their upcoming events and collaborations with Reading College, the group is likely to remain a valuable resource for professionals in the Reading area and beyond.
As the sun sets on the #SummerofSolutions Challenge, it's time to reflect and celebrate! The journey we embarked upon together was not just about providing answers – it was about fostering a sense of community, encouraging collaboration, and unlocking the true potential of the Power Platform tools. From the initial announcement to the final week's push, the Summer of Solutions Challenge has been a whirlwind of engagement and growth. It was a call to action for every member of our Power Platform community, urging them to contribute their expertise, engage in discussions, and elevate collective knowledge across the community as part of the low-code revolution. Reflecting on the Impact As the challenge ends, it's essential to reflect on the impact it’s had across our Power Platform communities: Community Resilience: The challenge demonstrated the resilience of our community. Despite geographical distances and diverse backgrounds, we came together to contribute, learn, and collaborate. This resilience is the cornerstone of our collective strength.Diverse Expertise: The solutions shared during the challenge underscore the incredible expertise within our community. From intricate technical insights to creative problem-solving, our members showcased their diverse skill sets, enhancing our community's depth.Shared Learning: Solutions spurred shared learning. They provided opportunities for members to grasp new concepts, expand their horizons, and uncover the Power Platform tools' untapped potential. This learning ripple effect will continue to shape our growth. Empowerment: Solutions empowered community members. They validated their knowledge, boosted their confidence, and highlighted their contributions. Each solution shared was a step towards personal and communal empowerment. We are proud and thankful as we conclude the Summer of Solutions Challenge. The challenge showed the potential of teamwork, the benefit of knowledge-sharing, and the resilience of our Power Platform community. The solutions offered by each member are more than just answers; they are the expression of our shared commitment to innovation, growth, and progress! Drum roll, Please... And now, without further ado, it's time to announce the winners who have risen above the rest in the Summer of Solutions Challenge! These are the top community users and Super Users who have not only earned recognition but have become beacons of inspiration for us all. Power Apps Community: Community User Winner: @SpongYe Super User Winner: Pending Acceptance Power Automate Community: Community User Winner: @trice602 Super User Winner: @Expiscornovus Power Virtual Agents Community: Community User Winner: Pending AcceptanceSuper User: Pending Acceptance Power Pages Community: Community User Winner: @OOlashyn Super User Winner: @ChristianAbata We are also pleased to announced two additional tickets that we are awarding to the Overall Top Solution providers in the following communities: Power Apps: @LaurensM Power Automate: @ManishSolanki Thank you for making this challenge a resounding success. Your participation has reaffirmed the strength of our community and the boundless potential that lies within each of us. Let's keep the spirit of collaboration alive as we continue on this incredible journey in Power Platform together.Winners, we will see you in Vegas! Every other amazing solutions superstar, we will see you in the Community!Congratulations, everyone!
User | Count |
---|---|
66 | |
35 | |
34 | |
30 | |
29 |
User | Count |
---|---|
79 | |
72 | |
68 | |
51 | |
50 |