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.
The source Excel table is a list of 5 employees with 3 different date columns.
Excel 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 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 BatchUpload
Example 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.
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 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 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.
Example 2 Results SendBatch
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 "
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.
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 Overview
Batch Upload Flow Detail p1 of 4
Batch Upload Flow Detail p2 of 4
Batch Upload Flow Detail p3 of 4
Batch Upload Flow Detail p4 of 4
Solved! Go to Solution.
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.
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 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 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.
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 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 SPData
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 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 SPData
Excel Source Table Top Row Blank Fields
SP 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 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 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 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 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 Expression
This will upload properly to the SharePoint.
FollowUpIssue 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.
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
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.
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 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 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.
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 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 SPData
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 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 SPData
Excel Source Table Top Row Blank Fields
SP 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 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 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 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 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 Expression
This will upload properly to the SharePoint.
FollowUpIssue 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.
Welcome to our November Newsletter, where we highlight the latest news, product releases, upcoming events, and the amazing work of our outstanding Community members. If you're new to the Community, please make sure to follow the latest News & Announcements and check out the Community on LinkedIn as well! It's the best way to stay up-to-date with all the news from across the Power Platform and beyond. This month's highlights:- - Our most active community members- Microsoft Power Up Program- Microsoft Community Days website - The latest blogs and more COMMUNITY HIGHLIGHTS Check out the most active community members of the last month. These hardworking members are posting regularly, answering questions, kudos, and providing top solutions in their communities. We are so thankful for each of you--keep up the great work! If you hope to see your name here next month, just get active! FLMikePstork1Nived_NambiarWarrenBelzSprongYeManishSolankiLaurensMwskinnermlcAgniusExpiscornovuscreativeopinion KatieAUinzil2kHaressh2728hafizsultan242douicmccaughanwoLucas001domliu Power Up Program Click the image below to discover more about the amazing Microsoft Power Up Program, as Reem Omar, Abbas Godhrawala, Chahine Atallah, Ruby Ruiz Brown, Juan Francisco Sánchez Enciso, Joscelyne Andrade Arévalo, Eric G. and Paulina Pałczyńska share how non-tech professionals can successfully advance into a new career path using Microsoft #PowerPlatform. To find out more about this amazing initiative, click here to apply for the program and reboot your journey into low-code app development today! Community Days - Event Website Have you checked out the Community Days website yet? Dedicated to the volunteer community organizers around the world, Community Days is the perfect place to find an event near you or add an event for wider exposure. Many thanks to Thomas Daly, Sharon Weaver, Sedat Tum, Jonathan Weaver, Manpreet Singh, David Leveille, Jason Rivera, Mike Maadarani, Rob Windsor and the team for all their hard work. Anyone can host a Community Day on any topic relevant to our industry, just click the image below to find out more. EVENT NEWS Power Platform French Summit - Paris/Virtual - 6-7th Dec It's not long now until the Power Platform French Summit, which takes place both virtually and in-person at the Microsoft France conference center in Paris on 6-7th December 2023. If you can't make it in-person, all sessions will also be broadcast on virtual networks for better distribution and accessibility. There's a fantastic array of speakers, including Jérémy LAPLAINE, Amira Beldjilali, Rémi Chambard, Erika Beaumier, Makenson Frena, Assia Boutera, Elliott Pierret, Clothilde Facon, Gilles Pommier, Marie Aubert, Antoine Herbosa, Chloé Moreau, Raphaël Senis, Rym Ben Hamida, Loïc Cimon, Joséphine Salafia, David Zoonekyndt, Aïcha Charpentier, Henry Jammes, Milene Rochard, Mehdi EL YASSIR, and many more. Click the image below for more information. LATEST COMMUNITY BLOG ARTICLES Power Apps Community Blog Power Automate Community Blog Copilot Community Blog Power Pages Community Blog
This is the TENTH post in our ongoing series dedicated to 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 feature new 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: All About Community Support Whether you're a seasoned community veteran or just getting started, you may need a bit of help from time to time! If you need to share feedback with the Community Engagement team about the community or are looking for ways we can assist you with user groups, events, or something else, Community Support is the place to start. Community Support is part of every one of our communities, accessible to all our community members. Power Apps: https://powerusers.microsoft.com/t5/Community-Support/ct-p/pa_community_support Power Automate: https://powerusers.microsoft.com/t5/Community-Support/ct-p/mpa_community_support Power Pages: https://powerusers.microsoft.com/t5/Community-Support/ct-p/mpp_community_support Copilot Studio: https://powerusers.microsoft.com/t5/Community-Support/ct-p/pva_community-support Within each community's Community Support page, you'll find three distinct areas, each with a different focus to help you when you need support from us most. Community Accounts & Registration is the go-to source for any and all information related to your account here in the community. It's full of great knowledge base articles that will help you manage your community account and know what steps to take if you wish to close your account. ● Power Apps ● Power Automate ● Power Pages, ● Copilot Studio Using the Community is your source for assistance with everything from Community User Groups to FAQ's and more. If you want to know what kudos are, how badges work, how to level up your User Group or something else, you will probably find the answers here. ● Power Apps ● Power Automate ● Power Pages ● Copilot Studio Community Feedback is where you can share opportunities, concerns, or get information from the Community Engagement team. It's your best place to post a question about an issue you're having in the community, a general question you need answered. Whatever it is, visit Community Feedback to get the answers you need right away. Our team is honored to partner with you and can't wait to help you! ● Power Apps ● Power Automate ● Power Pages ● Copilot Studio
What an amazing event we had this year, as Microsoft showcased the latest advancements in how AI has the potential to reshape how customers, partners and developers strategize the future of work. Check out below some of our handpicked videos and Ignite announcements to see how Microsoft is driving real change for users and businesses across the globe. Video Highlights Click the image below to check out a selection of Ignite 2023 videos, including the "Microsoft Cloud in the era of AI" keynote from Scott Guthrie, Charles Lamanna, Arun Ulag, Sarah Bird, Rani Borkar, Eric Boyd, Erin Chapple, Ali Ghodsi, and Seth Juarez. There's also a great breakdown of the amazing Microsoft Copilot Studio with Omar Aftab, Gary Pretty, and Kendra Springer, plus exciting sessions from Rajesh Jha, Jared Spataro, Ryan Jones, Zohar Raz, and many more. Blog Announcements Microsoft Copilot presents an opportunity to reimagine the way we work—turning natural language into the most powerful productivity tool on the planet. With AI, organizations can unearth value in data across productivity tools like business applications and Microsoft 365. Click the link below to find out more. Check out the latest features in Microsoft Power Apps that will help developers create AI-infused apps faster, give administrators more control over managing thousands of Microsoft Power Platform makers at scale, and deliver better experiences to users around the world. Click the image below to find out more. Click below to discover new ways to orchestrate business processes across your organization with Copilot in Power Automate. With its user-friendly interface that offers hundreds of prebuilt drag-and-drop actions, more customers have been able to benefit from the power of automation. Discover how Microsoft Power Platform and Microsoft Dataverse are activating the strength of your enterprise data using AI, the announcement of “plugins for Microsoft Copilot for Microsoft 365”, plus two new Power Apps creator experiences using Excel and natural language. Click below to find out more about the general availability of Microsoft Fabric and the public preview of Copilot in Microsoft Fabric. With the launch of these next-generation analytics tools, you can empower your data teams to easily scale the demand on your growing business. And for the rest of all the good stuff, click the link below to visit the Microsoft Ignite 2023 "Book of News", with over ONE HUNDRED announcements across infrastructure, data, security, new tools, AI, and everything else in-between!
This is the ninth post in our series dedicated to 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 feature new 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! Today's Tip: All About the Galleries Have you checked out the library of content in our galleries? Whether you're looking for the latest info on an upcoming event, a helpful webinar, or tips and tricks from some of our most experienced community members, our galleries are full of the latest and greatest video content for the Power Platform communities. There are several different galleries in each community, but we recommend checking these out first: Community Connections & How-To Videos Hosted by members of the Power Platform Community Engagement Team and featuring community members from around the world, these helpful videos are a great way to "kick the tires" of Power Platform and find out more about your fellow community members! Check them out in Power Apps, Power Automate, Power Pages, and Copilot Studio! Webinars & Video Gallery Each community has its own unique webinars and videos highlighting some of the great work being done across the Power Platform. Watch tutorials and demos by Microsoft staff, partners, and community gurus! Check them out: Power Apps Webinars & Video Gallery Power Automate Webinars & Video Gallery Power Pages Webinars & Video Gallery Copilot Studio Webinars & Video Gallery Events Whether it's the excitement of the Microsoft Power Platform Conference, a local event near you, or one of the many other in-person and virtual connection opportunities around the world, this is the place to find out more about all the Power Platform-centered events. Power Apps Events Power Automate Events Power Pages Events Copilot Studio Events Unique Galleries to Each Community Because each area of Power Platform has its own unique features and benefits, there are areas of the galleries dedicated specifically to videos about that product. Whether it's Power Apps samples from the community or the Power Automate Cookbook highlighting unique flows, the Bot Sharing Gallery in Copilot Studio or Front-End Code Samples in Power Pages, there's a gallery for you! Check out each community's gallery today! Power Apps Gallery Power Automate Gallery Power Pages Gallery Copilot Studio Gallery
In the bustling world of technology, two dynamic leaders, Geetha Sivasailam and Ben McMann, have been at the forefront, steering the ship of the Dallas Fort Worth Power Platform User Group since its inception in February 2019. As Practice Lead (Power Platform | Fusion Dev) at Lantern, Geetha brings a wealth of consulting experience, while Ben, a key member of the Studio Leadership team at Lantern, specializes in crafting strategies that leverage Microsoft digital technologies to transform business models. Empowering Through Community Leadership Geetha and Ben's journey as user group leaders began with a simple yet powerful goal: to create a space where individuals across the DFW area could connect, grow their skills, and add value to their businesses through the Power Platform. The platform, known for its versatility, allows users to achieve more with less code and foster creativity. The Power of Community Impact Reflecting on their experiences, Geetha and Ben emphasize the profound impact that community engagement has had on both their professional and personal lives. The Power Platform community, they note, is a wellspring of resources and opportunities, fostering continuous learning, skill enhancement, and networking with industry experts and peers. Favorite Moments and Words of Wisdom The duo's favorite aspect of leading the user group lies in witnessing the transformative projects and innovations community members create with the Power Platform. Their advice to aspiring user group leaders? "Encourage diverse perspectives, maintain an open space for idea-sharing, stay curious, and, most importantly, have fun building a vibrant community." Building Bridges, Breaking Barriers Geetha and Ben encourage others to step into the realm of user group leadership, citing the rewarding experience of creating and nurturing a community of like-minded individuals. They highlight the chance to influence, impact, and positively guide others, fostering connections that extend beyond mere technology discussions. Joining a User Group: A Gateway to Growth The leaders stress the importance of joining a user group, emphasizing exposure to diverse perspectives, solutions, and career growth opportunities within the Power Platform community. "Being part of such a group provides a supportive environment for seeking advice, sharing experiences, and navigating challenges." A Year of Milestones Looking back at the past year, Geetha and Ben express pride in the group's growth and global participation. They recount the enriching experience of meeting members in person at the Microsoft Power Platform conference, showcasing the diverse range of perspectives and guest speakers that enriched the community's overall experience. Continuous Learning on the Leadership Journey As user group leaders, Geetha and Ben recognize the continuous learning curve, blending interpersonal skills, adaptability, and dedication to foster a vibrant community. They highlight the importance of patience, persistence, and flexibility in achieving group goals, noting the significance of listening to the needs and suggestions of group members.They invite all tech enthusiasts to join the Dallas Fort Worth Power Platform User Group, a thriving hub where the power of community propels individuals to new heights in the dynamic realm of technology.
Are you attending Microsoft Ignite in Seattle this week? If so, we'd love to see you at the Community Lounge! Hosted by members of our Community team, it's a great place to connect, meet some Microsoft executives, and get a sticker or two. And if you're an MVP there are some special opportunities to meet up! The Community Lounge is more than just a space—it's a hub of activity, collaboration, and camaraderie. So, dive in, explore, and make the most of your Microsoft Ignite experience by immersing yourself in the vibrant and dynamic community that awaits you.Find out the schedule and all the details here: Community Lounge at Ignite! See you at #MSIgnite!
User | Count |
---|---|
60 | |
52 | |
27 | |
25 | |
19 |
User | Count |
---|---|
111 | |
67 | |
50 | |
45 | |
39 |