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

Power Apps V2 - Again

For those who have helped me in the past I beg your patience.

I am still struggling mightily to under how to make Power Apps V2 work for me.

I have a Power Apps with an attachment upload screen.

I am using Power Apps V2 for the first time, to upload attachments to an SP Library.

I managed to get bits and pieces of meta data to the library put I can't view attachment when I open.

Goal:
Use Power Apps V2 Create File to upload document, and an Update file (properties only) to append 'Client ID', 'Document Name', 'Attachment Comment' from the Power App screen to the attachment/item being uploaded.

SP Library -

Phineas_0-1696022997184.png

Power App Screen -

Phineas_1-1696023070597.png

 

Power App Submit Button Formula -

Phineas_2-1696023151219.png


My flow -

Phineas_4-1696023242933.png

2 ACCEPTED SOLUTIONS

Accepted Solutions
Pstork1
Most Valuable Professional
Most Valuable Professional

The error is because you have 5 string parameters and one file parameter but supply 4 text values and one file value.  you need to specify the same number of parameters as you define in the flow.

 

Part of the problem may be that you aren't saving and refreshing the flow in Power Apps between making changes.  The intellisense in Power Apps shows 4 text parameters when you've defined 5f and doesn't show the file parameter at all. Anytime you make a change to the flow you need to save it and then refresh it in Power Apps.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

View solution in original post

Pstork1
Most Valuable Professional
Most Valuable Professional

You are still using Document type for the file name when creating the file. You won't be able to open the file if it doesn't have a file extension that matches the contents of the file.  Your document name doesn't have an extension. Also your run line has 4 strings, but 5 text parameters are defined in the flow. I've already pointed out that the run() has to match the actual parameters you define. Yours don't



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

View solution in original post

24 REPLIES 24
Pstork1
Most Valuable Professional
Most Valuable Professional

For the ContentBytes value in the File record you are sending do not use JSON() to process the image.  Just reference the file in the attachment control directly.  Here's an example from one of my apps. In this case I'm only sending the first file in the attachment control.

 

UploadFile.Run(First(AttachmentControl.Attachments).Name,
  {file: {name: First(AttachmentControl.Attachments).Name,
  contentBytes: First(AttachmentControl.Attachments).Value}})

 



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Phineas
Community Champion
Community Champion

Thank you.

How do I write the other fields in to the formula?

Pstork1
Most Valuable Professional
Most Valuable Professional

The first parameter is just a string so Label15.Text will work for that.  Other than that what do you mean by the other fields in the formula?



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Phineas
Community Champion
Community Champion

Trying to get all this in but can't get the language correct.

Top of code window has -
Run(text, text_1, text_2, text_3, text_4) | text: Input

This is the code I'm trying -
UploadClientDriversLicenseDocumentsFlow.Run(
{text_1: Upload_Client_ID_Fld.Text,
text_2: Label15.Text,
text_3: TextInput1_3.Text,
text_4: Label1.Text,
{text: {name: First(Client_Attachments_Control_2.Attachments).Name,
contentBytes: First(Client_Attachments_Control_2.Attachments).Value}});

My flow -

Phineas_0-1696027807420.png

 



Pstork1
Most Valuable Professional
Most Valuable Professional

The parameters in the flow trigger need to match what you are submitting. You've got 5 string parameters, but your code is submitting 4 text parameters and a non-standard JSON record. The last parameter needs to be of type file and use the keyword file: not text: 

 

You can't send a JSON record other than specific types like {file:...} as a parameter.  



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Phineas
Community Champion
Community Champion

I am still unsure on the structure or how to interpret your clarification completely.

I've updated the formula to the following, and I am getting an error at the end. Say 'The formula contains CurlyClose where ParenClose is expected. 

UploadClientDriversLicenseDocumentsFlow.Run(
{Input: Upload_Client_ID_Fld.Text,
ClientID: Label15.Text,
AttachmentComments: TextInput1_3.Text,
ReprenstingDocument: Label1.Text,
file: First(Client_Attachments_Control_2.Attachments).Name,
contentBytes: First(Client_Attachments_Control_2.Attachments).Value}});

Phineas
Community Champion
Community Champion

I've been at this for three days, across three or four forum folks, and still can't get it.

I've watched this video 10 times. I can't figure out how to incorporate his work into mine.
          https://youtu.be/yDRzgl9JysU

He's sending an email; I'm trying to upload attachments. Not exactly the same, which makes it difficult for me to translate.

If you could help me with the 'actual' writing of the code - as much as I appreciate the guidance and words of wisdom, that would be great.

I've re-written my code a hundred times and haven't gotten it right.

Admittedly, I have some cognitive limitations, but I've come a long way.

Pstork1
Most Valuable Professional
Most Valuable Professional

