Hello,
In a PowerApps app, I have a screen where the users add their signatures inside the PenInput box and inside this screen, I have a button that updates a field in SP List.
What I am trying to achieve is the following:
I want to save for each (current) user signed in their signature image and populate the image signature that is related to the user when they want to sign a report.
For example:
If a user came to sign and it was his first time he will scrabble inside the box to add his signature and when he submit I want to store this signature image that is related to the current user signed in, inside a collection. After that, if the same user came back the next time to add his signature for a new report, here I want a condition that checks if he already has the signature image in the collection so instead of showing the PenInput box and scrabble his signature again I want to populate his signature image that was saved the first time he updated his signature. And vice versa if he never added his signature it will show the PenInput instead.
Is it possible to achieve the above scenario?
Can please someone explains in detail and provide an example?
Any help will be greatly appreciated.
Thank you!
Solved! Go to Solution.
Hi @Julien2 ,
Do you want to use Collection to store the Signature picture for the signed user when he sign in report first time?
If you want to use Collection to store the Signature picture for the signed user when he sign in report first time, I afraid that there is no way to achieve your needs.
The Collection in PowerApps app is a temporary data, which would be destroyed when you close your canvas app. When you re-open your canvas app, the previous saved Signature would be lost.
As an fixed solution, you could consider add a "Multiple Lines of Text" type column in your SP List, then save the Signature picture back to this Multiple Lines Of Text type column.
On your side, you could consider use Patch function to submit data from your canvas app back to your SP List. Please take a try with the following formula:
Patch(
'Your SP list',
Defaults('Your SP list'),
{
UserName: User().FullName,
MulLineTextField: Substitute(JSON(PenInput1.Image, JSONFormat.IncludeBinaryData), """", "")
}
)
Set the Visible property of the Pen Input Box to following:
If(
!IsBlank(LookUp('Your SP List', UserName = User().FullName, MulLineTextField)),
false,
true
)
You could add a Image control in your canvas app, set the Image property to following:
LookUp('Your SP List', UserName = User().FullName, MulLineTextField)
If current sign in user has stored a Signature picture into your SP List, the above Image control would display proper image data.
More details about storing image data back to SP List, please check and see if the following thread would help:
Best regards,
Hi @Julien2 ,
Do you want to use Collection to store the Signature picture for the signed user when he sign in report first time?
If you want to use Collection to store the Signature picture for the signed user when he sign in report first time, I afraid that there is no way to achieve your needs.
The Collection in PowerApps app is a temporary data, which would be destroyed when you close your canvas app. When you re-open your canvas app, the previous saved Signature would be lost.
As an fixed solution, you could consider add a "Multiple Lines of Text" type column in your SP List, then save the Signature picture back to this Multiple Lines Of Text type column.
On your side, you could consider use Patch function to submit data from your canvas app back to your SP List. Please take a try with the following formula:
Patch(
'Your SP list',
Defaults('Your SP list'),
{
UserName: User().FullName,
MulLineTextField: Substitute(JSON(PenInput1.Image, JSONFormat.IncludeBinaryData), """", "")
}
)
Set the Visible property of the Pen Input Box to following:
If(
!IsBlank(LookUp('Your SP List', UserName = User().FullName, MulLineTextField)),
false,
true
)
You could add a Image control in your canvas app, set the Image property to following:
LookUp('Your SP List', UserName = User().FullName, MulLineTextField)
If current sign in user has stored a Signature picture into your SP List, the above Image control would display proper image data.
More details about storing image data back to SP List, please check and see if the following thread would help:
Best regards,
Hello @v-xida-msft ,
Thanks for providing an example and clarified about the collection functionality. I have tried the solution above which makes it works as expected.
But unfortunately, I am still stuck on the visible property of the submission button. This submits button shows only if the Popup variable is true and if the PenInput1.Image is not null. Currently, I have tried to add the following function below which should also check if the Image exists then it should show the button else it should not but it's not working which means it's always invisible and if I used or between the PopUp and the Empty sign the buttons show but if I closed the popup the button keeps appearing:
PopUp && EmptySign<>PenInput1.Image || If(
!IsBlank(LookUp(UsersSignatures, UserName = User().FullName, ImageText)),
false,
true
2. onSelect property, I have a function that also sends for the users their signatures based on the PenInput1.Image, so in what should be the function instead to send for the current user the image that is stored in the SP list?
Office365Outlook.SendEmailV2(
CURRENT USER?,
SelectedReport.ID,
varHTMLImage,
{
Attachments:
Table(
{
Name:"FirstApprovalSignature.jpg",
ContentBytes:PenInput1.Image, // What should be here to get Current user image stored in the sp list to send it in the email?
'@odata.type':""
}
)
}
);
Finally, I received delegation warnings based on this function is that, okay, knowing that my data row limit for non-delegable queries is 2000 in the application.
Looking forward to your response.
Thanks again!
Hi @Julien2 ,
Is the solution I provided above helpful in your scenario?
Regarding the questions that you mentioned is about another issue, please consider open another ticket in our Community, we could help you there.
If the solution I provided above could achieve your needs, please consider go ahead to click "Accept as Solution" to identify my reply as Solution.
For your additional questions:
For your first question, could you please share a bit more about the EmptySign variable? Based on the formula that you mentioned, I think there is something with filter condition which you use to check if the Pen Input is Empty. I have made a test on my side, please consider take a try with the following workaround:
Set the OnVisible of the screen which contains the Pen Input Control to following:
Reset(PenInput1);
Set(EmptySignature, Substitute(JSON(PenInput1.Image, JSONFormat.IncludeBinaryData), """", ""));
Set(IsStart, false);Set(IsStart, true)
Add a Timer control in your screen, set the Duration property to following:
2000
set the Start property of the Timer control to following:
IsStart
set the Repeat property of the Timer control to following:
true
set the OnTimerEnd property of the Timer control to following:
Set(CurrentSignature, Substitute(JSON(PenInput1.Image, JSONFormat.IncludeBinaryData), """", ""))
set the Visible property of the Timer control to false.
Then set the Visible property of the "Submit" button to following:
If(
PopUp = true && EmptySignature <> CurrentSignature,
true,
false
)
More details about how to detect if the Pen input is empty
For your second question, you could not get the stored signature data from your SP List, and assign it to the ContentBytes property within your Office365Outlook.SendEmail() function. The ContentBytes property under Attachments argument is required to provide a Blog data, but the signature data stored in your SP List is a Text value.
As my previous reply, you could add a Image control in your app, set the Image property to following:
LookUp(UsersSignatures, UserName = User().FullName, ImageText)
Then you could modify your Office365Outlook.SendEmail() function as below:
Office365Outlook.SendEmailV2(
CURRENT USER?,
SelectedReport.ID,
varHTMLImage,
{
Attachments:
Table(
{
Name:"FirstApprovalSignature.jpg",
ContentBytes: Image1.Image, // Reference image data from the Image control
'@odata.type':""
}
)
}
);
For your third question, you could consider set the OnStart property of the App to followeing:
Set(CurrentUser, User().FullName)
then you could modify your LookUp formula as below:
LookUp(UsersSignatures, UserName = CurrentUser, ImageText)
then the Delegation warning issue would disappear. Please re-load your app to fire the OnStart property of App, then the issue would be fixed.
Best regards,
Hello @v-xida-msft ,
Yes, it was helpful and I have accepted as a solution. For the next time, I will post another ticket in the community about other questions.
1. I have initialized the EmptySign variable onSelect property of a button that shows the Popup in the same screen and which is the following:
Set(SelectedReport,ThisItem);UpdateContext({PopUp:true});UpdateContext({EmptySign:PenInput1.Image});
Everything is working fine except the visibility of the submit button and what's not working is that if the signature image already exists and appears in the Popup the submit button doesn't appears for another new item for the user be able to submit and send the email whereas if the first time he signed everything works as expected.
Please have a look at the below GIF which shows a new item that the user should submit his signature for this new item and how the submit button is not appearing:
Any suggestions to solve this issue?
Looking forward to your response.
Thank you!
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