So I've made an app for our small library. I want to add a button to the detail screen for a quick checkout. Right now users have to use the edit screen to add in their name and it'll mark the book as unavailable. However, I'd love to have a button specifically for checking out and/or returning a book. When they hit the button I want it to take their username and fill in the "Checked out By" field for them. Then vice versa. I thought the patch function would be all I needed.
Patch(IPC_LIB, ThisItem.'Checked Out By', User())
I'm probably just using the wrong syntax I assume. Any suggestions?
Solved! Go to Solution.
Yes, you can definitely do that and it will work. However, given what we're looking at, you shouldn't have to do it since you're patching the datasource directly.
However, you might want to change that formula just a bit...
Patch(IPC_LIB,
BrowseGallery1.Selected,
{'Checked Out By' : If(IsBlank(BrowseGallery1.Selected.'Checked Out By'),User().FullName,"")}
);
Refresh(IPC_LIB);
Back()
Just taking out the logical AND operator you had in there and putting the refresh first.
Assuming your 'Checkd Out By' column is a People column...
Try changing your Patch function to this formula:
Patch(IPC_LIB, ThisItem or Lookup, <- You need to specify the record you want to patch { 'Checked Out By': { '@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedUser", Claims:"i:0#.f|membership|" & Lower(User().Email), Department:"",
DisplayName:"", Email:"", JobTitle:"", Picture:"" }
}
)
NOTE: the above you must specify the record you want to patch. If you are in a Gallery that has the record from the datasource, then you can use ThisItem. If you don't have it, then you will need to use a Lookup to get it - Lookup(IPC_LIB, someColumn=someValue)
I hope this is helpful for you.
Honestly, this went a bit over my head. The "checked out by" was not a "person" column so I went ahead and made a column just called "check" that uses people.
I had assumed your column was a Person column only because you were trying to assign User() to it.
If you want to patch a Person column, you need to specify the record as I showed in the formula example.
If you want to patch a text column, you just need to change your User() to User().FullName (or one of the other values available on the User function)
Hi @Salamander94 ,
Do you want to add the "Check out" button within your Detail screen (display detail info of a specific book)?
Could you please share a screenshot about your app's configuration?
I assume that you use a Gallery control in your app to list all available books in your small library, and then within the Detail screen, display the detail info of a specific book selected from your Gallery, is it true?
Based on the formula that you mentioned, I think there is something wrong with it. I have made a test on my side, please take a try with the following workaround:
Within the Detail screen, set the OnSelect property of the "Quick Check out" button to following formula:
Patch( 'YourDataSource', /* <-- 'YourDataSource' represents the data source to store your Library books in your app */ BrowseGallery1.Selected, /* <-- BrowseGallery1 represents the Gallery in your app to list all available books in your small library */ { 'Checked Out By': User().FullName } )
Note: The 'Checked Out By' column is a Text type column in your data source.
In addition, you could also consider add a "Quick Return" button in your Detail screen, set the OnSelect property to following:
Patch( 'YourDataSource', /* <-- 'YourDataSource' represents the data source to store your Library books in your app */ BrowseGallery1.Selected, /* <-- BrowseGallery1 represents the Gallery in your app to list all available books in your small library */ { 'Checked Out By': "" } )
More details about the Patch function, please check the following article:
Best regards,
So this check out and return button does work. However, it seems like I have to click the button a few times in order for it to update on my screen then I get an error.
Can you provide your current formula and also explain a little more about what you are expecting to have updated on the screen when you click the button. Also any other formulas you might have that are of any significance.
Okay so here is my detail screen:
Here is the code for "Check Out"
Patch(IPC_LIB,BrowseGallery1.Selected, {'Checked Out By': User().FullName})
Here is the code for "Return"
Patch(IPC_LIB,BrowseGallery1.Selected, {'Checked Out By': ""})
Now on the edit screen I had the "Available?" Field automatically update when someone entered their name or deleted their name. Here's the code:
If(IsBlank(DataCardValue10), "Yes", "No")
Now I tried using this on the detail screen, but it does not update automatically like it did in the edit screen. The only difference in the formula being the "datacardValue".
So what seems to happen on the detail screen is when I hit the button once to check out, nothing updates. If I hid it a second or third time it finally registers. Same with the "Return" button but I still get that error message. As I'd said before the "Available?" Field no longer updates within the detail and edit screen automatically either.
Here's the code for my browse gallerey:
SortByColumns(Filter(IPC_LIB, StartsWith(Title, TextSearchBox1.Text)), "Alphabatize", If(SortDescending1, Descending, Ascending))
Thanks for all your help and let me know what else, if anything, you need.
In addition, ideally I just want the "check out" button to fill in their name to the "checked out by" field and then make the "Available?" field switch to no. Vice versa I want the return button to delete their name and set the "Available?" field to "No". It seems like the available field no longer updates on the gallerey either.
So, a couple things here:
You're using an Edit Form for this, so, you're going to need to submit it or refresh it since you are trying to do a Patch within it. It makes me ask the question, do you need to do this Patch? If you submit the form on your "Check Out" button instead, that would resolve some of this quicker. This is a design choice, but I would consider having only one button. It would change based on the value or lack of value in the 'Checked Out By' column:
Button Text Property: If(IsBlank(BrowseGallery1.Selected.'Checked Out By'), "Check Out, "Return")
The button would have a very simple action:
SubmitForm(yourFormName)
The Update Property of your DataCard for the 'Checked Out By' column would have the following:
If(IsBlank(ThisItem.'Checked Out By'), User().FullName, "")
As for the Available column...I would just base that off of the 'Checked Out By' value. Not sure you really need it on the EditForm as it is not something that someone would change.
If it is a column in your datasource, then you can set the Update Property of the DataCard for the Available column to the following:
If(IsBlank(ThisItem.'Checked Out By'), "Yes", "No")
This would take care of all the refreshing and updating and not require any Patch functions.
See what you think about that...
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
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** 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. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (tie) 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. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages