cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
AustinC
New Member

PATCH Advice

Hello!

 

I am trying to seek advice regarding a way to filter by table headings, rather than specific items within rows. I've been working on an attendance application for awhile, and I see some cool one's on YouTube that I'm curious as to how they created.

 

Some points/information:

 

1. I'm using OneDrive for Business as the data source.

2. Keiki = Children, Makua = Parent, Kumu = Teacher. These are Hawaiian words.

3. I have a Datepicker and also a text box that reflects it's selection via text.

4. The way I've written up the logic is incredibly tedious and I'm thinking there's a much easier way to do this.

 

Here's what I have: (note the dates are old as I've focused my time on other applications within the past few months. This will be changed to recent dates soon.) I'm sure the filter doesn't need a million things either, I definitely could probably reduce this to filtering 1-2 things?

 

I've also had to add a column for every single date that we need to track attendance for. Is there an easier way to do this?

 

If(Label1.Text = "1/22/2018",

Patch(Table2, First(Filter(Table2,

ProgramName = DataCardValue5.Text && KumuName = DataCardValue3.Text && NHEPCenter = DataCardValue4.Text && DayOfWeek= DataCardValue6.Text && MakuaLastName = DataCardValue8.Text && MakuaFirstName = DataCardValue7.Text)), {January_22: Dropdown3.Selected.Value, January_22_Curriculum: Dropdown4.Selected.Value}));

 

I would then have to write all that is above over every single time to reflect the next date.

 

Thanks for your help, the way I've written it up WORKS, however, it's super tedious and repetitive.

 

1 ACCEPTED SOLUTION

Accepted Solutions

