cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ericonline
Community Champion
Community Champion

Form with Multiple, Duplicate Entries: Best Practices

Hello, 

 

I'm coming across a common (and complex) pattern within Forms and could use the community's help: 

 

Pattern: 

  • User completes multiple, duplicate entries of some Form fields. 
    • Example: Form for a single Event
      • Task 1 Description
      • Task 1 Start Time
      • Task 1 End Time
      • User clicks "+" button and enters similar info but for Task 2
      • User completes remainder of Form (non-Task fields)
      • What is the best practice for capturing these items? Collection specifically for Tasks? Other method?
  • These Task items should be displayed to the user so they can edit/delete. 
    • What is the best practice for displaying these items? Gallery specific for Tasks? Other method?
      • The Gallery really disrupts the rest of the Form. Hence the ask here. 
  • These items should be written to Data Source using SubmitForm. 
    • What is the best practice for writing these items to their respective tables? 

Example UI: Here is what I end up with, but again, a separate "input bar with "+" for each item" mixed with a Form, mixed with a Gallery (not shown below) makes for a complex UI: 

2018-08-30_7-34-34.png

I know this exercise starts with a logical table design (a good reference for this is the "Data Management Best Practices" forum post). Lets assume I we have that in place for this particular topic. I'm really interested in the UI and App elements here. 

 

Please post your ideas, I'm certain we can all benefit from a standard approach. 

11 REPLIES 11
v-xida-msft
Community Support
Community Support

Hi @ericonline,

 

Could you please share a bit more about your scenario?

Could you please share a bit more about the formula within the OnSelect property of the "+" button?

 

For your first question, do you want to type multiple and duplicate entries within the Edit form for different tasks?

 

If you want to type multiple and duplicate entries within the Edit form for different tasks, I think the Collection could achieve your needs. You could consider take a try to store the form data as a Collection (TempCollection) using ClearCollect function, then if you want to reference the same value within the form for Task2, you could pull data from the TempCollection.

 

I have made a test on my side, please take a try with the following workaround:12.JPG

 

13.JPG

 

Set the OnSelect property of the "+" icon button to following formula:

ClearCollect(TempCollection,Form1.Updates);ResetForm(Form1)

Note: The Form1 represents the Edit form control within my screen.

 

Set the Default property of the Data card (which you want to remain same value as previous form) to following formula:

If(Form1.Mode=FormMode.New,First(TempCollection).Title,ThisItem.Title)

For your second question, if you want to display all task items within your app, I think the Gallery control could achieve your needs. You could consider take a try to create a sparated screen within your app, then within this screen, add a Gallery control to displays these task items.

 

For your third question, do you want to write these items back to one data source or each item to a separated data source? 

 

If you want to write data back to your data source, please check if the Patch function and SubmitForm function could help in your scenario.

 

Patch function, SubmitForm function

 

Best regards,

Kris

 

 

 

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi @v-xida-msft (Kris), 

 

Thank you for putting some thought and energy into this. Its a tough problem to explain and I'm afraid I wasn't clear enough. Let me clarify a bit more: 

 

RE: The "+" Button OnSelect property: 

  • I do indeed ClearCollect the results and display them in a gallery below the Form fields. 
  • Unfortunately, this results in what I would call, a complicated User Experience where 3 elements coexist in the same area (Repeating Field-input area, Gallery displaying Repeating Field inputs, and the remaining Form fields). 
  • This complicated UX is what I'm trying to solve for in the post

 

Here is what I'm going to try (no visuals at this time to share): 

  • Make the Repeating Field-input area and Gallery look like they are part of the Form
  • Goal will be to make all Controls look like a single Form to ease UX. 

Will report back soon!

 

Thanks again.

@ericonline

 

This is what I have come up with some of my apps.

 

We have a lot of InfoPath documents we are migrating to PowerApps

 

One document, in particular, has about 150 Questions. So having multiple screens is really not an option. (Unless the user wants to click the next button all day). 

 

I created a data form with dynamic positioning based on the previous control but we also had other tables with foreign keys in this document. So we had to add galleries into the PowerApp (Which is technically not a feature). The only problem is that when you get too far down the document with the galleries in the app and try and add an entry it causes the scrollbar position to go all the way to the middle of the DataCard.

 

This issue is described here but I found if you turn the "New Improved App Rendering" off then it works, but then you have other errors because you are using the old rendering engine.

 

If anyone has any other suggestions on how to make a scrollable screen with a one to many relationship I am all ears.  

wyotim
Resident Rockstar
Resident Rockstar

Great topic @ericonline! And I completely agree with your opening statement that this is a common issue. 

 

I worked out a bit of a solution for a one-to-many problem (as @JonathanWest so eloquently described it) that I will try to describe in the hopes that it can add something to this discussion and we can all work out a good best practice. Wall of text inbound!

 

*edit* Out of respect for everyone and the massive scrolling they might endure, I put my wall of text in a spoiler tag.

 

 

Spoiler

We have a wire rope inspection section in our maintenance app in which our supervisors input the results of inspections of a number of wire ropes on a rig. There are about 13-18 individual wire ropes with between 1 and 5 user inputs for each one, the number varying by whether the rig has one or two winch lines and what guy-securement systems they use. Essentially, the wire ropes would parallel the tasks in your scenario. There are also related items in our inspection (drum inspections, notes, etc.) that parallel the non-task fields in your scenario. In total, there are three different data tables storing inspection data: one which has entries for all maintenance tasks, one for the wire rope inspections, and one for related aspects of the inspection as mention before. This is also a phone app, so much of the design is a result of that choice.

 

The way I sorted it out for us was to not use forms or galleries. Instead, I built a form-like structure that shows/hides and formats input areas based on a page-like navigation system. This also allowed the freedom to group input items that are related but not in the same data tables (i.e. no restrictions from galleries or forms). It was a bit of work but, in the end, I think it was worth it. Plus, I couldn't find another way to do it. Smiley Very Happy In the case of having 150 different questions, this would be a tough build but depending on the questions, I would think there could be some way to do it where input areas could be reused and the layout was such that there could be a tenable pagination structure.

 

The navigation is controlled by a collection that acts like an index and is generated by the app for the specific inspection based on what rig is selected. Basically, there are buttons that change dynamically based on what the previous and next items in the index are, and these allow the user to go back and forth between items to enter data. I could see dynamically adding and removing items to this index, such as with your "+" button to add tasks. Also, the index has a key built in to tie it to the type of wire rope being inspected. 

 

