cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Create multiple Attachments in single powerapp screen and share to sharepoint list.

How should I create multiple attachments datacards in single powerapp editform screen and send all the attached files to sharepoint list in attachments. I tried to add multiple attachments but they send only one file to sharepoint from first attachment datacard. I need to collect all the files attached in all the attachemnt datacards in sharepoint list. Any way, hack or method would be helpful.

17 REPLIES 17

Microsoft Advice

So, it should be possible, but you would have to do this in a custom way. Your best bet is to use custom cards and add additional upload controls. What you would need to do, when the form is submitted, is patch these extra files as attachments.  You may need to use Power Automate in combination with Power Apps to achieve this.



See attachment

Thanks @KayBains !

ashwanidv100
Frequent Visitor

Unfortunately I don't have access to my this account. I'm started using other account which is @ashwanidv100 

Thanks @KayBains for you responses and answers.

@Lilian1331 ,

Q. How did you resolved this Issue?

A. I was able to consult it through to on my project instead of hitting this wall. I did used multiple attachments using one datacard. As It was yearly data submission at once. I was able to manage to distribute on a monthly basis. So That helped me to save a lot files to not be submit at once but frequently. So In my part was consulting on the possible ways to manage things out, if the system is having limitations.

ashwanidv100
Frequent Visitor

@Lilian1331 ,

 

I was novice at that time, But if you ask me now. 

 

I would say don't use patch function, but simply use power automate to manage it somehow. 

 

1. Create a single list and create a 3 Editforms for the same list with different names, Use the attachment datacard. 

2. When submit the forms, Use power Automate and keep the attachments in sharepoint docs or wherevers you like to store them in a specific folder.

3. Use unique name for each folder can be created easily by following a right nomenclature.

4. Generate the link and store it in the SharePoint list column and may call it 'Link to attachments' or 'Something else you like'.

5. And it just instead of storing the files directly to list record it will have a path of where its stored in a SharePoint docs.

 

Hope this help you somehow to guide you to think about it.

 

Ash

 

KyleJ
Helper II
Helper II

@Lilian1331 
@KayBains @Anonymous 
I have a solution.

When you patch an item, you are able to save the patch to a variable, giving you the newly created ID number. From there, you can patch updates to that same record via ID. 

We know, you can

Patch(YourDatabase,Defaults(YourDatabase),{Field:"Value"},form1.Updates)

But lets expand on this. In ONE SINGLE submission, we need to accomplish a few things. You can first submit the record as above, with 1 of your attachments being submitted. But, lets go ahead and grab the newly created ID by wrapping a Set Variable around the Patch Function. 

Set(PatchedID,Patch(YourDatabase,Defaults(YourDatabase),{Field:"Value"},form1.Updates))

The above code will now submit the record and all fields, and it will add the first attachment, and return to the variable the ID (among other info) 

We can now execute, two additional patch functions. 

Patch(YourDatabase,LookUp(YourDatabase,ID=PatchedID.ID),Form1_1.Updates);
Patch(YourDatabase,LookUp(YourDatabase,ID=PrevPatchedID.ID),Form1_2.Updates);

All together, these three functions (the first being the "Set(Patch())" ) all together will submit multiple attachments from multiple sections of 1 singular form, into 1 single record. 
Finished code should look about like this: 

 

 

 

Set(PrevPatchedID,Patch(Datasource,Defaults(Datasource),{
    Title:TextInput.Text,
},Form1.Updates));

Concurrent(
Patch(Datasource,LookUp(Datasource,ID=PrevPatchedID.ID),Form1_1.Updates),
Patch(Datasource,LookUp(Datasource,ID=PrevPatchedID.ID),Form1_2.Updates)
)

 

 

 




ashwanidv100
Frequent Visitor

Thanks @KyleJ , 

 

Yes, This is one of the possible solutions that someone can think of and may use the same 👏

 

The main intension to my proposed solution was to store the attachments handy and available in structured way (folder wise). Because in generally we ended up using power automate as a part of power suite solution So those files can come handy for sending it forward and do more with that.  

 

Ash

Doodooo
Frequent Visitor

In case anyone else is having trouble handling multiple attachments and stumbled upon this post, as I did, let me explain how I managed to handle it. It's not the most elegant solution, but it works and might help someone in the future.

 

As has already been mentioned - MS Lists allow to store only 1 attachment in the Attachment column. Therefore, if you need more than 1 attachment per record, your best bet is to create a separate MS List to store just your attachments and link this list via Relationship to your main list.

I created a list that has only 4 columns:

  1. Attachment ID - the primary unique column, changed from the default Name and set the Autonumber data type on it
  2. Attachment - File data type, stores actual attachments
  3. Attachment name - String data type, not really required for this solution to work, but without it you won't be able to see attachment's name in the list.
  4. Request ID - reference to the main table's primary column

 

Then, in order to upload or update the attachments, you need to have a separate form for your attachments in addition to your main form in your Power App that will handle the Attachments. It should consist of only 1 datacard with Attachments control. Make sure that your control has a MaxAttachments property set to more than 1.

 