@AustinC, You are well on your way to the solution just by thinking through this design! Yes, the multiplication of rows should be the attendance records, and you can patch these into existence every day, (or be smart, and simply implement exception reporting where the teacher ONLY calls out and actually stores a row for the lower population of data) This should be those students absent, unless you are like the Detroit schools and those in attendance are the lesser of the two populations! (Sarcasm aside), we don't want to make columns out of dates, this is really REALLY bad design mojo, and we will not be employed for long designing things like that. Think of it this way, the student body is a table, and it can live independent of all the other data info. Teacher is the same way, and so is the list of classes. This could be one single table, or SharePoint list object, or any type of backend storage scheme. The "Joins" are where you have a powerapp dropdown list to pick from, which is storing your brand spanking new "Attendance" table, which presents the class in a dropdown for the teacher to pick, then it presents the student list for them to pick the absentee from another dropdown, then, it lets them specify with an affirmative "Yes/NO" or checkbox selection, that this student is not present today (which is your date, and please use current date so they don't have to type one in. Be nice to teachers!) These few fields (the Teacher/Class/Students/Date/Attendance switch) are now your record for your penultimate table. This way, the PowerApps dropdowns get their data from data sources (The code tables, or stacks of students and teachers, etc) and your "Attendance" designation is the marriage of these fields in the logical order representing the attendance structure that fits your "business requirements." You know, the current day, the teacher, the class, the semester, the week, the student, and BANG, suddenly you have 2 or 5 entries in a class of 22 students who were not there on day 4/17/2018. You can join it all in the database for reporting, but the app is generally adding/modifying/deleting data from ONE TABLE at a time with one "page" of the app, or a gallery and detail page for each of these tables that are managed as independent code lists, leading up to your joined ATTENDANCE row. To cut to the chase, your teacher taps in her name (or her Azure AD login name is auto populated in the first field to be slick) then she picks the class she is teaching from a dropdown and selects the missing kids from another dropdown, then she checks the mark and saves the single ATTENDANCE table record exception for Moana since she is surfing today(or Bethany Hamilton perhaps?) With all the richness that the other dropdowns have collected from the other tables in the schema. Another way to put this, is that the dropdown selection fields have data sources that are "Item collections" from your code tables, and you ultimately store the ATTENDANCE with the goodies from the code tables. Do something for your own education on this item, look up how the items collections work on choice fields in PowerApps and you will be closer to the answer you seek. So, Yes, each ROW is a dated object, with a child name, and class name. This removes redundant data storage of teacher and class from your detailed records, and provides a unique class list of students per class per teacher. I Hope this makes sense, and I wish I could be there (boy do I) to help with this app, but I am stuck in Michigan today. PS (between us coconuts, it's THIRD normal form, not first! Bill Inmon is blushing at you!) Peace, and sunscreen my tropical friend! SmartMeter.

View solution in original post

6 REPLIES 6
timl
Super User
Super User

Hi @AustinC

 

>> I've also had to add a column for every single date that we need to track attendance for.

If possible, I would encourage you NOT to add a column for every single date that you need to track attendance for. It's far better to store the dates as rows in a table. It isn't really possible to filter by table headings. The answer here by @CarlosFigueira highlights the complexity of the formulas we would need to use when the data values are in columns

https://powerusers.microsoft.com/t5/General-Discussion/Dynamic-Collect-column-name/m-p/60753/highlig...

I would recommend that you normalize your data structure to 'third normal form' - you'll find plenty of articles on the web that can do a better job of explaining this than I can. This article on 'first normal form' highlights the problems of a customer table that contains the columns 'Telephone number 1' and 'Telephone number 2', and also describes how you can fix this. Conceptually, this is the same as your 'Table2' with the columns 'January_22' and 'January_22_Curriculum'.

https://en.wikipedia.org/wiki/First_normal_form

If you post more details about your data structure (eg - what are you storing in the Jan_22 column, what data does Dropdown3 contain) , I'm sure someone here can offer more advice.

SmartMeter
Helper V
Helper V

Hi AustinC, What Timl says is spot on, however 3nf is a rather complex thing for a newbie to digest unless he is on a tropical island paradise surrounded by beaches sun and endless time. Let me jump to a closer answer from snowy Michigan because I envy your paradise and will join you in spirit here! Anything that repeats with frequency is a row, anything that is an "entity" (think major noun words) is a column. You make tables of these, then connect them with Junction records. Regardless of SQL or SharePoint or whatever backend (storage means) you are using, you want to do two things here. First, design your tables on a white board with all the stakeholders in session. You will need a "code definition table" to contain the unique list of students (student body table) at any point in time (semester, year, etc.) Make this have a date, the grade they are in, and all the master student info you will need. Make a simple dimple app to add/mod/delete students from this list. Sit back, crack a coconut, and enjoy your progress thus far. Once you have the basic student info. (Think Phone book of the student body as a list.) You will also need one of these "code" tables for teachers and then a third one for your classes. Boom, you now have your first three tables, and a little app to add/mod/delete all the data inside them. Next, you make join tables connecting these unique lists to add your "attendance" functionality. One essential join record will be the Teachers to all the classes and it will need a third and fourth field (Class start and end dates) Simple, done with table number four. Next, add a table for students connected to these class records (hint, table four was named "Classes") This table FIVE is your "Master list of students attending each and all of the classes in the semester." Table six is "the big island" you seek. It is the ATTENDANCE table. This is a junction record (connector) that joins your class table of students in classes, to a brand new piece of data - a simple check mark that the teacher strikes to say "in attendance or not". This should be a gallery based on the Fifth table (list of students in any particular class) and it is simply a list of those students by class name, and the daily check mark arbitrated by the teacher. So there you go, a free database schema, but you will need to flesh out the fields (entities, or nouns) that each of these six tables should properly contain, and the relationships (joined common data fields) that your school will need to use. Long story short (from a guy who was a DBA for a while!) You will need exactly six tables, and six teeny tiny apps to pull this design off optimally. As for a report, you can do this with PowerBI, or a simple-dimple report can be done with the power-apps charting components. Next time I'm in Hawaii (in my dreams) save me a beach, and if you ever make it to Michigan, I'll save you some snow! (PS, I would use SQL server for the backend if I were you, it does relationships very easily, and SharePoint is rather constrained to the depth of relational design that can be executed therein- aka Lookups are not at a par with primary and foreign keys in SQL.) Peace, SmartMeter.

OOPS, I forgot something. "All I can say is Your Welcome!" SmartMeter 😉

Thanks for all of your feedback and hilarious commentary. I'm not sure if First Normal Form would be the answer to tracking attendance, as every attendance entry would contain a new row with student attendance? Unless I am misunderstanding that. I do see how it would simplify the problem in it's entirety, because I could just have a PATCH function with the insertion of data into a Date Attended column... That would solve my problem, however, would create a new one by there being many entries.

 

@SmartMeter, I have some experience working with Heidi SQL, but mainly as a hobby. I have never tried to run strictly My SQL, though, so not sure how different it is.

 

I also never thought about multiple tables, as I thought Powerapps didn't support it. It seems like using SQL with multiple tables could definitely be the most beneficial in the long run: 

 

https://powerusers.microsoft.com/t5/General-Discussion/Syntax-for-joining-tables/td-p/61387 shows a way to join it. I just need to try and put it into practice.

 

Thanks for all of your help!

I forgot to add. In the column curriculum, a teacher requested an option to select which week of curriculum they taught that day. They have 20-40 weeks of curriculum, and I couldn't think of a better way to track it.

 

Maybe you are right with First Normal Form... Maybe I should PATCH a new row with a simple date and curriculum column, rather than manually entering in every date for the rest of the year and future years.

@AustinC, You are well on your way to the solution just by thinking through this design! Yes, the multiplication of rows should be the attendance records, and you can patch these into existence every day, (or be smart, and simply implement exception reporting where the teacher ONLY calls out and actually stores a row for the lower population of data) This should be those students absent, unless you are like the Detroit schools and those in attendance are the lesser of the two populations! (Sarcasm aside), we don't want to make columns out of dates, this is really REALLY bad design mojo, and we will not be employed for long designing things like that. Think of it this way, the student body is a table, and it can live independent of all the other data info. Teacher is the same way, and so is the list of classes. This could be one single table, or SharePoint list object, or any type of backend storage scheme. The "Joins" are where you have a powerapp dropdown list to pick from, which is storing your brand spanking new "Attendance" table, which presents the class in a dropdown for the teacher to pick, then it presents the student list for them to pick the absentee from another dropdown, then, it lets them specify with an affirmative "Yes/NO" or checkbox selection, that this student is not present today (which is your date, and please use current date so they don't have to type one in. Be nice to teachers!) These few fields (the Teacher/Class/Students/Date/Attendance switch) are now your record for your penultimate table. This way, the PowerApps dropdowns get their data from data sources (The code tables, or stacks of students and teachers, etc) and your "Attendance" designation is the marriage of these fields in the logical order representing the attendance structure that fits your "business requirements." You know, the current day, the teacher, the class, the semester, the week, the student, and BANG, suddenly you have 2 or 5 entries in a class of 22 students who were not there on day 4/17/2018. You can join it all in the database for reporting, but the app is generally adding/modifying/deleting data from ONE TABLE at a time with one "page" of the app, or a gallery and detail page for each of these tables that are managed as independent code lists, leading up to your joined ATTENDANCE row. To cut to the chase, your teacher taps in her name (or her Azure AD login name is auto populated in the first field to be slick) then she picks the class she is teaching from a dropdown and selects the missing kids from another dropdown, then she checks the mark and saves the single ATTENDANCE table record exception for Moana since she is surfing today(or Bethany Hamilton perhaps?) With all the richness that the other dropdowns have collected from the other tables in the schema. Another way to put this, is that the dropdown selection fields have data sources that are "Item collections" from your code tables, and you ultimately store the ATTENDANCE with the goodies from the code tables. Do something for your own education on this item, look up how the items collections work on choice fields in PowerApps and you will be closer to the answer you seek. So, Yes, each ROW is a dated object, with a child name, and class name. This removes redundant data storage of teacher and class from your detailed records, and provides a unique class list of students per class per teacher. I Hope this makes sense, and I wish I could be there (boy do I) to help with this app, but I am stuck in Michigan today. PS (between us coconuts, it's THIRD normal form, not first! Bill Inmon is blushing at you!) Peace, and sunscreen my tropical friend! SmartMeter.

Helpful resources

Announcements

Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

  It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd. at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3rd, 2024 at 9:30 AM PDT and join us for an engaging and informative session!

Tuesday Tip: Unlocking Community Achievements and Earning Badges

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!     THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article!       A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog.       A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions.   Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community

Tuesday Tips: Powering Up Your Community Profile

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   This Week's Tip: Power Up Your Profile!  🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile.     Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today!  💪🚀   Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio  Community Account Support | Power Pages

Super User of the Month | Chris Piasecki

In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons!       Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community.   When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪🌠

Tuesday Tips: Community Ranks and YOU

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!This Week: Community Ranks--Moving from "Member" to "Community Champion"   Have you ever wondered how your fellow community members ascend the ranks within our community? What sets apart an Advocate from a Helper, or a Solution Sage from a Community Champion? In today’s #TuesdayTip, we’re unveiling the secrets and sharing tips to help YOU elevate your ranking—and why it matters to our vibrant communities. Community ranks serve as a window into a member’s role and activity. They celebrate your accomplishments and reveal whether someone has been actively contributing and assisting others. For instance, a Super User is someone who has been exceptionally helpful and engaged. Some ranks even come with special permissions, especially those related to community management. As you actively participate—whether by creating new topics, providing solutions, or earning kudos—your rank can climb. Each time you achieve a new rank, you’ll receive an email notification. Look out for the icon and rank name displayed next to your username—it’s a badge of honor! Fun fact: Your Community Engagement Team keeps an eye on these ranks, recognizing the most passionate and active community members. So shine brightly with valuable content, and you might just earn well-deserved recognition! Where can you see someone’s rank? When viewing a post, you’ll find a member’s rank to the left of their name.Click on a username to explore their profile, where their rank is prominently displayed. What about the ranks themselves? New members start as New Members, progressing to Regular Visitors, and then Frequent Visitors.Beyond that, we have a categorized system: Kudo Ranks: Earned through kudos (teal icons).Post Ranks: Based on your posts (purple icons).Solution Ranks: Reflecting your solutions (green icons).Combo Ranks: These orange icons combine kudos, solutions, and posts. The top ranks have unique names, making your journey even more exciting! So dive in, collect those kudos, share solutions, and let’s see how high you can rank! 🌟 🚀   Check out the Using the Community boards in each of the communities for more helpful information!  Power Apps, Power Automate, Copilot Studio & Power Pages

Find Out What Makes Super Users So Super

We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)

Top Solution Authors
Top Kudoed Authors
Users online (5,929)