Inputs for the inspection are stored first in temporary tables, allowing the user to enter/edit inputs before submission. This actually came as a result of the app requiring offline functionality but it turned out to be a really great way to handle the one-to-many aspects. This makes it pretty easy to enter and check the data without constant writing to the source as well. When the user has completed putting in the required items, they can then submit the data. This is done through a Collect in our case as the data is a one-time submission (it wouldn't be prudent if they could edit inspections after the fact). In the case where users need to go back and edit data, it would be possible to pull data into the temporary tables and use Patch instead of Collect.

 

One note on this: the offline functionality/temporary table structure necessitated de-normalizing the data a bit so that there was some sort of key to tie the items together in lieu of a SQL generated ID. I ended up using a composite of the user ID, inspection date, and equipment ID in each table, which has worked well. 

 

On the display/review side, this is where my approach differs quite a bit. Instead of a data review or anything like that, I created a graphic of a top-down view of a rig with the wire rope locations color-coded based on the completeness and quality assessment. I would assume having a summary shown from what is stored in the temporary tables would work, perhaps using a gallery based on the index and custom fields to display relevant information.

 

So, those are the high-level aspects of what I came up with. My solution is a bit complex but I didn't see any other way at the time given the needs associated with the scenario. Feel free to critique it or ask for more detail if you like. This was actually the first PowerApp I ever built, so I am sure there is plenty of room for improvement.

 

 

As stated before, this seems a common scenario and if we can work out some best practices I suspect it would be very helpful to a number of people.

Awesome write up @wyotim

 

I have a couple questions for you: 

 

  • When you say "I built a form-like structure that shows/hides and formats input areas based on a page-like navigation system."
    • Does this mean you created your own "form fields" with labels, asterisks, error messages, error handling, ect.?
    • If so, what are some best practices for this? I got stuck here a while back where I had to manually write all the error handling. Was quite a challenge.
  • Wow! "...a collection that acts like an index and is generated by the app for the specific inspection based on what rig is selected"
    • This I'd like to know more about! 
    • How is the collection initialized?
      • If user selects Inspection A, Collection A is initialized, If Inspection B, Collection B is initialized?
    • How does the app "traverse" the "index"?
      • When user clicks "Next" button, Lookup(indexCol, some=condition, result) ? 

Dude! Neat stuff. Are you ever in Seattle? We should hang out!

@ericonlineFor the first question, essentially yes, with some caveats.

 

The labels and inputs are dynamic in some cases so they change as the user selects different items.

 

In my case, all the items are required except for the notes area, so my primary validation method is making sure there are inputs for every item. Some of the items are radio controls but the majority of them are numerical, so the text boxes are set to numerical inputs which solve the majority of issues with the data entry. The user's inputs are assessed right away as the app compares the input to a specified boundary based on the wire rope type so they get instant feedback on what they entered, making it easy to see errors before submission. In that regard, the error handling is pretty light and handled in the input field before submission.

 

This does put a lot on the user but hopefully is enough to guide them and let them know if data was mis-entered. A complication with this is that an entry outside the normal bounds could be a legitimate entry, which is another reason for the light approach. Another aspect is that every completed inspection triggers an email with an out-of-bounds items noted so that our operations managers can review the data, so while not technically part of the error handling in-app, it is part of the process.

 

I am not sure if there are too many best practices to glean from my approach and I am definitely open to input as I want/need to grow in this area!

 

On the second question, the collection is initialized in the OnVisible section of the inspection screen, based on the selection from a gallery. There are two key items for our situation that decide which of the two versions to use, so a simple If statement is all that is needed. 

As far as traversing the index, I use a UpdateContext on an arrow button to track a number. The number relates to the position in the index and is used for the text labels. I'll include my code so you can see it:

 

/* Button code for the next item */
If(
    CurrentInspectionItem.Text = "Winch Line 1" ,
    If(
        LookUp(RigCollection, EquipmentID = EquipmentListBrowseGallery.Selected.ID).WinchLineCount = 1,
        UpdateContext({LocationVariable: LocationVariable + 2}),
        UpdateContext({LocationVariable: LocationVariable + 1})
    ),
    If(LocationVariable < 19,
        UpdateContext({LocationVariable: LocationVariable + 1}),
        ""
    )
) /* Text code for the next item */ Substitute(
    If(
        CurrentInspectionItem.Text = "Winch Line 1",
        If(
            LookUp(RigCollection, EquipmentID = EquipmentListBrowseGallery.Selected.ID).WinchLineCount = 1,
            LookUp(RigWireRopeLocationCollection,
                ID = LocationVariable + 2,
                RigLocationName
            ),
            LookUp(RigWireRopeLocationCollection,
                ID = LocationVariable + 1,
                RigLocationName
            )
        ),
        If(
            LocationVariable = 19,
            "",
            If(
                LocationVariable = 18,
                "Notes",
                If(LocationVariable = 17,
                    "Clamps",
                    LookUp(RigWireRopeLocationCollection,
                        ID = LocationVariable + 1,
                        RigLocationName
                    )
                )
            )
        )
    ),
    If(
        LookUp(
            RigCollection,
            EquipmentID = EquipmentListBrowseGallery_1.Selected.ID,
            Sheaves
        ) = true,
        "/Boomer",
        "Sheave/"
    ),
    ""
)

For updating the number, the main complexity for my scenario is knowing if the rig has one or two winches and if the list is at the beginning or end of the list. The previous item button code is much the same just checking if the number is less than one to show that the selected item is the first one. 

 

For the text, the complexity is a bit greater in that some items are altered (the Sheave/Boomer is truncated based on what the rig actually uses) and some items have to be made because they aren't wire rope items (Clamps and Notes). Obviously, this is before I learned to use the If statement in a non-nested way. I need to update the code a bit!

 

The number is the PK for the wire rope type, so I can reuse it to help in the quality assessment as well as setting up what should be shown/hidden and how it is formatted. That is essentially what everything is based on. The temp tables are also pre-made and ready for input. There is an Update function in the OnChange area of each input field so that it goes to the right place.

Unfortunately, I don't get to Seattle that often but maybe that needs to change. The last time I was in town was for the Microsoft Data Insights Summit last year, which was the old name for the Business Applications Summit. I didn't make it to the Summit this year sadly. If I head up to your area, I will shoot you a message for sure!

 

Let me know if I can clear anything else up. It's a bit difficult to describe but hopefully what I wrote is decently understandable. Again, feel free to offer any suggestions or critiques. There is plenty of room for improvement on my side and it would be great to get to a best practice of some kind for these scenarios.

*edit* Screenshot for reference. Again, this is the first app I ever made so any chuckling at the design is warranted. The color scheme is an attempt to use brand colors and results in a pretty bold scheme. I am in the process of revamping this app now, so it won't actually look like this by the end of the week.

 

2018-09-05 (1).png

 

 

@wyotim

So let me ask you this.

I may not be understanding your app very well but why didn't you just use different screens and navigate to them instead of hiding controls and what not. You still would have to build a Navigation Model for it depending on the entity and what questions needing to be asked.

That is a great question. I guess for two reasons: first, because the idea never occurred to meSmiley LOL

 

Second, because this app was already pretty screen heavy (it was at like 19 or so at that point), I was just trying to not have to build more onto it by that point. It was the first PowerApp I had made and I started on it basically when PowerApps went GA and released the first version in about 6 weeks. Truth be told, it was the first app I had ever made, not just my first PowerApp. My main experience is in Excel/VBA, which is a bit of a far cry from PowerApps, so I had/still have a lot to learn.

 

And really, once I got to the temporary table aspect along with the index, it was pretty easy to map the data to and from the input areas so it seemed a good approach at the time. And it has held up pretty well too. While I am currently redesigning the app, that approach is staying. (I am cleaning up the code a bit though. Those unnecessary nested Ifs...)


Mainly because the idea never occurred to me though. That does seem like it would be a cleaner approach (and the more obvious one in hindsight). Again, great question!

wyotim
Resident Rockstar
Resident Rockstar

So in thinking a bit more about this, I realized there are some other areas that have a similar one-to-many structure which I approach in a much simpler manner. We have an area in an app to track and enter employee information such as training records. There are a number of these trainings that must be renewed, be it annually or some other multi-year scale. The way that I display these is in a nested gallery. I then have a pop-out form to add/edit/delete entries.

 

In keeping with the use of forms and the SubmitForm function, what about having a form for tasks and a form for the rest of the items? (Assuming this is a two-table design that is; you would need a form for each table basically.) On the tasks form, it could have a button to add another task (which would submit the current form and refresh it for another entry), and a button that went to the form to add the rest of the data (which would also submit the task form). 

 

The information could then be shown in a nested gallery (a gallery of galleries?) next to the form area which would add the information as it is submitted, giving the user a view of their submissions. There could be buttons to allow the user to add/edit/delete from the gallery as well, which would bring up the applicable form.

 

This is certainly simpler in design than my previous offering. The main downside I see is how slow it would be to enter data. One monolithic form would be much faster for sure.

Helpful resources

Announcements

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders     UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Win free tickets to the Power Platform Conference | Summer of Solutions

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the challenge.   Week 1 Results:  Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   Week 2 Results:  Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Top Solution Authors
Top Kudoed Authors
Users online (1,947)