web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Apps
Answered

Had to remove

(0) ShareShare
ReportReport
Posted on by 9

Had to remove.

Categories:
I have the same question (0)
  • RandyHayes Profile Picture
    76,299 Super User 2024 Season 1 on at

    @JustBeginningPo 

    Is the 'Report a Kiosk Fault' the datasource for your form?

    If so, then you need not do any patching and can do what you are trying to do directly in the form.

    Let me know if this is the case or not.

     

    Also, if it is - is the logic that NEW record should have the current user in the 'User Reporting' column and then from that point on, it should not change (i.e. editing a the record by another user should NOT change the User Reporting Column?)

  • JustBeginningPo Profile Picture
    9 on at

    @RandyHayes 

    Yes, 'Report a Kiosk Fault' is the datasource for my Form. (SPList)

    How would I go about doing this directly from the form instead?

     

    I have it set on datacard set to DisplayMode.View and the datacardvalue set to DisplayMode.Edit (got to keep the borders somehow!), and as the user is brough to the screen on the App, it detects who the user is and populates it accordingly, without users having to lift a finger.

  • Verified answer
    RandyHayes Profile Picture
    76,299 Super User 2024 Season 1 on at

    @JustBeginningPo 

    Very good.  So a couple of things.

    1) Your initial formula will not work as you expected.

    You are checking (with an If) the result of SubmitForm.  SubmitForm does not return a result, so your formula will never evaluate as you think it should.

    What you need to do is change your OnSelect action for the control that you are using to Submit to the following:

    SubmitForm(KioskFaultForm)

    This is all you should have in there.

    Then set the OnSuccess action of KioskFaultForm to:

    Navigate(SuccessForm)

    And the OnFailure action to:

    Navigate(FailureForm)

     

    Now, in the DataCard for your 'User Reporting' field.  If you have a combobox to pick people from, then set the DefaultSelectedItems property to:

    Coalesce(Parent.Default,
     With({_usr: User()},
     {
     Claims: "i:0#.f|membership|" & Lower(_usr.Email),
     Department: "",
     DisplayName: _usr.FullName,
     Email: _usr.Email,
     JobTitle: "",
     Picture: ""
     }
     )
    )

    (Note: you don't need the odata.type any longer and you cannot set the Picture column as you had)

     

    If you have some other form of displaying this user information (other than a combobox people picker), then set the Default property of the DataCard to the same formula above.

     

    If you have neither and this is a hidden datacard, then you can go right to the Update property of the datacard and place that same formula as above.  

     

    Choose 1 depending on your form (not all 3).

     

  • JustBeginningPo Profile Picture
    9 on at

    @RandyHayes 

    1. Thank you for that, I'm doing this on about by 10th cup of coffee and it somehow made sense in my head. This has now been fixed.

     

    2. You're correct on assuming it's a ComboBox as that's what it is. 🙂 

     

    I've just tested it.... AND IT WORKED :DDD

     

    Though I did lose the some text.... it used to look like " [fullName} - [Department] ", which was a byproduct of using Office365's DisplayName parameter. Is there anyway to get that back as well, whilst it continues to work like a charm above? Would really appreciate it.

     

    And for the learning experience...

    1. What happened with the odata.type?

    2. Why is "Picture: _user.Image()" not a thing?

    3. Is there any up-to-date learning courses / video tutorials that you could recommend to a beginner?

  • timl Profile Picture
    37,283 Super User 2026 Season 2 on at

    @JustBeginningPo - There are some video tutorials I would recommend here  😉

    https://www.youtube.com/channel/UCi2pZL1kGf6TcAG0ACdaAnw

     

  • RandyHayes Profile Picture
    76,299 Super User 2024 Season 1 on at

    @JustBeginningPo 

    1. The odata.type is assumed now and no longer needed to be specified (which is great because I only had about 40% of it memorized).

    2. The reality is, the Claims and Email are about the only things that are of value when setting the SharePoint user column.  SharePoint has its own user management built in, so you cannot set those properties on the user...well, you can, but SharePoint will ignore them.  SharePoint users are synchronized with Office 365 in the background.  When you add a user that SharePoint has not "seen", it will get the appropriate information.  When you change one that has been seen, it will be "queued" up to resync on the next timed sync - that you don't control.

    3.  There are a lot of videos out there to get some beginning steps underway.  Thank you @timl for the reference to my own videos 😁  While I do have a few videos out there, they are nowhere near the exhaustive quantity to get all things answered.  Just be careful with some of the videos you will find.  Many provide bad advice and incorrect information on how things work.  My videos do focus more on the "reality" of how PowerApps works, but again, I need more time in a day to keep on top of them and get some more out there.

     

    My basic tips would be:

    1) Remember - you are not coding/developing, you are designing.  PowerApps is modeled around Excel, so you are designing formulas

    2) Again - PowerApps is modeled around Excel.  In Excel you write a formula in one cell and then reference the result in others.  Do the same in PowerApps...all of your controls are global and you can reference the property results at any place.  

    3) Think tables and records.  Get up to speed on JSON syntax and how it is used in PowerApps.  It's pretty basic, but once you can picture it all in your head, so many of the functions and actions will all make sense.

    4) If you find yourself writing a lot of formulas in OnXxxx actions, setting variables, using collections - then you are thinking too programmer/developer.  Step back and think Excel.

     

    Hopefully some of that will be helpful and then you will have to change your name on here from JustBeginning to NowAnExpert

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 358 Most Valuable Professional

#2
11manish Profile Picture

11manish 214 Super User 2026 Season 2

#3
Mohsin Ali Profile Picture

Mohsin Ali 185

Last 30 days Overall leaderboard