cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
JerryH
Resolver III
Resolver III

Insert Media > Add Picture - Simple instructions and attach to email

hi

Can anyone direct me to "simple to follow instructions" to Insert Media > Add Picture - and then attach photo to email coding

Thanks

Jerry

AddMedia.PNG

3 ACCEPTED SOLUTIONS

Accepted Solutions
wyotim
Resident Rockstar
Resident Rockstar

Hi @JerryH, this took a little digging for me as I have managed to go this long without ever sending an email with an attachment from Power Apps. Pulling from your other thread, you would add the following to the code in curly braces:

Attachments: {Name: AddMediaButton1.FileName, ContentBytes: UploadedImage1.Image, '@odata.type': ""}

where AddMediaButton1 and UploadedImage1 are the default names of the two items in the AddMediaWithImage control. 

 

So if I grab your previous code from the other thread, it would look something like this:

Office365Outlook.SendEmailV2(
    "jerry.hald@nworld.com",
    "Asset Fault Log Request",
    "Equipment Fault - Call out required" & Concat(
        FaultList,
        "<table style='700'>
            <tr>
                <td><b>Client Name :</b></td>
                <td>" & ManufacturerName & "</td>
            </tr>" &
            "<tr>
                <td><b>Location :</b></td>
                <td>" & LocationName & "</td>
            </tr>" &
            "<tr>
                <td><b>Asset Description :</b></td>
                <td>" & AssetDecription & "</td>
            </tr>" &
            "<tr>
                <td><b>Serial Number :</b></td>
                <td>" & 'Device Name' & "</td>
            </tr>
        </table></body>"
    ),
    {
        Importance: "Normal"
        Attachments: {Name: AddMediaButton1.FileName, ContentBytes: UploadedImage1.Image, '@odata.type': ""}
    }
)

Again, you may need to change the AddMediaButton1 and UploadedImage1 titles to match the names you have. It's a bit of a beast but the main takeaway is that the Attachments section needs to be a table with those three items (Name, ContentBytes, and '@odata.type' which has a blank value). With this in mind, you could put multiple items in a collection and use that to send numerous attachments if needed.

 

I hope that gets you going! Let me know either way and I will follow up if needed!

View solution in original post

wyotim
Resident Rockstar
Resident Rockstar

Hi @JerryH! Sorry for the non-response to your first message; it's been a full day. 😵 😁 For the record, I'm fine with you posting in the same thread. It could be good to make a new thread if the issue is different enough and you think others could benefit from seeing it but otherwise we can keep it all in the same one. 

 

From looking at your code, I am noticing that the closing parentheses are missing from the Patch statement and the ForAll statement. That might explain the two errors you are seeing. Let's start there and see if that solves it!

 

ForAll(
    Filter(
        Devices1_1.AllItems,
        VerifyItem_1.Value = true
    ),
    Patch(
        Devices,
        Defaults(Devices), 
        {
            Name: User().FullName,
            Date: Now(),
            Status: "Confirmed"
        }
    )
)

 

View solution in original post

wyotim
Resident Rockstar
Resident Rockstar

Hey @JerryH, so I have good news and bad news. The bad news is that I couldn't find a way to use the disambiguation operator on the gallery reference. This means that the ForAll loop will only look at the first item in the gallery and never make it past that one. It also seems that it isn't possible to reference the GUID that Power Apps assigns. This part might not be too much of a problem as long as you have one unique value, like a device name or something, that you can reference. It would also work to use multiple items in the LookUp to define a row if one value isn't unique but two or more together are.

 

The good news is that doing what you are trying without the gallery reference isn't too difficult. Here's what I did: 

 

On the checkbox control, I put the following items in the OnCheck and OnUncheck properties:

// OnCheck
Collect(colVerifiedDevices, ThisItem)

// OnUncheck
Remove(colVerifiedDevices, ThisItem)

This simply adds the row of data from the gallery into a collection called colVerifiedDevices if the box is checked and removes it if it is unchecked. I then used this collection in the ForAll loop instead of the gallery like so:

ForAll(
    colVerifiedDevices,
    Patch(
        Devices,
        LookUp(Devices, DeviceName = colVerifiedDevices[@DeviceName]), 
        {
            Name: User().FullName,
            Date: Now(),
            Status: "Confirmed"
        }
    )
);
Clear(colVerifiedDevices)

I assumed that the name of the column with Test6, Test7, Test8, etc. was called DeviceName, so you will want to change that with the field name with the unique values.

 

If you need to use more than one field to define a unique row, it would look something like this:

