cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
wskinnermctc
Memorable Member
Memorable Member

When Excel first row has blank date all remaining row dates will be Serial instead of ISO 8601

Excel Dates Changed to Serial Instead of ISO 8601 Due to First Row In Table Blank

 

I have been using the API Batch upload method to get data out of an excel table and into a SharePoint list. I was having an issue with the date conversion after the List Rows in Excel Table being correctly set to ISO 8601.

I did some testing, and it seems like if the first row of the table has a blank in the date column then it will cause the entire column to read and converted to Serial.

I can't guarantee that the first row in my data will always be filled in the date column. Why does Power Automate not recognize the rest of the fields in the same column with the ISO 8601 setting?

 

I’m using the Batch Create SharePoint list items Batch Update SharePoint List With External Data  , and do not have an issue with it working. I have made it work and have it running with Excel and Dataverse tables. I just noticed this date issue and do not understand why the order of the dates in the excel table impact how Power Automate reads the column even with the setting as ISO 8601.

 

The first test I had all date fields filled and the date was converted to UTC as power automate normally does.

The second test I deleted the date fields from the top row in two of the columns and it made the remaining rows Serial.

 

Example 1 - All Date Fields Filled

 

The source Excel table is a list of 5 employees with 3 different date columns.

Excel Source Example 1 - All DatesExcel Source Example 1 - All Dates

 

All of the rows are completely filled in and the flow to batch generate and upload runs without an issue. I'm attaching outputs of the test flow in the two steps of the flow "Generate SPData" and "SendBatch". The Generate SPData step is an array that combines all of the data. The SendBatch is the actual Send HTTP Request to Sharepoint that is what posts the data to the SharePoint list. The array is easier to read since it shows what the data is that is being sent within the batch upload. The array is where you can see the formatting of the datetime values. The outputs of the BatchUpload does not give a lot of detail, but it does show if the posting was successful via a status code.

 

Example 1 Results Generate SPDataExample 1 Results Generate SPData

 

All of the datetime fields in the Generate SPData are in the UTC format that was done by the settings in the Get List Rows step.

 

Example 1 Results BatchUploadExample 1 Results BatchUploadExample 1 Results SharePoint ListExample 1 Results SharePoint List

 

 

 

 

 

The BatchUpload outputs are difficult to read, but it does show all 5 of the items were successfully posted. The SharePoint List contains all of the items and date fields when the flow is completed.

 

 

 

 

 

 

 

Example 2 - Delete Fields in First Row of Excel table

 

I used the exact same table and flow as the first example but the only difference is I deleted the dates out of the first row for 2 of the 3 datetime columns.

Example 2 Excel Source TableExample 2 Excel Source Table

None of the rows are successful in uploading from the flow because all of the dates are converted to Serial instead of ISO 8601 due to the first row being blank. I'm attaching the outputs of the Generate SPData and it clearly shows the first row has "" for the blank datetime columns and the last column that was filled is in the UTC format from the Get List settings ISO 8601. 

Looking further down the outputs the rest of the dates are now in Serial number format.

 

Example 2 Results Generate SPDataExample 2 Results Generate SPData