This is the formula I used in the OnSuccess property of my main form NewRequestForm. First, it stores the attachments from DataCardValue1 (which is an Attachments control that has Attachments) into a collection, and then we Patch it into the AttachmentsList, which is the aforementioned MS List that stores only attachments. I found that you need to add a column FileName in order for the attachment to be understood by MS Lists, which you can fill in with the values from Name column from the Attachments control.

// Store attachments in a new collection
Set(lastCreateRequest, NewRequestForm.LastSubmit);
ClearCollect(NewAttachmentsCol, AddColumns(DataCardValue1.Attachments, "FileName", Name));

// Upload attachments
ForAll(
    NewAttachmentsCol, 
    Patch(
        'AttachmentsList',
        {
            Attachment: ThisRecord,
            'Attachment Name': ThisRecord.Name,
            'Request ID': lastCreateRequest,
        }
    )
);

There you go, uploading attachments to the list should work now.

 

Updating attachments in the list is slightly more difficult, as you need to manually keep track of which attachments has been added or removed from the control (at least that's the only solution I found that works). I have a separate form for updating the records called EditRequestForm.

 

First, you need to load the records into your Attachments control. In my case, I select the record in the RequestIDComboBox which is a ComboBox control linked to my main list.

This is the formula that goes into OnChange property of this Combobox control.

The VariablesCol is a collection that is used to keep track of the current record number in the ForAll loop, as Power Apps don't allow Set formula to be inside the loop. In the formula we just iterate through the attachments and store them in the LoadedAttachmentsCol.

learCollect(VariablesCol, {FirstVar:0});

ClearCollect(LoadedAttachmentsCol,Blank());

ForAll(RequestIDComboBox.Selected.'AttachmentsList',
    Patch(VariablesCol, First(VariablesCol), {FirstVar: First(VariablesCol).FirstVar + 1});

    Collect(
        LoadedAttachmentsCol,
        {
            Name: Last(FirstN(RequestIDComboBox.Selected.'AttachmentsList', First(VariablesCol).FirstVar)).Attachment.FileName,
            Value: Last(FirstN(RequestIDComboBox.Selected.'AttachmentsList', First(VariablesCol).FirstVar)).Attachment.Value,
            ID: Last(FirstN(RequestIDComboBox.Selected.'AttachmentsList', First(VariablesCol).FirstVar)).'Attachment ID'
        }
    );
);

 

Then, you can set your Attachments control's Items property to reference this newly created LoadedAttachmentsCol. Voila, your attachments are now shown in the control whenever you change the Combobox selection. You might need to change the Name and Value properties too to Name and Value columns accordingly, in case it shows some weird values.

 

Now, in order to upload these to the list you need to keep track which attachments have been added and which have been removed in the meantime by the user. This is the formula I have on the OnSuccess property of the EditRequestForm that I use for updating my main list. First, it stores currently loaded attachments from the DataCardValue2 (which is also an Attachments Control) in UpdatedAttachmentsCol. Then, it compares it against the initially loaded attachments that we already have stored in LoadedAttachmentsCol and based on the comparisons, it will store this record in either AttachmentsToBeUploadedCol or AttachmentsToBeRemovedCol. Finally, it uploads the new attachments with the Patch formula (same as we did at the beginng when adding new attachments) and removes the not required attachments with the Remove formula by filtering the list by Attachment ID that we grabbed when we loaded the attachments from the list.

// Store updated attachments in collection
ClearCollect(UpdatedAttachmentsCol, AddColumns(DataCardValue2.Attachments, "FileName", Name));

// Compare initially loaded attachments with updated attachments to see which ones are new to upload
ClearCollect(AttachmentsToBeUploadedCol, Blank());
ForAll(
    UpdatedAttachmentsCol,
    If(
        ThisRecord.Value in LoadedAttachmentsCol.Value,
        true,
        Collect(AttachmentsToBeUploadedCol, ThisRecord)
    )
);

// Compare initially loaded attachments with update attachments to see which ones are to be deleted
ClearCollect(AttachmentsToBeRemovedCol, Blank());
ForAll(
    LoadedAttachmentsCol,
    If(
        ThisRecord.Value in UpdatedAttachmentsCol.Value,
        true,
        Collect(AttachmentsToBeRemovedCol, ThisRecord)
    )
);

// Upload new attachments
Set(lastUpdateRequest, EditRequestForm.LastSubmit);
ForAll(
    AttachmentsToBeUploadedCol,
    Patch(
        'AttachmentsList',
        {
            Attachment: ThisRecord,
            'Attachment Name': Name,
            'Request ID': lastUpdateRequest
        }
    )
);

// Remove attachments that need to be removed
ForAll(AttachmentsToBeRemovedCol,
    Remove(
        'AttachmentsList',
        Filter(
            'Sell contract attachments',
            'Attachment ID' = ID
        )
    )
);

// Clear loaded collection to clean the datacard
ClearCollect(LoadedAttachmentsCol, Blank());

 

That's it. If there is anything unclear - feel free to contact me and I will make sure to explain the best I can.

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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

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.    

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 (974)