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.

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.

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.

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}});

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.

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.

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.

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.

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.

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

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

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

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**   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 SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (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. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     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 Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22  

Updates to Transitions in the Power Platform Communities

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

Users online (3,029)