ForAll(
    colVerifiedDevices,
    Patch(
        Devices,
        LookUp(Devices, Field1 = colVerifiedDevices[@Field1] && Field2 = colVerifiedDevices[@Field2]), 
        {
            Name: User().FullName,
            Date: Now(),
            Status: "Confirmed"
        }
    )
);
Clear(colVerifiedDevices)

Just repeat the '&& Field# = colVerifiedDevices[@Field#]' for each additional field you need in there (where Field# is the column name of course).

 

One thing to note is the Clear(colVerifiedDevices) at the end of the ForAll Patch statement. This clears the collection out when the loop is done so those values aren't repeated.

 

I hope all of that makes sense but feel free to hit me up if it doesn't!

View solution in original post

11 REPLIES 11
wyotim
Resident Rockstar
Resident Rockstar

Hi @JerryH, this took a little digging for me as I have managed to go this long without ever sending an email with an attachment from Power Apps. Pulling from your other thread, you would add the following to the code in curly braces:

Attachments: {Name: AddMediaButton1.FileName, ContentBytes: UploadedImage1.Image, '@odata.type': ""}

where AddMediaButton1 and UploadedImage1 are the default names of the two items in the AddMediaWithImage control. 

 

So if I grab your previous code from the other thread, it would look something like this:

Office365Outlook.SendEmailV2(
    "jerry.hald@nworld.com",
    "Asset Fault Log Request",
    "Equipment Fault - Call out required" & Concat(
        FaultList,
        "<table style='700'>
            <tr>
                <td><b>Client Name :</b></td>
                <td>" & ManufacturerName & "</td>
            </tr>" &
            "<tr>
                <td><b>Location :</b></td>
                <td>" & LocationName & "</td>
            </tr>" &
            "<tr>
                <td><b>Asset Description :</b></td>
                <td>" & AssetDecription & "</td>
            </tr>" &
            "<tr>
                <td><b>Serial Number :</b></td>
                <td>" & 'Device Name' & "</td>
            </tr>
        </table></body>"
    ),
    {
        Importance: "Normal"
        Attachments: {Name: AddMediaButton1.FileName, ContentBytes: UploadedImage1.Image, '@odata.type': ""}
    }
)

Again, you may need to change the AddMediaButton1 and UploadedImage1 titles to match the names you have. It's a bit of a beast but the main takeaway is that the Attachments section needs to be a table with those three items (Name, ContentBytes, and '@odata.type' which has a blank value). With this in mind, you could put multiple items in a collection and use that to send numerous attachments if needed.

 

I hope that gets you going! Let me know either way and I will follow up if needed!

Thank you so much...

I have a few other questions for my App?

Can i use this thread?

HI Wyotim

Any chance you can see if you can pick up an errors in this code? Basically, when user checks the checkbox, and presses button, it sends info back to datasource…..

 

ForAll(Filter(Devices1_1.AllItems,VerifyItem_1.Value = true),
Patch(Devices,Defaults(Devices),

{Name: User().Email,

Date: Now(),

Status: "Confirmed"}

 

Code.PNGPicture1.pngAssetVerification.PNG

wyotim
Resident Rockstar
Resident Rockstar

Hi @JerryH! Sorry for the non-response to your first message; it's been a full day. 😵 😁 For the record, I'm fine with you posting in the same thread. It could be good to make a new thread if the issue is different enough and you think others could benefit from seeing it but otherwise we can keep it all in the same one. 

 

From looking at your code, I am noticing that the closing parentheses are missing from the Patch statement and the ForAll statement. That might explain the two errors you are seeing. Let's start there and see if that solves it!

 

ForAll(
    Filter(
        Devices1_1.AllItems,
        VerifyItem_1.Value = true
    ),
    Patch(
        Devices,
        Defaults(Devices), 
        {
            Name: User().FullName,
            Date: Now(),
            Status: "Confirmed"
        }
    )
)

 

Amazing!!!!!! That result made me so happy!

 

3 Questions.

1. The information recorded in my Datasource but in new rows... Can we get to show in correct asset row. See image below

2. With my Dropdowns - can we get the Item to default either to Blank or one of the Items such as Select?

3. Now that my App is almost complete. Should i move the Datasource from Excel to Sharepoint?

 

DefaultItem.PNG


RecordedAsset.PNG

wyotim
Resident Rockstar
Resident Rockstar

Hey @JerryH, glad that did the trick for you!

 

For the first question, the reason it is writing a new row is due to the Defaults(Devices) section of your code. This writes a new record using the default values of the data source listed. To update a row, you will need to swap that portion of code out with something that identifies a record. I'll need to test using a gallery as a reference in a ForAll loop as I have never done that before, but one general way to do it is to use a LookUp to find the specific record you are on in the loop in the data source. Something generally like this:

ForAll(
    ForAllDataSource,
    Patch(
        DataSourceName,
        LookUp(DatasourceName, FieldYouWant = ForAllDataSource[@FieldYouWant]),
        {
            ...
        }
    )
)

You will notice the square brackets and the @ symbol. The @ symbol is called a disambiguation operator and what it is doing is making sure Power Apps knows which field you are referencing, in this case, the particular FieldYouWant field that the ForAll loop is on in the ForAllDataSource data source. 

 

The best field to use here is something that uniquely defines that row, like an ID of some kind. In Excel, Power Apps makes that GUID column that I see at the end of your data table. That would be the best thing to use. As I said before, I am not sure of the syntax when referencing a gallery but I will test that after I post this message.

 

On question 2, this is possible. Dropdowns have an AllowEmptySelection property just for blank values. If you set that to true and then set the Default property to "", this should accomplish that part. If you are in a form, leaving the Default set to Parent.Default would show the value for that record or leave it blank if there is no value.

 

As far as the third question goes, SharePoint is a good data source and might be easier to use than Excel. Back in the old days when I got started with Power Apps, sharing an app with Excel as a data source didn't seem to work so well so I stopped trying and haven't attempted it since. I'm sure it's a much better experience now, but Excel does have limitations with how much data can be used and it is a bit on the slow side.

 

One thing about SharePoint to keep in mind is that anyone with access to that app will have access to that table on SharePoint, which is the same with Excel but SharePoint has lots of security options to control what data each person can see. I'm not a SharePoint expert at all (the company I work for uses SQL so that is what I know best) but there are some really good YouTube channels to check out if you want more info about building Power Apps for SharePoint and all the layers of permissions. Laura Rogers (WonderLaura) and Shane Young are both great channels to check out.

 

Hopefully, that helps but if I can try to clarify or explain more, let me know! And I'll get back on the gallery syntax as soon as I crack it.

wyotim
Resident Rockstar
Resident Rockstar

Hey @JerryH, so I have good news and bad news. The bad news is that I couldn't find a way to use the disambiguation operator on the gallery reference. This means that the ForAll loop will only look at the first item in the gallery and never make it past that one. It also seems that it isn't possible to reference the GUID that Power Apps assigns. This part might not be too much of a problem as long as you have one unique value, like a device name or something, that you can reference. It would also work to use multiple items in the LookUp to define a row if one value isn't unique but two or more together are.

 

The good news is that doing what you are trying without the gallery reference isn't too difficult. Here's what I did: 

 

On the checkbox control, I put the following items in the OnCheck and OnUncheck properties:

// OnCheck
Collect(colVerifiedDevices, ThisItem)

// OnUncheck
Remove(colVerifiedDevices, ThisItem)

This simply adds the row of data from the gallery into a collection called colVerifiedDevices if the box is checked and removes it if it is unchecked. I then used this collection in the ForAll loop instead of the gallery like so:

ForAll(
    colVerifiedDevices,
    Patch(
        Devices,
        LookUp(Devices, DeviceName = colVerifiedDevices[@DeviceName]), 
        {
            Name: User().FullName,
            Date: Now(),
            Status: "Confirmed"
        }
    )
);
Clear(colVerifiedDevices)

I assumed that the name of the column with Test6, Test7, Test8, etc. was called DeviceName, so you will want to change that with the field name with the unique values.

 

If you need to use more than one field to define a unique row, it would look something like this:

ForAll(
    colVerifiedDevices,
    Patch(
        Devices,
        LookUp(Devices, Field1 = colVerifiedDevices[@Field1] && Field2 = colVerifiedDevices[@Field2]), 
        {
            Name: User().FullName,
            Date: Now(),
            Status: "Confirmed"
        }
    )
);
Clear(colVerifiedDevices)

Just repeat the '&& Field# = colVerifiedDevices[@Field#]' for each additional field you need in there (where Field# is the column name of course).

 

One thing to note is the Clear(colVerifiedDevices) at the end of the ForAll Patch statement. This clears the collection out when the loop is done so those values aren't repeated.

 

I hope all of that makes sense but feel free to hit me up if it doesn't!

Absolutely amazing - thank you so so much.😀

wyotim
Resident Rockstar
Resident Rockstar

@JerryH Happy to be able to help out! If I can be of assistance in the future, feel free to tag me in the post.

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!  

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

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

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. 

Top Solution Authors
Top Kudoed Authors
Users online (3,876)