The file parameter needs to be passed as a JSON record.  You are missing the opening { for the record. That's why you are getting the error.  Also the string parameters don't have keywords. They are identified by their position in the list. It should be

 

UploadClientDriversLicenseDocumentsFlow.Run(
Upload_Client_ID_Fld.Text,
Label15.Text,
TextInput1_3.Text,
Label1.Text,
{file: First(Client_Attachments_Control_2.Attachments).Name,
contentBytes: First(Client_Attachments_Control_2.Attachments).Value}});

 



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Pstork1
Most Valuable Professional
Most Valuable Professional

See my response above where I've added the missing brace { to your code.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Phineas
Community Champion
Community Champion

Thank you, for your patience and assistance.

I placed the following in the submit button and got the following error -

     'Invalid argument type (Record). Expecting a Text value instead."

Phineas_0-1696045460742.png

 

Pstork1
Most Valuable Professional
Most Valuable Professional

Did you add a File type parameter as the fifth parameter like you had in the earliest screenshots? The error says you are trying to pass the file type parameter to a text parameter.  Can you provide a screenshot of the current trigger?



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Phineas
Community Champion
Community Champion

Are you meaning here, circled?

Phineas_1-1696086316838.png

 

Also, I am seeing that maybe I should have 'varBase64Only' in the SharePoint formula (shown below), and/or maybe in the flow (at the arrow shown above) in order to be able to view the documents.

Your thoughts?

UploadClientDriversLicenseDocumentsFlow.Run(
Upload_Client_ID_Fld.Text,
Label15.Text,
TextInput1_3.Text,
Label1.Text,
{file: First(Client_Attachments_Control_2.Attachments).Name,
contentBytes: First(Client_Attachments_Control_2.Attachments).Value}});

Pstork1
Most Valuable Professional
Most Valuable Professional

As I explained in an earlier reply you can't send the file content as a text string. You have to send it as a  file record. To do that the parameter needs to be created as a file parameter not a text parameter. What you have circled is a text parameter.

 

And no you don't need VarBase64 if you send the file as a file record you will have the right file contents to make it viewable. 



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Phineas
Community Champion
Community Champion

Yes, sir; Though, I still can't quite translate your instructions into what to actually do.

That said, I think I'm getting close.

My Library: I finally got all the content in the correct columns, when I test the flow manually from Power Automate -

Phineas_0-1696092764799.png

My Flow: When I test manually it delivered the above output to the Library.

Phineas_1-1696092922334.png


My Power App: This is where I'm running into some of the problems. I believe I've got the input order correct; However, I don't know how to finish it. What is the language for the record. This is where all that basetobinary use to go in the old Power App. 

Phineas_3-1696093476214.png

 

 

Pstork1
Most Valuable Professional
Most Valuable Professional

The final parameter is a record with a keyword of file: It contains a record that has two properties with the keywords of name: and contentBytes: Name: is a text property and contains the filename you want to use for the file in the flow. ContentBytes is the Value property pulled from one of the files in the attachment control on your screen. The attachment control can hold multiple files, So its a collection/array or files. If you only want to upload one file then you can get the value using first(NameOfAttachmentControl).Value. You can get the current name of the uploaeded file using first(NameOfAttachmentControl).Name. So to pass that as a file record it takes the following record format for the final parameter.

 

{file: {name: {first(attachmentControlname).name, contentBytes: first)attachmentControlname).value}}

 

 



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Phineas
Community Champion
Community Champion

Power Apps was fine with this - 

Phineas_1-1696099996484.png


Power Apps didn't like the addition. Also, it wouldn't take attachment language with the last text parameter; I got (Received 6; Expected 5) error.

Error:
'Invalid argument type (Record). Expecting a Text value instead'

Phineas_3-1696100497772.png


Should the 'FileName' have a default parameter and not one I add - such as 'DocumentType'?

Phineas_2-1696100330404.png

 

Pstork1
Most Valuable Professional
Most Valuable Professional

As I've said before you need to add a file parameter as the last parameter in the trigger. Your screenshot still shows 5 string parameters and no file parameter. That's why it doesn't like the file: record. there is no file parameter. The filename can be either passed seperately or as the Name: attribute of the file record.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Phineas
Community Champion
Community Champion

If I may, pleading through teary eyes and sniveling nose...can you show me what that would look like, please?

 

It ought to be obvious, by now, that I am not understanding this last part.

 

Thank you.

Pstork1
Most Valuable Professional
Most Valuable Professional

I'm not sure why you are using the Document Type parameter for the name. I assume that is a mistake.  But assuming you need the rest somewhere in the flow it would look like this

image.png

And the run command would be this

UploadClientDocuments.Run(
Upload_Client_ID_Fld.Text,
Label15.Text,
TextInput1_3.Text,
Label1.Text,
{file: First(Client_Attachments_Control_2.Attachments).Name,
contentBytes: First(Client_Attachments_Control_2.Attachments).Value}});


-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

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!

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

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 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**

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. 

Users online (3,533)