All of the rows failed to upload in the batch update (the first row failed because the blanks can't be sent to SharePoint in a datetime field). The last 4 rows failed because they were in Serial format that can't be sent to SharePoint. The output of the SendBatch shows the errors for each item.

  • Error:{“code”:”-1, Microsoft.SharePoint.Client.InvalidClientQueryException”,
  • Message{“value”: “Cannot convert a primitive value to the expected type ‘Edm.DateTime’. See the inner exception for more details.”
  • StatusCode: 400

Example 2 Results SendBatchExample 2 Results SendBatch

 

Other Attempts:

 

I tried this while using a if(empty(null expression to replace the first blank row with null instead of "" and all the remaining dates were still in Serial format. I also tried a more standard Apply to Each and Create Item in SharePoint instead of the batch upload and none of the items were created since the dates were still in Serial format. (The error message for apply to each was Status 400 "

String was not recognized as a valid DateTime").
 

Conclusion:

 

The order of the dates in the Excel table seem to impact how Power Automate reads the type of the column even when the setting is set to ISO 8601. If the first row is blank in the date time field then the remaining rows are read as Serial.

 

If you have any suggestions or ideas about why this happens please let me know.

 

 

Batch Upload Reference:

The steps I am using came from @takolota and his instructions and video. They have been a big help! I'm posting pictures of the overall flow here for reference to my flow on this post.

Power Automate Cookbook Batch Update SharePoint List With External Data 

Tachytelic.net 2021/06 Power Automate Flow Batch Create Sharepoint List Items 

 

Batch Upload  Flow OverviewBatch Upload Flow OverviewBatch Upload Flow Detail p1 of 4Batch Upload Flow Detail p1 of 4Batch Upload Flow Detail p2 of 4Batch Upload Flow Detail p2 of 4Batch Upload Flow Detail p3 of 4Batch Upload Flow Detail p3 of 4Batch Upload Flow Detail p4 of 4Batch Upload Flow Detail p4 of 4

 

1 ACCEPTED SOLUTION

Accepted Solutions
wskinnermctc
Memorable Member
Memorable Member

I have a couple of correction steps for when the dates convert to Serial due to first row blank. I'll use expressions to convert the date numbers like @takolota suggested. However, the correction steps lead to a follow-up problem that requires additional changes to the overall datetime format of the Get List Rows step. 

I realize these correction steps aren't anything new and there are dozens of pages referring to these; however, I am going to have a problem in another flow and I want to be able to reference this post.

 

Correction Step 1 - Replace blank date fields with 'null' by using expression If(empty([Date]),null,[Date])

 

The first issue is that SharePoint can’t accept double quotes blank value for a datetime field. SharePoint can accept a blank so long as it has the word null to represent the blank data field. So using the empty() expression will check if the field is double quote “” blank and return a result of true if it is.

Combine the empty() expression with the if() expression to say If the date is empty then return ‘null’ else just return the date field.

if(empty(item?['Birth Date']),null,item()?['Birth Date])

 

Correction Step 1 Detail Generate SPDataCorrection Step 1 Detail Generate SPData

I’m attaching a screenshots of the results of a test flow showing the inputs and outputs of the step Generate SPData. When running the flow using the if(empty() expression we can see that the blank field in Birth Date column was changed to null. The column CSVReportLastUpdate which did not have the if(empty() expression remained with the “” double quotes blank.

Correction Step 1 Results GenerateSPDataCorrection Step 1 Results GenerateSPData

The problem with just using the if(empty() expression is that the remaining date fields after the first row are still in Serial format. None of the rows will upload to SharePoint because they are still in Serial and will not be accepted.

 

Correction Step 2 – Use addSeconds() expression to convert Serial dates

To convert the Serial dates to a format that can be used by SharePoint the expression addDays() or addSeconds() has to be used. There are many posts on converting dates that can be found. For my example I’m going to use the addSeconds() expression for both columns [‘Birth Date’] and [‘CSVReportLastUpdate’] since one column includes time and a bonus is the final result will be in a format that can be accepted by SharePoint without writing it out.

 

The expression addSeconds() is adding the number of seconds to the date 1899-12-30 based on the Serial date and then formats it. If no additional formatting such as yyyy-mm-dd is added to the addSeconds() expression it will default to a ISO 8601 format that is readable by SharePoint so I don’t add any additional formatting.

 

addSeconds('1899-12-30',int(formatNumber(mul(float(item()?['CSVReportLastUpdate']),86400),'0')))

Correction Step 2 Generate SPDataCorrection Step 2 Generate SPData

There is an issue with only using the addSeconds() expression due to blank values. The addSeconds() is unable to deal with the blank values and sends a flow error message when testing. The flow fails because of the error “The template language function ‘float’ was invoked with a parameter that is not valid. The value cannot be converted to the target type.”

Correction Step 2 Results Generate SPDataCorrection Step 2 Results Generate SPData

 

Correction Step 3 - Combine the previous correction steps into a single expression 

 

Since the If(empty() expression is able to deal with the first row blank and the AddSeconds() is able to deal with the dates being in Serial format then put both expressions within an If() expression.

The expression will check if the field is empty then replace with null, and if the field is not empty then use the addSeconds to format the time correctly.

if(empty(item()?['Birth Date']),null,addSeconds('1899-12-30',int(formatNumber(mul(float(item()?['Birth Date']),86400),'0'))))

Correction Step 3 Detail Generate SPDataCorrection Step 3 Detail Generate SPData

 

After putting in the expressions and running the test flow I’m comparing the Generate SPData inputs and outputs to see the changes the expressions made. Since the dates are now formatted as IS0 8601 they can be uploaded in the SendBatch and see the result is they are in the SharePoint list correctly.

 

Correction Step 3 Results Generate SPDataCorrection Step 3 Results Generate SPData

Excel Source Table Top Row Blank FieldsExcel Source Table Top Row Blank FieldsSP List Upload Results after Step 3SP List Upload Results after Step 3

This solution is only temporary and applies specifically to this example with dates blank in the first row. Since the blanks in the first row changed the remaining rows to Serial they had to be corrected with the expressions. If the first rows are not blank, the expressions will cause errors.

 

Follow-Up Issue after Correction Steps:

The format of the Excel Get List settings is still IS0 8601, so if this flow is run again but the first rows do have dates filled instead of blank like the examples, then the flow will error since the addseconds() formula is attempting to add time to values that are already in the UTC format.

If I remove two date fields that are not in the top row the flow goes back to the correct ISO 8601 format that is UTC. In the results it shows the dates of Index 1 correctly formatted as UTC so the addSeconds() expression errors since the now UTC formatted date doesn’t work correctly in the float() due to not being a decimal number.

Follow Up Issue Excel Source tableFollow Up Issue Excel Source table

 

I'm attaching a screenshot of the results after I remove the 2 dates but leave the expressions the same as before from Correction Step 3.

FollowUp Issue Result ErrorFollowUp Issue Result Error

 

The solution to correct this will be to change the List Rows dropdown DateTime Format to Serial Number which will change all dates to Serial format. This will allow the dates to work with the correction expressions whenever the top row has blanks or filled.

FollowUp Issue List Rows Setting ChangeFollowUp Issue List Rows Setting Change

However, now ALL date column have to include the expressions since they will be in Serial format even if there are no blanks. If a column is not formatted from the expression it will not upload properly to SharePoint because it is now being pulled from Excel as Serial due to the List Rows settings drop down.

I ran the flow to get a copy of the results to show the formatting differences after changing the dropdown to Serial instead of ISO 8601. The flow ran, but nothing was uploaded to SP due to the last datetime column not having any expression changing it.

FollowUpIssue Result after Serial ChangeFollowUpIssue Result after Serial Change

So I have to go to the third datetime column CSVRptCentralStandardTime and also put it in an expression even though it hasn’t been an issue with any of the previous examples.

FollowUpIssue Results All DateFields ExpressionFollowUpIssue Results All DateFields Expression

This will upload properly to the SharePoint.

FollowUpIssue SharePoint List ResultFollowUpIssue SharePoint List Result

 

Conclusion:

I'll probably never have an exact answer for why top blank rows cause remaining rows to be Serial. I believe @takolota is most likely correct with the import making an initial reading and then applying to the rest of the rows.

 

The solution for dealing with blank fields in the first row isn't exactly straightforward and depends on expected data coming in the fields. However, changing the dropdown to Serial instead of ISO 8601, then using expressions on all date or datetime columns seems the be the biggest catchall since it will account for blanks in the first row as well as format date correctly even if the first row fields are filled.  

 

View solution in original post

2 REPLIES 2
takolota
Super User
Super User

@wskinnermctc 

 

Thanks for the shoutout & feedback.

 

My first guess for the issue is that if the Excel rows are blank and dates, then maybe it is registering it as a text column instead of a date column, so the ISO 8601 isn’t being applied.

 

Have you tried using a method like this to convert the date numbers to the date format you need in the GenerateSPData action?

https://www.tachytelic.net/2020/11/convert-excel-dates-power-automate/?amp

wskinnermctc
Memorable Member
Memorable Member

I have a couple of correction steps for when the dates convert to Serial due to first row blank. I'll use expressions to convert the date numbers like @takolota suggested. However, the correction steps lead to a follow-up problem that requires additional changes to the overall datetime format of the Get List Rows step. 

I realize these correction steps aren't anything new and there are dozens of pages referring to these; however, I am going to have a problem in another flow and I want to be able to reference this post.

 

Correction Step 1 - Replace blank date fields with 'null' by using expression If(empty([Date]),null,[Date])

 

The first issue is that SharePoint can’t accept double quotes blank value for a datetime field. SharePoint can accept a blank so long as it has the word null to represent the blank data field. So using the empty() expression will check if the field is double quote “” blank and return a result of true if it is.

Combine the empty() expression with the if() expression to say If the date is empty then return ‘null’ else just return the date field.

if(empty(item?['Birth Date']),null,item()?['Birth Date])

 

Correction Step 1 Detail Generate SPDataCorrection Step 1 Detail Generate SPData

I’m attaching a screenshots of the results of a test flow showing the inputs and outputs of the step Generate SPData. When running the flow using the if(empty() expression we can see that the blank field in Birth Date column was changed to null. The column CSVReportLastUpdate which did not have the if(empty() expression remained with the “” double quotes blank.

Correction Step 1 Results GenerateSPDataCorrection Step 1 Results GenerateSPData

The problem with just using the if(empty() expression is that the remaining date fields after the first row are still in Serial format. None of the rows will upload to SharePoint because they are still in Serial and will not be accepted.

 

Correction Step 2 – Use addSeconds() expression to convert Serial dates

To convert the Serial dates to a format that can be used by SharePoint the expression addDays() or addSeconds() has to be used. There are many posts on converting dates that can be found. For my example I’m going to use the addSeconds() expression for both columns [‘Birth Date’] and [‘CSVReportLastUpdate’] since one column includes time and a bonus is the final result will be in a format that can be accepted by SharePoint without writing it out.

 

The expression addSeconds() is adding the number of seconds to the date 1899-12-30 based on the Serial date and then formats it. If no additional formatting such as yyyy-mm-dd is added to the addSeconds() expression it will default to a ISO 8601 format that is readable by SharePoint so I don’t add any additional formatting.

 

addSeconds('1899-12-30',int(formatNumber(mul(float(item()?['CSVReportLastUpdate']),86400),'0')))

Correction Step 2 Generate SPDataCorrection Step 2 Generate SPData

There is an issue with only using the addSeconds() expression due to blank values. The addSeconds() is unable to deal with the blank values and sends a flow error message when testing. The flow fails because of the error “The template language function ‘float’ was invoked with a parameter that is not valid. The value cannot be converted to the target type.”

Correction Step 2 Results Generate SPDataCorrection Step 2 Results Generate SPData

 

Correction Step 3 - Combine the previous correction steps into a single expression 

 

Since the If(empty() expression is able to deal with the first row blank and the AddSeconds() is able to deal with the dates being in Serial format then put both expressions within an If() expression.

The expression will check if the field is empty then replace with null, and if the field is not empty then use the addSeconds to format the time correctly.

if(empty(item()?['Birth Date']),null,addSeconds('1899-12-30',int(formatNumber(mul(float(item()?['Birth Date']),86400),'0'))))

Correction Step 3 Detail Generate SPDataCorrection Step 3 Detail Generate SPData

 

After putting in the expressions and running the test flow I’m comparing the Generate SPData inputs and outputs to see the changes the expressions made. Since the dates are now formatted as IS0 8601 they can be uploaded in the SendBatch and see the result is they are in the SharePoint list correctly.

 

Correction Step 3 Results Generate SPDataCorrection Step 3 Results Generate SPData

Excel Source Table Top Row Blank FieldsExcel Source Table Top Row Blank FieldsSP List Upload Results after Step 3SP List Upload Results after Step 3

This solution is only temporary and applies specifically to this example with dates blank in the first row. Since the blanks in the first row changed the remaining rows to Serial they had to be corrected with the expressions. If the first rows are not blank, the expressions will cause errors.

 

Follow-Up Issue after Correction Steps:

The format of the Excel Get List settings is still IS0 8601, so if this flow is run again but the first rows do have dates filled instead of blank like the examples, then the flow will error since the addseconds() formula is attempting to add time to values that are already in the UTC format.

If I remove two date fields that are not in the top row the flow goes back to the correct ISO 8601 format that is UTC. In the results it shows the dates of Index 1 correctly formatted as UTC so the addSeconds() expression errors since the now UTC formatted date doesn’t work correctly in the float() due to not being a decimal number.

Follow Up Issue Excel Source tableFollow Up Issue Excel Source table

 

I'm attaching a screenshot of the results after I remove the 2 dates but leave the expressions the same as before from Correction Step 3.

FollowUp Issue Result ErrorFollowUp Issue Result Error

 

The solution to correct this will be to change the List Rows dropdown DateTime Format to Serial Number which will change all dates to Serial format. This will allow the dates to work with the correction expressions whenever the top row has blanks or filled.

FollowUp Issue List Rows Setting ChangeFollowUp Issue List Rows Setting Change

However, now ALL date column have to include the expressions since they will be in Serial format even if there are no blanks. If a column is not formatted from the expression it will not upload properly to SharePoint because it is now being pulled from Excel as Serial due to the List Rows settings drop down.

I ran the flow to get a copy of the results to show the formatting differences after changing the dropdown to Serial instead of ISO 8601. The flow ran, but nothing was uploaded to SP due to the last datetime column not having any expression changing it.

FollowUpIssue Result after Serial ChangeFollowUpIssue Result after Serial Change

So I have to go to the third datetime column CSVRptCentralStandardTime and also put it in an expression even though it hasn’t been an issue with any of the previous examples.

FollowUpIssue Results All DateFields ExpressionFollowUpIssue Results All DateFields Expression

This will upload properly to the SharePoint.

FollowUpIssue SharePoint List ResultFollowUpIssue SharePoint List Result

 

Conclusion:

I'll probably never have an exact answer for why top blank rows cause remaining rows to be Serial. I believe @takolota is most likely correct with the import making an initial reading and then applying to the rest of the rows.

 

The solution for dealing with blank fields in the first row isn't exactly straightforward and depends on expected data coming in the fields. However, changing the dropdown to Serial instead of ISO 8601, then using expressions on all date or datetime columns seems the be the biggest catchall since it will account for blanks in the first row as well as format date correctly even if the first row fields are filled.  

 

Helpful resources

Announcements

Power Platform Connections Ep 15 | L. Baybutt | Thursday, 1 June 2023

Episode Fifteen of Power Platform Connections sees David Warner and Hugo Bernier talk to Microsoft MVP Lewis Baybutt aka Low Code Lewis, alongside the latest news and community blogs.   Use the hashtag #PowerPlatformConnects on social media for a chance to have your work featured on the show.        Action requested: Feel free to provide feedback on how we can make our community more inclusive and diverse.  This episode premiers live on our YouTube at 12pm PST on Thursday 1st June 2023.  Video series available at Power Platform Community YouTube channel.    Upcoming events:  European Power Platform conference – Jun. 20-22nd - Dublin Microsoft Power Platform Conference – Oct. 3-5th - Las Vegas  Join our Communities:  Power Apps Community Power Automate Community Power Virtual Agents Community Power Pages Community  If you’d like to hear from a specific community member in an upcoming recording and/or have specific questions for the Power Platform Connections team, please let us know. We will do our best to address all your requests or questions.  Action requested: Feel free to provide feedback on how we can make our community more inclusive and diverse.  This episode premiers live on our YouTube at 12pm PST on Thursday 1st June 2023.  Video series available at Power Platform Community YouTube channel.    Upcoming events:  European Power Platform conference – Jun. 20-22nd - Dublin Microsoft Power Platform Conference – Oct. 3-5th - Las Vegas  Join our Communities:  Power Apps Community Power Automate Community Power Virtual Agents Community Power Pages Community  If you’d like to hear from a specific community member in an upcoming recording and/or have specific questions for the Power Platform Connections team, please let us know. We will do our best to address all your requests or questions. 

May 2023 Community Newsletter and Upcoming Events

Welcome to our May 2023 Community Newsletter, where we'll be highlighting the latest news, releases, upcoming events, and the great work of our members inside the Biz Apps communities. If you're new to this LinkedIn group, be sure to subscribe here in the News & Announcements to stay up to date with the latest news from our ever-growing membership network who "changed the way they thought about code".         LATEST NEWS "Mondays at Microsoft" LIVE on LinkedIn - 8am PST - Monday 15th May  - Grab your Monday morning coffee and come join Principal Program Managers Heather Cook and Karuana Gatimu for the premiere episode of "Mondays at Microsoft"! This show will kick off the launch of the new Microsoft Community LinkedIn channel and cover a whole host of hot topics from across the #PowerPlatform, #ModernWork, #Dynamics365, #AI, and everything in-between. Just click the image below to register and come join the team LIVE on Monday 15th May 2023 at 8am PST. Hope to see you there!     Executive Keynote | Microsoft Customer Success Day CVP for Business Applications & Platform, Charles Lamanna, shares the latest #BusinessApplications product enhancements and updates to help customers achieve their business outcomes.         S01E13 Power Platform Connections - 12pm PST - Thursday 11th May Episode Thirteen of Power Platform Connections sees Hugo Bernier take a deep dive into the mind of co-host David Warner II, alongside the reviewing the great work of Dennis Goedegebuure, Keith Atherton, Michael Megel, Cat Schneider, and more. Click below to subscribe and get notified, with David and Hugo LIVE in the YouTube chat from 12pm PST. And use the hashtag #PowerPlatformConnects on social media for a chance to have your work featured on the show.         UPCOMING EVENTS   European Power Platform Conference - early bird ticket sale ends! The European Power Platform Conference early bird ticket sale ends on Friday 12th May 2023! #EPPC23 brings together the Microsoft Power Platform Communities for three days of unrivaled days in-person learning, connections and inspiration, featuring three inspirational keynotes, six expert full-day tutorials, and over eighty-five specialist sessions, with guest speakers including April Dunnam, Dona Sarkar, Ilya Fainberg, Janet Robb, Daniel Laskewitz, Rui Santos, Jens Christian Schrøder, Marco Rocca, and many more. Deep dive into the latest product advancements as you hear from some of the brightest minds in the #PowerApps space. Click here to book your ticket today and save!      DynamicMinds Conference - Slovenia - 22-24th May 2023 It's not long now until the DynamicsMinds Conference, which takes place in Slovenia on 22nd - 24th May, 2023 - where brilliant minds meet, mingle & share! This great Power Platform and Dynamics 365 Conference features a whole host of amazing speakers, including the likes of Georg Glantschnig, Dona Sarkar, Tommy Skaue, Monique Hayward, Aleksandar Totovic, Rachel Profitt, Aurélien CLERE, Ana Inés Urrutia de Souza, Luca Pellegrini, Bostjan Golob, Shannon Mullins, Elena Baeva, Ivan Ficko, Guro Faller, Vivian Voss, Andrew Bibby, Tricia Sinclair, Roger Gilchrist, Sara Lagerquist, Steve Mordue, and many more. Click here: DynamicsMinds Conference for more info on what is sure an amazing community conference covering all aspects of Power Platform and beyond.    Days of Knowledge Conference in Denmark - 1-2nd June 2023 Check out 'Days of Knowledge', a Directions 4 Partners conference on 1st-2nd June in Odense, Denmark, which focuses on educating employees, sharing knowledge and upgrading Business Central professionals. This fantastic two-day conference offers a combination of training sessions and workshops - all with Business Central and related products as the main topic. There's a great list of industry experts sharing their knowledge, including Iona V., Bert Verbeek, Liza Juhlin, Douglas Romão, Carolina Edvinsson, Kim Dalsgaard Christensen, Inga Sartauskaite, Peik Bech-Andersen, Shannon Mullins, James Crowter, Mona Borksted Nielsen, Renato Fajdiga, Vivian Voss, Sven Noomen, Paulien Buskens, Andri Már Helgason, Kayleen Hannigan, Freddy Kristiansen, Signe Agerbo, Luc van Vugt, and many more. If you want to meet industry experts, gain an advantage in the SMB-market, and acquire new knowledge about Microsoft Dynamics Business Central, click here Days of Knowledge Conference in Denmark to buy your ticket today!   COMMUNITY HIGHLIGHTS Check out our top Super and Community Users reaching new levels! These hardworking members are posting, answering questions, kudos, and providing top solutions in their communities.   Power Apps:  Super Users: @WarrenBelz, @LaurensM  @BCBuizer  Community Users:  @Amik@ @mmollet, @Cr1t    Power Automate:  Super Users: @Expiscornovus , @grantjenkins, @abm  Community Users: @Nived_Nambiar, @ManishSolanki    Power Virtual Agents:  Super Users: @Pstork1, @Expiscornovus  Community Users: @JoseA, @fernandosilva, @angerfire1213    Power Pages: Super Users: @ragavanrajan  Community Users: @Fubar, @Madhankumar_L,@gospa  LATEST COMMUNITY BLOG ARTICLES  Power Apps Community Blog  Power Automate Community Blog  Power Virtual Agents Community Blog  Power Pages Community Blog  Check out 'Using the Community' for more helpful tips and information:  Power Apps , Power Automate, Power Virtual Agents, Power Pages 

Announcing | Super Users - 2023 Season 1

Super Users – 2023 Season 1    We are excited to kick off the Power Users Super User Program for 2023 - Season 1.  The Power Platform Super Users have done an amazing job in keeping the Power Platform communities helpful, accurate and responsive. We would like to send these amazing folks a big THANK YOU for their efforts.      Super User Season 1 | Contributions July 1, 2022 – December 31, 2022  Super User Season 2 | Contributions January 1, 2023 – June 30, 2023    Curious what a Super User is? Super Users are especially active community members who are eager to help others with their community questions. There are 2 Super User seasons in a year, and we monitor the community for new potential Super Users at the end of each season. Super Users are recognized in the community with both a rank name and icon next to their username, and a seasonal badge on their profile.  Power Apps  Power Automate  Power Virtual Agents  Power Pages  Pstork1*  Pstork1*  Pstork1*  OliverRodrigues  BCBuizer  Expiscornovus*  Expiscornovus*  ragavanrajan  AhmedSalih  grantjenkins  renatoromao    Mira_Ghaly*  Mira_Ghaly*      Sundeep_Malik*  Sundeep_Malik*      SudeepGhatakNZ*  SudeepGhatakNZ*      StretchFredrik*  StretchFredrik*      365-Assist*  365-Assist*      cha_cha  ekarim2020      timl  Hardesh15      iAm_ManCat  annajhaveri      SebS  Rhiassuring      LaurensM  abm      TheRobRush  Ankesh_49      WiZey  lbendlin      Nogueira1306  Kaif_Siddique      victorcp  RobElliott      dpoggemann  srduval      SBax  CFernandes      Roverandom  schwibach      Akser  CraigStewart      PowerRanger  MichaelAnnis      subsguts  David_MA      EricRegnier  edgonzales      zmansuri  GeorgiosG      ChrisPiasecki  ryule      AmDev  fchopo      phipps0218  tom_riha      theapurva  takolota     Akash17  momlo     BCLS776  Shuvam-rpa     rampprakash  ScottShearer     Rusk  ChristianAbata     cchannon  Koen5     a33ik  Heartholme     AaronKnox  okeks      Matren  David_MA     Alex_10        Jeff_Thorpe        poweractivate        Ramole        DianaBirkelbach        DavidZoon        AJ_Z        PriyankaGeethik        BrianS        StalinPonnusamy        HamidBee        CNT        Anonymous_Hippo        Anchov        KeithAtherton        alaabitar        Tolu_Victor        KRider        sperry1625        IPC_ahaas      zuurg    rubin_boer   cwebb365   Dorrinda   G1124   Gabibalaban   Manan-Malhotra   jcfDaniel   WarrenBelz   Waegemma   drrickryp   GuidoPreite   metsshan    If an * is at the end of a user's name this means they are a Multi Super User, in more than one community. Please note this is not the final list, as we are pending a few acceptances.  Once they are received the list will be updated. 

Check out the new Power Platform Communities Front Door Experience!

We are excited to share the ‘Power Platform Communities Front Door’ experience with you!   Front Door brings together content from all the Power Platform communities into a single place for our community members, customers and low-code, no-code enthusiasts to learn, share and engage with peers, advocates, community program managers and our product team members. There are a host of features and new capabilities now available on Power Platform Communities Front Door to make content more discoverable for all power product community users which includes ForumsUser GroupsEventsCommunity highlightsCommunity by numbersLinks to all communities Users can see top discussions from across all the Power Platform communities and easily navigate to the latest or trending posts for further interaction. Additionally, they can filter to individual products as well.   Users can filter and browse the user group events from all power platform products with feature parity to existing community user group experience and added filtering capabilities.     Users can now explore user groups on the Power Platform Front Door landing page with capability to view all products in Power Platform.      Explore Power Platform Communities Front Door today. Visit Power Platform Community Front door to easily navigate to the different product communities, view a roll up of user groups, events and forums.

Microsoft Power Platform Conference | Registration Open | Oct. 3-5 2023

We are so excited to see you for the Microsoft Power Platform Conference in Las Vegas October 3-5 2023! But first, let's take a look back at some fun moments and the best community in tech from MPPC 2022 in Orlando, Florida.   Featuring guest speakers such as Charles Lamanna, Heather Cook, Julie Strauss, Nirav Shah, Ryan Cunningham, Sangya Singh, Stephen Siciliano, Hugo Bernier and many more.   Register today: https://www.powerplatformconf.com/   

Users online (4,917)