Skip to main content

Notifications

Community site session details

Community site session details

Session Id : arN2PxdRK8X/IFI4/o5iAZ
Power Apps - Building Power Apps
Unanswered

Behavior function in a non-behavior property

Like (0) ShareShare
ReportReport
Posted on 24 Mar 2023 16:33:22 by

Good afternoon Community,

 

I am experiencing the above error after building an app to collect data from a from and pass it to a SharePoint list.

 

On the SP list I have created 3 Lookup controls which I hope will look up data from a table in the Dataverse (when it is uploaded)

I have also created 4 drop down controls to select a value between 1-4, as well as 3 text boxes, a user search field in O365, and finally a box to collect the ID of the person logging in and completing the form.  

I have successfully set up most of the form, but I'm experiencing the error "Behavior function in a non-behavior property".

mc00515_0-1679673254628.png

P'Apps doesn't point to where the fault lies, just reports it, and stops the app from working.

When I hit the submit button, and error is returned saying "Title Field required".

When I add the title field, and run it again,  it works,, but I don't understand why?

The Title field appears to be connected with the 3 lookup fields:

mc00515_1-1679675313387.png

 

So if I add it back 

mc00515_2-1679675519825.png

The app runs. Since the title is supposed to be data picked up from the Dataverse, I am clearly doing something wrong by having to add it back manually.

I don't understand why a Title field is mandatory? I think my approach must be wrong. Can anyone explain the best approach?

 

 

  • Community Power Platform Member Profile Picture
    on 29 Mar 2023 at 11:08:26
    Re: Behavior function in a non-behavior property

    @Pstork1 and @BostonSailor , thanks again for your valued input. Your guidance has led to the app working now - super grateful for the guidance.

     

    I'm not hundred percent sure I'm on the right track yet, however, about this default ‘Title’ column and how it should integrate with the 3 Lookup columns I have now added. Regarding your advice @Pstork1, "What should normally be in the Title field when you submit the data?" That's a very good question. I'm still trying to get my head around things.

     

    To back up a bit, my first iteration of the app around 4-5 months ago, consisting of the default Title column renamed "ID", type single line of text, incrementally added a numeric value to the previous record in SP. I thought that was quite useful from a tracking point of view. I can't for the life of me think how it behaved like an auto number field with a field set to "single line of text". That was then, and now the project has shifted to require three additional columns that will pull in data uploaded batch wise from an external source.

     

    Having researched known resources on the internet, it seems the way forward it is to upload that  data to the Dataverse, and then use lookup types to bring that data into the App, to then be pushed into the SP list. If my approach is not the best, I should appreciate further guidance.

     

    Now the app more less seems to be doing what it was designed for – except pick up the lookup data from the Dataverse (that has yet to be uploaded).

     

    I can't recall how I got some test data into the Lookup fields previously, but I think it must have been directly through SP since that seems to be the only way I can get it in now. I can't repeat that effect now. With Look ups, is there a setting somewhere that permits free texting data directly through the control box or is it strictly for looking up elsewhere, be that SP or the Dataverse?

     

    Regarding integration with the Lookup columns, here is how I setup the first setting options.

    mc00515_0-1680088411598.png

    These are my column headers in SP.

    mc00515_1-1680088602579.png

     

    Am I supposed to align it to Title?

  • Community Power Platform Member Profile Picture
    on 29 Mar 2023 at 10:47:33
    Re: Behavior function in a non-behavior property

    Having said that I did see a delete option in the List settings. I didn't try it.

  • Pstork1 Profile Picture
    66,162 Most Valuable Professional on 28 Mar 2023 at 17:13:32
    Re: Behavior function in a non-behavior property

    I would recommend finding another use for the Title column that will always have data rather than making it not required.  SharePoint expects it to be required and there can be side effects if you change that setting.  They are fairly rare, but I have seen issues in the past when people rename the Title column or make it not required.

  • BostonSailor Profile Picture
    150 on 28 Mar 2023 at 17:07:03
    Re: Behavior function in a non-behavior property

    You can't delete it, but you can ignore it. You need to go and make it not required, though.

  • Pstork1 Profile Picture
    66,162 Most Valuable Professional on 28 Mar 2023 at 17:02:47
    Re: Behavior function in a non-behavior property

    In a SharePoint data source the Title column is required by default.  So the Title field always has to have something in it when you submit.  What should normally be in the Title field when you submit the data?

  • BostonSailor Profile Picture
    150 on 28 Mar 2023 at 16:49:58
    Re: Behavior function in a non-behavior property

    You should take the error message at face value.

     

    You are updating a SharePoint list, which always has a column called Title. By default, this is a required field. Go to the SharePoint list, List Properties, and make the Title column not required.

  • Community Power Platform Member Profile Picture
    on 28 Mar 2023 at 16:44:10
    Re: Behavior function in a non-behavior property

    Thanks for the heads-up @Pstork1 and @BostonSailor . I  moved the code from the App.OnStart to OnVisible screen. It worksed once, now gives an error message on the Submit button. It will work if I add text to the title control.

     

    So to be clear, my code in the AppOnStart was Set(UserEmail, User().Email),  to collect the the person's ID who logs onto to complete the form, then pass the data to my SharePoint list. So I moved the code here

    mc00515_0-1680021566185.png

    The error keeps coming back to Field title required.

    mc00515_1-1680021843127.png

     

  • BostonSailor Profile Picture
    150 on 24 Mar 2023 at 18:55:11
    Re: Behavior function in a non-behavior property

    Pstork is correct, although I would say that App.StartScreen requires a formula that yields a "screen" reference as a result. In any case, move your behavior to OnStart or OnVisible. 

  • Pstork1 Profile Picture
    66,162 Most Valuable Professional on 24 Mar 2023 at 16:40:00
    Re: Behavior function in a non-behavior property

    You've added some code to the App.StartScreen property.  That property can only contain a reference to a screen, not a formula.  You need to move the code to either the App.OnStart property or to the OnVisible property of the screen you reference in the App.StartScreen.  You may need to change your settings to put it in App.OnStart since that is disabled by default now.

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

Understanding Microsoft Agents - Introductory Session

Confused about how agents work across the Microsoft ecosystem? Register today!

Warren Belz – Community Spotlight

We are honored to recognize Warren Belz as our May 2025 Community…

Congratulations to the April Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard > Power Apps - Building Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 89 Most Valuable Professional

#2
MS.Ragavendar Profile Picture

MS.Ragavendar 60

#3
stampcoin Profile Picture

stampcoin 48

Overall leaderboard